Finding and changing the restart timer within the SCCM 2007 Computer Client component may be a good idea as the default values are a 5 minute restart timer with a 1 minute final notification time. Here is how to do it:
-
Expand Site Settings
-
Select Client Agents
-
Select Computer Client Agent and enter the properties dialog box via the actions pane
-
Select the Restart tab
-
Change the "Restart countdown" and "Restart final notification" values to something more appropriate to your environment
-
Click the Apply button
-
Exit the dialog box
Here is a picture for your convenience:
During the SCCM 2007 upgrade, there is a section which will red line within SMS Trace. Here is the clip:
<06-19-2009 10:48:26> Attempting to delete Configuration Manager 2007 sub-program group
<06-19-2009 10:48:26> Failed to delete program group C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft System Center\Configuration Manager 2007 with error 3
<06-19-2009 10:48:26> Attempting to delete Microsoft System Center program group
<06-19-2009 10:48:26> Failed to delete program group C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft System Center with error 2
No need to panic. This happens because the program groups do not exist.
Error 2 = The system cannot find the file specified.
Error 3 = The system cannot find the path specified.
I just thought I should post this in case others see these red lines and freak out. If you are using SMS Trace from the Toolkit to watch your upgrade log files during the SCCM 2007 upgrade and you see red lines, read the lines before believing your upgrade has failed. SMS Trace will flag lines red which have the word "Error" in them.
i.e. <06-19-2009 10:32:26> SQL Script: Create SQL object v_WOLCommunicationErrorStatus
Just a small note to comfort some people that encounter this.
This weekend, I was monitoring an installation of the SQL Server 2005 client tools to a workstation. Normally, I would have the help desk perform this, but the particular individual had some critical DTS packages to run first thing this morning, so I wanted to ensure that everything installed properly. Of course, since it was critical that this worked, it did not.
So, I put this here for those of you who may run into this in the future.
execmgr.log:
Script for Package:CEN0011C, Program: SQL 2005 SP2 - 2nd Install failed with exit code 1307 execmgr 5/29/2009 6:39:36 PM 2224 (0x08B0)
Generally, I first check exit codes (which I do not recognize) against a handy link from symantec:
http://www.symantec.com/connect/articles/windows-system-error-codes-exit-codes-description
This specific error code yielded big goose egg on this site.
1307 This security ID may not be assigned as the owner of this object.
which made absolutely no sense in this case. So, I checked the following handy link from Microsoft:
http://msdn.microsoft.com/en-us/library/aa372835(VS.85).aspx
1307 There is not enough disk space remaining to install this file: [2]. If you can, free up some disk space, and click Retry, or click Cancel to exit.
This made far more sense that the Symantec site. I next checked the SQL installation summary log for SP2, which are located at: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.txt. The only failure noted in the summary was the following entry:
Summary
Setup cannot complete due to out of disk space.
Exit Code Returned: 1307
After checking the total disk space on the remote computer, I found this to be true. I had the user clean out some garbage and the installation worked fine.
I hope this saves others some time.