Hi, I've just upgraded a clients infrastructure to R3 and have rolled out the KB977384 patch to the existing SCCM client infrastructure. My client uses OSD for build deployment and obviously the build task sequence installs the configmgr client. After applying the KB977384 hotfix to the infrastructure a new 'hotfix' directory has been created under the client\i386\ which contains the .msp patch. This is the source I've used to roll out the patch to the existing clients. The problem I have is when new clients are installed as part of the build task sequence, even though I use the same source as above the clients install at version 4.00.6487.2000 instead of 4.00.6487.2157. This would indicate that when ccmsetup is ran it does NOT install any patches that are located in the 'hotfix' directory as I would have expected it to. We then have to deploy the KB977384 patch post build, which is hardly ideal. Applying the patch seperately through the build TS causes it to fail as installation of this patch shuts down the ccmexec service, causing the TS to fail. My question is how can the source for the client install be updated to include this patch with the normal install routine? Can this patch be applied directly to the the existing client.msi install files? I wouldn't have thought so... Cheers, Stephen

You can use the PATCH property as described near the bottom in KB977203: http://support.microsoft.com/kb/977203.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Jason, Thanks for this, looks promising, I'll give it a test.... Don't see this documented anywhere in the Technet library for client installation properties. Is there OSD docs covering this? Cheers, Stephen

No, it's standard/built-in MSI installation capabilities though. There are a couple of other links on the web (that I can't find right now) talking about this also including ones from the ConfigMgr team. Another possibility is to use SCUP: http://myitforum.com/cs2/blogs/jsandys/archive/2010/11/06/configmgr-client-hotfixes.aspx. Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Is this update needed on the clients? I have upgraded the servers to R3 but have not updated the clients..

Which update are you talking about? The hotfix (installed on a primary) creates a new ConfigMgr package and that has to be used to upgrade the clients.

I have read that you need it when you want to use powermanagement.. else you can skip it..

I have read that you need it when you want to use powermanagement.. else you can skip it.. Absolutly you're right. So, if you don't want to install that hotfix on client machines, therefore what is your worry now please ?Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/default.aspx

Hmm just asking.. No worries at this time..

Here is a good atricle about applying patches as part of the ConfigMgr client install step in an OSD task sequence. http://blogs.technet.com/b/deploymentguys/archive/2010/08/13/automatically-populate-the-patch-property-for-the-configmgr-2007-client-installation.aspx Be sure to click on the "how to" link too to have some screenshots of the whole process. I just implmented the patch this way in my OSD and it works great.