R3 is the latest feature pack to be released for ConfigMgr 2007 – it is also the first R3 release in Microsoft’s history. The update includes a server side component as well as an upgrade for your ConfigMgr clients. Pushing the update out to your clients is one thing but when it comes to updating your OSD task sequences it gets a little tricky. If you simply attach the update as a install software step or call it from a script during your task sequence the sequence will fail because the R3 update stops the winmgmt service. In order to install the update during a task sequence you must add the correct command line to the installation properties of your ConfigMgr client install step. There are a couple of ways of doing this.
Locate the “Setup Windows and ConfigMgr” step in you task sequence and on the properties tab under Installation properties add one of the following command lines:
PATCH="%_SMSTSMDataPath%\OSD\Package ID\i386\hotfix\KB977384\SCCM2007AC-SP2-KB977384-x86-enu.msp"
Or you might need to specify a drive letter instead of using the SMSTSMDataPath variable
PATCH=”C:\_SMSTaskSequence\OSD\Package ID\i386\hotfix\KB977384\sccm2007ac-sp2-kb977384-x86-enu.msp"
However if you have set the advertisement for your task sequence to access content directly from a distribution point when needed by the running task sequence then you’ll need to change the SMSTSMDataPath variable or your local drive reference to the network location of your R3 patch. Like this:
PATCH=”\\Network Location\ConfigMgr Client Source Files Directory\hotfix\KB977384\sccm2007ac-sp2-kb977384-x86-enu.msp"
