SCCM KB977384 Install Notes

I’ve been working on an System Center Configuration Manager server for quite some time now. One hitch I ran across was not being able to find the KB977384 installation notes on the internet or the local system once the hotfix is deployed. I’ve reinstalled the hotfix in my dev environment, copied the text, cleaned up the line breaks, and pasted the notes here in case someone else was looking as well :).

Hotfix Link and Description: KB97738 – Description of the prerequisite hotfix for System Center Configuration Manager 2007 R3.

=======================================================
Applying hotfixes to Configuration Manager 2007 Clients
=======================================================

Read this completely before you attempt to apply the Windows Installer .msp file to Configuration Manager 2007 clients.

This hotfix package may include a hotfix to one or more Systems Center Configuration Manager 2007 (ConfigMgr) client components. The ConfigMgr client is not automatically updated after the hotfix has been applied to the site server. To apply the hotfix to ConfigMgr clients in your environment, the .msp file that is supplied with this package must be applied to each client computer. You can use the software distribution  feature of ConfigMgr, manually apply the hotfix, 
or use another method of your choosing to deploy the .msp file to computers in your environment. If you choose to use software distribution to apply the .msp file, you can target a program that installs the hotfix to systems based on their client component version reported in hardware inventory.


-------------------------------------------
To deploy the client .msp by using Configuration Manager software distribution:
-------------------------------------------

NOTE: If during installation of the hotfix package to the site server you chose the option of having a package and program created for you, begin with step 10 to create distribution points for the existing package.

1. In the Configuration Manager console, create a new package. The "Package Properties" dialog box appears. In the Name box on the General tab of the Package Properties dialog box, provide a name that describes it as a hotfix for the ConfigMgr client and identifies the ID number of the associated Knowledge Base article.
2. In the "Package Properties" dialog box, on the "Data Source" tab, in the "Source directory" box, specify the folder where the hotfix was installed by the hotfix installer. The default location is: 
\\<siteserver>\sms_<sitecode>\client\<platform>\hotfix\<updateid>

Where:
<siteserver> is the name of the ConfigMgr site server
<sitecode> is the site code of the site
<platform> is the processor type, e.g. I386
<updateid> is the ID number of the associated Knowledge Base article
==========================================
Example: \\Server1\SCCM_123\client\I386\hotfix\KB891073

Additionally, to ensure accurate status is reported back for the application of the client hotfix, the MIF file name must be specified in the "MIF file name" field of the Reporting tab.  For example, if the .msp file is named: "SCCM2007AC-KB891073-x86.msp" you would enter: "CMclient.SCCM2007AC-KB891073-x86.mif" (without the quotes).

Because the application of this hotfix on a client computer stops and restarts the SMS Agent Host service, it cannot monitor for an exit code from the update and must rely on finding a matching status MIF after the service is restarted.  
If a matching MIF is not found, the status will be reported to ConfigMgr as a failure (1603) even though the update may have completed successfully.

3. Click "OK" to accept the other default package settings.
4. Under the new package, create a new program. The "Program Properties" dialog box appears. On the "General" tab, in the "Name" box, enter a name that describes it as a hotfix for the Configuration Manager client. 
5. In the "Program Properties" dialog box, on the "General" tab, in the "Command line" box, specify the following: Msiexec /p <filename> /L*v <logfile> /q REINSTALL=ALL REINSTALLMODE=mous

Where: 
<filename> is the file name of the .msp file provided with the hotfix package. Typically, the file name is in the form: SCCM2007AC-<articleID>-<platform>.msp
<logfile> is the path where the results should be logged

Example: msiexec.exe /P SCCM2007AC-KB891073-X86.msp /L*v %temp%\SCCM2007AC-KB891073-X86.log /q REINSTALL=ALL REINSTALLMODE=mous

Specify for the program to run minimized and set the "After running" option to Program restarts computer. 

6. In the "Program Properties" dialog box, on the "Requirements" tab, set the "Maximum allowed run time" to 20 minutes. This will prevent the installation from blocking other software distributions if a problem occurs.
7. In the "Program Properties" dialog box, on the "Requirements" tab, choose the operating system version on which you want to install the client hotfix.
8. In the "Program Properties" dialog box, on the "Environment" tab, select program can run "Whether or not a user is logged on."
9. Click "OK" to accept the other default program settings.
10. Under the new package, select distribution points for the new package.
11. In the Configuration Manager console, create a new query to identify systems that need the .msp. This is a sample query that you can adapt to your environment:

select *  from  SMS_R_System inner join SMS_G_System_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ClientType = 1 and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Name = "<COMPONENT_NAME>" and (SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version < "2.50.2726.xxxx" or SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version in ( "2.50.2726.4", "2.50.2726.5", "2.50.2726.18", "2.50.2726.1", "2.50.2726.16" ))

Where: 
<COMPONENT_NAME> is the name of the component to be updated

COMPONENT_NAME
	(Display Name)
------------------------------------------
CcmFramework		
	(CCM Framework)
CcmPolicyAgent		
	(CCM Policy Agent)
CcmStatusAgent		
	(CCM Status and Eventing Agent)
SmsClient
	(SMS Client Core Components)
SmsCommon
	(SMS Client Shared Components)
SmsInventory
	(SMS Inventory Agent)
SmsRemoteTools
	(SMS Remote Tools Agent)
SmsSoftwareDistribution	
	(SMS Software Distribution Agent)
SmsSoftwareMetering
	(SMS Software Metering Agent)
SMSSourceUpdateAgent
	(SMS Source List Update Agent)


<XXXX> is the hotfix build number provided in the hotfix Knowledge Base article.

Note that the query includes a static list of client versions that were shipped with the original release which do not include leading zeros in the hotfix version field (e.g. .0004 versus .4). For the query to be accurate, you should include these versions.
12. Create a collection based on the query that you created in step 11. Limit this query to a pilot group of systems.
13. In the Configuration Manager console, create a new advertisement. The "Advertisement Properties" dialog box appears. On the "General" tab, in the "Name" box, enter a name that describes it as a hotfix for the Configuration Manager client.

14. In the "Advertisement Properties" dialog box, on the "General" tab, select the package that you created in step 1, the program that you created in step 4, and the pilot collection that you created in step 12. 
15. In the "Advertisement Properties" dialog box, on the "Schedule" tab, create a new mandatory assignment. Assign it to run more frequently than your hardware inventory collection schedule. For example, if your hardware inventory is collected once per week, use a schedule more frequent than once per week. This will ensure that the hardware inventory that includes the ConfigMgr client version information is up to date.
16. Click "OK" to accept the other default advertisement settings.
17. Test the hotfix deployment to the pilot group.
18. When the pilot deployment is successful, expand the target to deploy to all the clients that require the hotfix.

------------------------------------------
To deploy the ConfigMgr client .msp by using a method other than ConfigMgr software distribution:
------------------------------------------

Use the following command line:
Msiexec /p <filename> /L*v <logfile> /q REINSTALL=ALL REINSTALLMODE=mous

Where: 
<filename> is the file name of the .msp file that is provided with the hotfix package. Typically, the file name is in the form: SCCM2007AC-<articleID>-<platform>.msp
<logfile> is the path where the results should be logged

Example: msiexec.exe /P SCCM2007AC-KB891073-X86.msp /L*v %temp%\SCCM2007AC-KB891073-X86.log /q REINSTALL=ALL REINSTALLMODE=mous
Advertisements

2 thoughts on “SCCM KB977384 Install Notes

  1. Pingback: SCCM 2007 Single-Server Install Process (part 1) « windowsmasher

  2. Pingback: Table of Contents | windowsmasher

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s