You can use this guide to help you plan your upgrade from SCCM 2007 SP1 to SP2.
This guide is provided as is to help you in your LAB environment, if you find any errors please report them in the Forums. For best practice advice always refer to Technet and in particular refer to the Configuration Manager 2007 SP2 Upgrade Checklist
Verify your SCCM version
Before we get started, let's verify our SCCM version. Right click on your Site Name in ConfigMgr and choose Properties.
The version info should read 4.00.6468.2001 for the SP2 release candidate.
Close ConfigMgr and open up control panel, add remove programs.
Uninstall WAIK
Close ConfigMgr and open up Control Panel, Programs And Features.
highlight Windows Automated Installation Kit and choose Uninstall
Resized to 96% (was 1008 x 629) - Click image to enlarge
answer yes when prompted
and Click Allow if you see the UAC prompt.
If prompted about the Windows Deployment Services Server, choose Do not close Applications and click Ok
When the WAIK is uninstalled answer Yes to reboot when prompted.
Extract the SP2 Upgrade files
First of all, download the SP2 file from here
There are two versions:
Full install (Note, this is a 180 day Eval)
Upgrade Install (Use this one to upgrade SCCM 2007 Sp1 to Sp2)
After the reboot double click on our ConfigMgr07SP2Upgrade_RTM_ENU.exe file
You will be prompted to unzip the file to a folder, so give it a folder to unzip to eg: c:\sccmsp2upgrade
Once unzipped, now would be a good time to read the ReadMe particularly to highlight the Known Issues.
Quote
Known Issues with System Center Configuration Manager 2007 SP2
This section provides the most up-to-date information about issues with Configuration Manager 2007 SP2. These issues do not appear in the product documentation, and in some cases may contradict existing product documentation. Whenever possible, these issues will be addressed in later releases.
Adding Packages to WinPE Images for Operating System Deployment by Using WAIK 2.0 Might Fail On Servers That Run the 64-Bit Version of Windows Server 2003 and the 64-bit Edition of Windows Server 2008
Configuration Manager 2007 uses the Deployment Image Service and Management (DISM) tool and the Windows Automated Installation Kit (WAIK) 2.0 to add packages to WinPE images for operating system deployment of Windows 7. On computers that run the 64-Bit version of Windows Server 2003 or the 64-bit edition of Windows Server 2008, a known issue might cause the following DISM commands to fail when updating string values in the registry:
* /Add-Package
* /Enable-Feature
* /Disable-Feature
During the Configuration Manager 2007 SP2 installation, DISM runs the /Add-Package command on the site server. The command fails on site servers that run the 64-Bit version of Windows Server 2003 or the 64-bit edition of Windows Server 2008.
WORKAROUND Install hotfix 960037 on the site server computer before upgrading to Configuration Manager 2007 SP2. For information about this issue and to download this hotfix, see article 96037 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=164906).
This section provides the most up-to-date information about issues with Configuration Manager 2007 SP2. These issues do not appear in the product documentation, and in some cases may contradict existing product documentation. Whenever possible, these issues will be addressed in later releases.
Adding Packages to WinPE Images for Operating System Deployment by Using WAIK 2.0 Might Fail On Servers That Run the 64-Bit Version of Windows Server 2003 and the 64-bit Edition of Windows Server 2008
Configuration Manager 2007 uses the Deployment Image Service and Management (DISM) tool and the Windows Automated Installation Kit (WAIK) 2.0 to add packages to WinPE images for operating system deployment of Windows 7. On computers that run the 64-Bit version of Windows Server 2003 or the 64-bit edition of Windows Server 2008, a known issue might cause the following DISM commands to fail when updating string values in the registry:
* /Add-Package
* /Enable-Feature
* /Disable-Feature
During the Configuration Manager 2007 SP2 installation, DISM runs the /Add-Package command on the site server. The command fails on site servers that run the 64-Bit version of Windows Server 2003 or the 64-bit edition of Windows Server 2008.
WORKAROUND Install hotfix 960037 on the site server computer before upgrading to Configuration Manager 2007 SP2. For information about this issue and to download this hotfix, see article 96037 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=164906).
as I am running the X64 edition of Server 2008 I need to first check if I need to install the hotfix mentioned above and it seems the the hotfix is included in SP2 for Server 2008.
Install the Upgrade
Double click on Splash.HTA in the newly extracted folder
Run the PreRequisite checker click continue to the UAC prompt
I'm not running a SUP on this server so we can safely ignore the WSUS warning
click OK and run the Splash.hta file again, this time select to Install the Configuration Manager SP2 option
when the wizard appears click next
choose Upgrade an Existing...
accept the EULA
decide your CEIP settings
next choose to download the updates from the internet or if you have no internet connection on that server point to where you have downloaded the updates in advance
specify the path to the updates
and click next
you should see a summary of the upgrade, click next to begin
the PreRequisite checker will run again, as long as there are no show stoppers click Begin Install
after a long while the upgrade will be complete, make sure to scroll down to verify that all parts are marked as Completed and ok
click Next to complete the process and you can choose to view the upgrade log
Verify the new version
Now that the installation of SP2 is complete, start ConfigMgr and look at the version number.
The new version number should be 4.00.6487.2000
Verify your boot images
In ConfigMgr expand the Operating System Deployment node, boot images, select your X64 boot image and review it's properties, the version should read 6.1.7600.16385
once verified, you should update your Distribution Points with a copy of that boot image
Now that you are done, do the same with your X86 boot image
Create new Package from Definition
In ConfigMgr, expand the Software Distribution node and right click, choose New, Package from Definition
Choose the Configuration Manager Client Upgrade option
choose Always obtain files from a source directory
point to your client source eg: \\SERVER\sms_xxx\client where xxx is the site code, and choose finish
Expand the newly created package, and click on Programs, select the Advanced client and right click, choose Properties.
click on the Requirements tab, and select this program can run on any platform and click Apply
Right click on distribution points and select New, go through the wizard
when done, update your client to the same Distribution points
Final Actions after the Upgrade
* You need to update your Client versions to the new SP2 ConfigMgr Client.
* You may need to add network drivers back to your boot images otherwise network boot (which worked before the ugprade) may fail with the following error
PXE-T01: File Not Found
PXE-E3B: TFTP Error - File Not found.
SP2 tips and gotchas
* The Configuration Manager Service Pack Install Guide
* SCCM SP2 Upgrade Gotchas and Tips
* The SP2 Upgrade may take a lot of time especially if your Database is large
* How to create a custom boot image after the SP2 upgrade
* Upgrade the ConfigMgr consoles from SP1 to SP2 otherwise they will not work properly (advertisements missing etc)
* hotfix for "Number of retries" and "Delay before retrying (minutes)" retry settings
* SCCM 2007, ready to load SP2 and have some questions. .
No comments:
Post a Comment