ConfigMgr SP2 Client Upgrades forcing reboots
I upgraded my central site to SP2 (from SP1) yesterday morning and started deploying the SP2 client via an advert to my first batch of machines in the afternoon to upgrade their clients from SP1 to SP2.
Our first deployment targeted about 115 machines, 20 of which were running Server 2008 64-bit.
Of those 20 machines, 10 of them rebooted automatically with no prompt or warning after the client installation. Some of them rebooted multiple times (our AD admin says one of the DCs rebooted 7 times).
A quick investigation of the event logs returns the following logs related to the reboot:
(All of these have MSIinstaller as the source, all are logged with the same time stamp)
#1. Product: Configuration Manager Client -- Configuration completed successfully.
#2. Windows Installer reconfigured the product. Product Name: Configuration Manager Client. Product Version: 4.00.6487.2000. Product Language: 1033. Reconfiguration success or error status: 0.
#3. Windows Installer requires a system restart. Product Name: Configuration Manager Client. Product Version: 4.00.6487.2000. Product Language: 1033. Type of System Restart: 1. Reason for Restart: 1.
#4. Ending a Windows Installer transaction: C:\Windows\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi. Client Process Id: 2496.
#5. The Windows Installer initiated a system restart to complete or continue the configuration of 'Configuration Manager Client'.
The machine then proceeds to log everyone off and reboot with a prompt or any chance to interrupt it.
These event particular logs were generated from a machine running 64-bit server 2008 Enterprise with Service Pack 2.
This machine already *had* the updated client, but for grins I decided to manually reinstall the client with the following command line:
(FQDNs and site codes redacted)
\\xxxxxx-sccm01\SCCMClient\ccmsetup.exe SMSSITECODE=xxx CCMHTTPPORT=80 CCMHTTPSPORT=443 CCMALLOWSILENTREBOOT=0 SMSMP=xxxxxx-SCCM01.xxx.xxx.edu SMSSLP=xxxxxx-sccm01.xxx.xxx.edu FSP=xxxxxx-reporting.xxx.xxx.edu
And it rebooted automatically, without warning after the ccmsetup process finished.
This is the same command line that I've been using in production (and the same command in the aforementioned advert deployment) for 18 months without any issues like this ever cropping up previously.
Has anyone else seen anything like this?
My fellow admins are pretty pissed at me right now.
I can provide any more information or logs upon request.
Answers
I believe I have figured this out.
On the 64-bit Windows Server 2008 machines, if run my installation command line and omit the CCMALLOWSILENTREBOOT=0 argument, the machines do not reboot.
If I include the argument, the machines are more likely to (but not guaranteed to) restart. I can duplicate this behavior 100% of the time on one of my 64-bit Server 2008 machines that has the SCCM SP2 client already installed.
Here's what my new "mostly working" command line looks like:
\\xxxxxx-sccm01\SCCMClient\ccmsetup.exe SMSSITECODE=xxx CCMHTTPPORT=80 CCMHTTPSPORT=443 SMSMP=xxxxxx-SCCM01.xxx.xxx.edu SMSSLP=xxxxxx-sccm01.xxx.xxx.edu FSP=xxxxxx-reporting.xxx.xxx.edu
However, I'm hesitant to strip out the CCMALLOWSILENTREBOOT=0 argument and just call it a day, since I really, really don't want these machines to ever reboot as a result of a client installation.
The command line arguments are documented here: http://technet.microsoft.com/en-us/library/bb680980.aspx
Can someone chime in on this?
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 16, 2009 3:55 AM
- Proposed As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 16, 2009 3:55 AM
All Replies
SCCM Client require minimun BITS 2.5 version on workstation, if not SCCM Client upgrade will install BITS 2.5 and its require reboot. however because of bits installation workstation will not reboot automatically it will only wait for reboot. it can reboot automatically if you deploy client software through SUP.
Surendar Reddy- All of these machines already had the SCCM already had the SCCM SP1 client installed, and BITS 2.5 is a pre-requisite for that client agent.
I've also found that if I manually re-run the installation on a 64-bit Windows Server 2008 machine that already has the SP2 agent installed successfully using the aforementioned command line, the machine reboots again without warning.
If if the BITS 2.5 client component installation was forcing a restart of the machine automatically (which it shouldn't), it certainly should not require the machine to reboot again if the agent is re-installed.
- Yuck! This is good info to know. Hopefully someone will reply with a solution.
- Not to be a meanie and poke holes in the BITS theory:
http://support.microsoft.com/kb/923845
This is the KB associated with the BITS25 folder within the x64 folder in the SCCM client installation location.
Notice that this article does not mention a version of the BITS package for Server 2008 or 64-bit Server 2008, nor is there an .exe/.msi/.msu for any version of Server 2008.
Also:
http://msdn.microsoft.com/en-us/library/aa363167%28VS.85%29.aspx
says:
"The 2.5 features are available in the Windows Server 2008, Windows Vista, and Windows XP with Service Pack 3 (SP3) operating systems." I believe I have figured this out.
On the 64-bit Windows Server 2008 machines, if run my installation command line and omit the CCMALLOWSILENTREBOOT=0 argument, the machines do not reboot.
If I include the argument, the machines are more likely to (but not guaranteed to) restart. I can duplicate this behavior 100% of the time on one of my 64-bit Server 2008 machines that has the SCCM SP2 client already installed.
Here's what my new "mostly working" command line looks like:
\\xxxxxx-sccm01\SCCMClient\ccmsetup.exe SMSSITECODE=xxx CCMHTTPPORT=80 CCMHTTPSPORT=443 SMSMP=xxxxxx-SCCM01.xxx.xxx.edu SMSSLP=xxxxxx-sccm01.xxx.xxx.edu FSP=xxxxxx-reporting.xxx.xxx.edu
However, I'm hesitant to strip out the CCMALLOWSILENTREBOOT=0 argument and just call it a day, since I really, really don't want these machines to ever reboot as a result of a client installation.
The command line arguments are documented here: http://technet.microsoft.com/en-us/library/bb680980.aspx
Can someone chime in on this?
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 16, 2009 3:55 AM
- Proposed As Answer byEric Zhang - MSFTMSFT, ModeratorMonday, November 16, 2009 3:55 AM
