"ConfigMgr Restarts Computer" not working
- Hello,
We are currently deploying SEP to our clients and have mixed results for the rebooting. Some clients reboot after the install and some dont. They all receive the status saying that exit code is "0" and that a reboot is required. We have to manually reboot the machines so they continue with the rest of the advertisement. The advertisement has "ignore maint windows" ticked. Here is a sample from execmgr.log
Script for Package:UMG00530, Program: SEP 11.0.4202.75 - Install WITH REBOOT succeeded with exit code 0 execmgr 11/4/2009 2:55:39 PM 4800 (0x12C0)
Raising event:
[SMS_CodePage(850), SMS_LocaleID(2057)]
instance of SoftDistProgramPrelimSuccessEvent
{
AdvertisementId = "EU0201EE";
ClientID = "GUID:D54E8CC6-26F6-4FBF-8DE3-AF76807023FF";
DateTime = "20091104145539.696000+000";
ExitCode = "0";
MachineName = "UKROMWL93393";
PackageName = "UMG00530";
ProcessID = 1720;
ProgramName = "SEP 11.0.4202.75 - Install WITH REBOOT";
SiteCode = "ROM";
ThreadID = 4800;
};
execmgr 11/4/2009 2:55:39 PM 4800 (0x12C0)
Raised Program Prelim Success Event for Ad:EU0201EE, Package:UMG00530, Program: SEP 11.0.4202.75 - Install WITH REBOOT execmgr 11/4/2009 2:55:39 PM 4800 (0x12C0)
Execution is complete for program SEP 11.0.4202.75 - Install WITH REBOOT. The exit code is 0, the execution status is SuccessRebootRequired execmgr 11/4/2009 2:55:39 PM 3664 (0x0E50)
Execution Request for package UMG00530 program SEP 11.0.4202.75 - Install WITH REBOOT state change from Running to ReportStatusAtReboot execmgr 11/4/2009 2:55:39 PM 3664 (0x0E50)
Persisting request for program SEP 11.0.4202.75 - Install WITH REBOOT package UMG00530 in state ReportStatusAtReboot execmgr 11/4/2009 2:55:39 PM 3664 (0x0E50)
Program exited expecting reboot, delaying execution of other programs for 60000 ms execmgr 11/4/2009 2:55:39 PM 3664 (0x0E50)
Execution Manager timer has been fired. execmgr 11/4/2009 2:56:39 PM 3296 (0x0CE0)
CExecutionRequestManager::OnTimer - Processing reboot Delay Timer execmgr 11/4/2009 2:56:39 PM 3296 (0x0CE0)
CExecutionRequestManager::ProcessRebootDelayTimer execmgr 11/4/2009 2:56:39 PM 3296 (0x0CE0)
Entering CTimerTask::CancelTimer. execmgr 11/4/2009 2:56:39 PM 3296 (0x0CE0)
We have no maintenance windows on our user collections. Some machines do actually reboot. The user was not logged on during the install and the system account was used for the install. I have suppressed notifications from the program setting and our countdown setting for the site is 5min so even if that option was set, surely after 5min it should force the reboot.
Why does ConfigMgr not reboot the machine even though the option is set? How does ConfigMgr reboot the machine? Does it use WMI? we have a script that uses WMI for rebooting and we find that it doesnt always work, just like the ConfigMgr option.
Thanks in advance for your help!
Answers
We didn't worry about booting the machines after SEP was installed because it works even without the restart. At least it did for us. I have only had a few occasions where machines don't restart. I have had it more with Patching, when the machine says it needs to restart but never does and several days and windows later it still hasn't restarted. For your problem you could easily deploy with a cmd or batch file
---- install.bat ----
msiexec /i sep.msi /qn
restart -r -f -t 30
---------------------
It would then restart with the windows command instead of the ConfigMgr restart command.
Alternately you can create a collection of machines that have a staus code of 3010 or the other restart required status messages and then send down a restart command when the machine has no one logged in. Do you have the program set to program restarts computer or ConfigMgr restarts computer?
http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com- Marked As Answer byEric C. MattoonMSFT, ModeratorMonday, November 09, 2009 2:23 PM
- Proposed As Answer byEric C. MattoonMSFT, ModeratorFriday, November 06, 2009 3:56 PM
All Replies
- Maintenance windows are a "union" if you reflect back on 2nd or 3rd grade math "set theory". So, even though you don't have MW set on the User colleciton, if you have them set on machine collections you get the union of most restrictive.
So, the question is "do you have MW set on machine collections?" If so, then that is probably why you are observing this behavior. If not, we'll investigate further. - Apologies for the confusion. i meant to say computer collections not user collections. we only work off machine accounts not groups or user accounts. the only collections we have with MW's are server collections and they are manually populated.
- Just to be 100% clear here... You don't have any maintenance windows anywhere right?
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum - We only have maintenance windows on our Server collections not our workstation collections. To confirm I have run the report "Maintenance Windows Available to a Particular Client" on all sites in the hierarchy and none of these clients are part of a maintenance window.
We didn't worry about booting the machines after SEP was installed because it works even without the restart. At least it did for us. I have only had a few occasions where machines don't restart. I have had it more with Patching, when the machine says it needs to restart but never does and several days and windows later it still hasn't restarted. For your problem you could easily deploy with a cmd or batch file
---- install.bat ----
msiexec /i sep.msi /qn
restart -r -f -t 30
---------------------
It would then restart with the windows command instead of the ConfigMgr restart command.
Alternately you can create a collection of machines that have a staus code of 3010 or the other restart required status messages and then send down a restart command when the machine has no one logged in. Do you have the program set to program restarts computer or ConfigMgr restarts computer?
http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com- Marked As Answer byEric C. MattoonMSFT, ModeratorMonday, November 09, 2009 2:23 PM
- Proposed As Answer byEric C. MattoonMSFT, ModeratorFriday, November 06, 2009 3:56 PM
- Thanks for the advice. I know how to do all that and we are currently implementing a similar method. But that is exactly what we are trying to avoid. My main question is not how to do the deployment, but WHY ConfigMgr is not rebooting the machines and HOW ConfigMgr calls the restart. If its WMI, then we can look into fixing WMI on these machines so our future deployments dont require a whole bunch of extra steps to secure a successful deployment.
- Try repairing WMI on a pilot group of machines which are not behaving as you expect.
