locked
Reboot popup comes up after deploying the SC1511 client RRS feed

  • Question

  • Hi,

    We could see a wired issue in an our environment as gives a reboot popup after deploying the SCCM 1511 client to the machine. We have verified the logs and found the below message in RebootCoordinator.log .

    Entered ScheduleRebootImpl - requested from 'ClientDeployment'. set Rebootby = 0. set NotifyUI = True. set PreferredRebootWindowType = 3

    based on above message, we are concluding that SCCM client triggers the non-mandatory reboot after the client deployment/upgraded.

    we would like to know why this is happening for few machines and also want to know the cause for triggering reboot.

    Monday, May 23, 2016 7:21 AM

Answers

  • Dear Sir,

    The notification is a process SCNotification.exe under ccmexec.exe. If it's already happened and you need to stop it, you may have to kill the SCNotification.exe process on the client side.

    Best regards

    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com



    • Edited by Frank Dong Tuesday, May 24, 2016 2:22 AM
    • Proposed as answer by Frank Dong Wednesday, June 1, 2016 8:33 AM
    • Marked as answer by Frank Dong Tuesday, June 7, 2016 1:13 AM
    Tuesday, May 24, 2016 2:22 AM

All replies

  • The ConfigMgr Client itself doesn't need a reboot. It's most likely a dependency like .NET Framework 4.5.2 for example. Examine ccmsetup.log and the other log file in C:\Windows\ccmsetup\Logs

    This might contain some useful Information as well: http://blog.configmgrftw.com/ugh-ccmsetup-error-codes/


    Simon Dettling | msitproblog.com | @SimonDettling

    Monday, May 23, 2016 7:49 AM
  • Thanks Simon for responding.

    I verified the CCMsetup.log and noticed that client is suppressing the reboot, but why SCCM client is not suppressing the reboot notification. is there any way to suppress the notification?

    And also want to know any other application issue comes up if higher version of .Net frame installed on the machine during the SCCM client installation.

    Monday, May 23, 2016 10:01 AM
  • Because it's a notification from the .NET Framework and not the ConfigMgr client agent. The only real solution here is to pre-deploy the .NET Framework to your clients and suppress the messages yourself or to use the recently released hotfix: https://support.microsoft.com/en-us/kb/3140781

    As for App Compat with .NET 4.5.2, there should be no issues if the app developers followed the rules.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, May 23, 2016 12:48 PM
  • Thanks Jason for replying.

    But,We are getting the notification from the software center only.

    Provided solution is for precautions for deploying the SC 1511 client before. If Client is already deployed to the machines and throwing Non-mandatory reboot notification, in that case what solution you could suggest us for suppressing the reboot notification.

    Monday, May 23, 2016 2:25 PM
  • OK. So that's different from what we've been discussing in this thread and has nothing to do with the client agent version or upgrade.

    Are you using a package or application? Is the message truly from ConfigMgr?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, May 23, 2016 2:38 PM
  • Dear Sir,

    The notification is a process SCNotification.exe under ccmexec.exe. If it's already happened and you need to stop it, you may have to kill the SCNotification.exe process on the client side.

    Best regards

    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com



    • Edited by Frank Dong Tuesday, May 24, 2016 2:22 AM
    • Proposed as answer by Frank Dong Wednesday, June 1, 2016 8:33 AM
    • Marked as answer by Frank Dong Tuesday, June 7, 2016 1:13 AM
    Tuesday, May 24, 2016 2:22 AM