Automatically Populate the PATCH Property for the ConfigMgr 2007 Client Installation

re: Automatically Populate the PATCH Property for the ConfigMgr 2007 Client Installation

Ian Broadbent — Mon, 29 Apr 2013 02:07:06 GMT

Thanks for the script, it's much better than having to manually specify each hotfix . I found though, that the script is configured to look on the server for all available patches (I had applied a dozen or so patches to the server, some superceded others). This caused me an issue because of the same files being updated by different hotfixes as described by Mark above. I only wanted a few client hotfixes that I had in my client file-set to apply. So I just commented out the four lines below in the script to stop it looking on the server (for the dozen or so hotfixes I had applied):

' ElseIf UCase(oEnvironment.Item("_SMSTSMediaType")) <> UCase("FullMedia") then

' sHotFixFolder = oEnvironment.Item("DeployRoot") & "\hotfix"

' bCopyFolder = True

' oLogging.CreateEntry "Running in ConfigMgr OSD Online, SCCM... hotfixes copied to : " & sHotFixFolder, LogTypeInfo

The script then successfully applied the four hotfixes I had in the client file-set which were, for the record:

KB2750782 (Client-side update is KB2698619) - supersedes KB977384

KB2659258 Asset Intelligence roll-up

KB2815223 Fix for boot image error

KB2509007 Fix for many updates stops Task Sequence

re: Automatically Populate the PATCH Property for the ConfigMgr 2007 Client Installation

Todd Miller — Mon, 27 Aug 2012 17:30:34 GMT

Might as well link to the updated community WSF that puts the patches in the correct order...

myitforum.com/.../automatically-populate-the-sccm-client-patch-property-during-osd.aspx

re: Automatically Populate the PATCH Property for the ConfigMgr 2007 Client Installation

Mark Allcock — Fri, 15 Apr 2011 10:19:42 GMT

Hi Michael

I've been using this script for a while now and I have to tell you it's saved me so much aggrevation when trying to populate the PATCH property by hand. It’s very dynamic too just in case you install more hotfixes in Configuration Manager.

I have, however, stumbled across a problem with the order in which the hotfixes are detected…

We deploy the following hotfixes to our client systems:

• KB977203

• KB977384

• KB978754

• KB979199

• KB2444668

Your script populates the PATCH property in the following order because of the way Windows sorts the hotfix folder structure:

KB2444668, KB977203, KB977384, KB978754, KB979199

CCMSETUP fails to install with an error 1635 and ‘Client.msi.Log’ reports “ERROR: Attempting to install downlevel patch for feature SmsInventory. Rejecting patch and aborting install.”.

Clearly, two hotfixes replace the same SCCM component and the older one (KB979199, I assume) cannot overwrite the newer (KB2444668, I assume).

If I specify the PATCH property in the following order, it works!

KB977203, KB977384, KB978754, KB979199, KB2444668

I know you are limited in your available time, so a colleague and I are going to edit the script to present a logical order to the PATCH property so that recent KB2xxxxxx (7 digit) hotfixes appear nearer the end in their order of release. I will get back to you with results if successful.

Mark Allcock

re: Automatically Populate the PATCH Property for the ConfigMgr 2007 Client Installation

Michael Murgolo — Tue, 22 Feb 2011 21:48:57 GMT

Markus,

You would need to add logic to the script to either detect the conditions when this happens (i.e. partition configuration, etc.) or set a task sequence variable on refresh and then change the drive letter in the PATCH property or move the files so that it's correct when the OS is up and running.

Unfortunately, I don't have the time to solve this problem now. If you find a solution that works for you, post a comment back here.

Michael Murgolo

re: Automatically Populate the PATCH Property for the ConfigMgr 2007 Client Installation

Markus Lindgren — Tue, 22 Feb 2011 13:53:22 GMT

This works fine for me when running in New Computer scenario (F12 to PXE boot and run task sequence). When doing a Refresh scenario and starting the task sequence from an OS, the patches are downloaded to the d: drive and the PATCH property points to d: path. The SCCM client installation task sequence step reboots the computer automatically and installs the SCCM client from c: drive. The d: path where the PATCH property points to is not found. Any suggestions on how to fix this?

System Center Configuration Manager (ConfigMgr) – Automatically Populating The PATCH Property

Chris Nackers Blog — Sun, 29 Aug 2010 03:40:13 GMT

I had previously blogged about a script created by Michael Murgolo over on TechNet . I wanted to now

Configuration Manager (ConfigMgr) – Automatically Populating The PATCH Property

Chris Nackers Blog — Fri, 27 Aug 2010 19:41:30 GMT

I had previously blogged about a script created by Michael Murgolo over on TechNet . I wanted to now

Automatically Populate the PATCH Property for the ConfigMgr 2007 Client Installation

Chris Nackers Blog — Tue, 24 Aug 2010 23:23:09 GMT

Another great post by Michael Murgolo over on TechNet for automating the ConfigMgr client PATCH property