imageHere’s a new Knowledge Base article we published today. This one talks about an issue where attempting to install System Center Configuration Manager 2007 (ConfigMgr 2007) hotfix 2509007 along with either 977203 or 977384 via the PATCH= option in the "Setup Windows and ConfigMgr" task of an OSD Task Sequence, 2509007 appears to fail and the problem described in 2509007 still occurs:

=====

Symptoms

When attempting to install System Center Configuration Manager 2007 (ConfigMgr 2007) hotfix 2509007 along with either 977203 or 977384 via the PATCH= option in the "Setup Windows and ConfigMgr" task of an OSD Task Sequence, 2509007 does not appear to install correctly and the problem described in 2509007 still occurs.

Under the "Components" tab of the ConfigMgr 2007 control panel the "ConfigMgr Software Updates Agent" will show as being updated to version 4.0.6487.2188. However, inspecting the DLL that 2509007 is supposed to replace, Updateshandler.dll, reveals that it has not been replaced and is at version 4.0.6487.2000 instead of version 4.0.6487.2188.

Attempting to rerun the 2509007 hotfix to try and resolve the issue does not fix the problem.

Cause

There original released hotfixes contained MSPs that may cause the issue described. As of June 2011, updated versions of the hotfixes have been released that resolves the issue described.

Resolution

To resolve the issue, the following two actions should be taken:

  1. Uninstall KB977203, KB977384, and KB2509007 from the site server, download the latest versions of these KB hotfixes, and then reinstall the latest versions on the site server.
  2. In the PATCH= statement, ensure that the KBs are installed in the order that they were released.

Please note that both KB977203 and KB977384 are not needed.

Reinstall KB Hotfixes On Site Server

In the below instructions, both KB977203 and KB977384 may be installed or only one of them may be installed. If only one is installed, it is only necessary to reinstall the KB hotfix that was originally installed.

If both KB977203 and KB977384 are installed, KB977384 contains the hotfix found in KB977203, so normally KB977384 is sufficient. However KB977203 may still be desired to be installed since it includes CCMCertFix.exe. KB977384 does not contain CCMCertFix.exe.

  1. On the affected site server, uninstall the KB977203, KB977384, and KB2509007 hotfixes:
    Windows Server 2008 and newer
    1. Open the "Programs and Features" control panel.
    2. On the left pane, click on "View installed updates".
    3. On the right pane scroll through the list of updates and find the section "System Center Configuration Manager 2007".
    4. One at a time double click on KB977203, KB977384, and KB2509007 to uninstall the hotfixes. In the "Windows Installer" dialog box, click on the "Yes" button to confirm uninstalling the hotfix.

Windows Server 2003

  1. Open the "Add or Remove Programs" control panel.
  2. Make sure that the "Show updates" checkbox is checked.
  3. Scroll and find "System Center Configuration Manager 2007".
  4. Under "System Center Configuration Manager 2007" find KB977203, KB977384, and KB2509007.
  5. On each hotfix click on the "Remove" button. For each hotfix navigate through the "Software Update Removal Wizard" to properly uninstall the hotfix.
  1. In the Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Software Distribution" --> "Packages" node, delete any packages that were created by the original install of KB977203, KB977384, and KB2509007.
  2. On the site server where ConfigMgr 2007 is installed, navigate to the directory where ConfigMgr 2007 is installed.
  3. In the ConfigMgr 2007 install directory, navigate into the "Logs" folder and delete the folders "KB977203", "KB977384", and "KB2509007".
  4. In a web browser navigate to the sites for the hotfixes 977203, 977384, and 2509007, and request to download them.
  5. Once the KB977203, KB977384, and KB2509007 hotfixes have been downloaded, reinstall them on the site server. Please note that if installing both KB977203 and KB977384, KB977203 should be installed before installing KB977384.
  6. Update the Distribution Points for the ConfigMgr 2007 client package being specified in the "Setup Windows and ConfigMgr" task of affected Task Sequences.
    Please note that if the data source for the ConfigMgr 2007 client package being specified in the "Setup Windows and ConfigMgr" task is not pointing to the path
    \\<ConfigMgr_Site_Server>\<Site_Code>\Client
    then the ConfigMgr 2007 client package being used will need to be manually updated with the newly installed hotfix MSP files followed up updating the Distribution Points for that package.

Ensure Hotfixes Are Installed In The Correct Order

  1. In the Configuration Manager 2007 Admin Console, navigate to the "Computer Management" --> "Operating System Deployment" --> "Task Sequences" node.
  2. Right click on the affected Task Sequence and choose "Edit"
  3. Click on the "Setup Windows and ConfigMgr" task.
  4. If installing KB977203 and KB2509007, the following line is the correct syntax for the PATCH= option that should be included in the "Installation properties" text window:
    PATCH="C:\_SMSTaskSequence\OSD\<Package_ID>\i386\hotfix\KB977203\SCCM2007AC-SP2-KB977203-x86.msp";"C:\_SMSTaskSequence\OSD\<Package_ID>\i386\hotfix\KB2509007\SCCM2007AC-SP2-KB2509007-x86-enu.msp"
    where <Package_ID> is the Package ID of the ConfigMgr 2007 client install package. Do not include the brackets (<>) as part of the Package ID.
  5. If installing KB977384 and KB2509007, the following line is the correct syntax for the PATCH= option that should be included in the "Installation properties" text window:
    PATCH="C:\_SMSTaskSequence\OSD\<Package_ID>\i386\hotfix\KB977384\SCCM2007AC-SP2-KB977384-x86-enu.msp";"C:\_SMSTaskSequence\OSD\<Package_ID>\i386\hotfix\KB2509007\SCCM2007AC-SP2-KB2509007-x86-enu.msp"
    where <Package_ID> is the Package ID of the ConfigMgr 2007 client install package. Do not include the brackets (<>) as part of the Package ID.

Notes

  • The paths in Steps 5 and 6 may need to be modified if the Task Sequence cache folder (_SMSTaskSequence) resides on a drive other than C:. The Task Sequence cache folder will usually reside on the drive or partition with the largest amount of free space. It is not recommended to use the variable %_SMSTSMDataPath% as part of the path. This variable initially evaluates while in WinPE and its value can change once the Task Sequence boots into the full OS. This may cause the paths to become invalid.
  • Please note that KB977203 or KB977384 are placed before KB2509007. Ensure that that order is correct.
  • If installing KB977384, KB977203 should not also be included as KB977384 includes the hotfix in KB977203.

=====

For the most current version of this article please see the following:

2673515 : Configuration Manager 2007 hotfix 2509007 does not install correctly when installed at the same time as 977203 or 977384

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/