SCCM 2012 – Updating SCCM client during TS

SCCM 2012 – Updating SCCM client during TS

Hi All,

for ages, i’ve being using a script to automatically populate the PATCH option of the SCCM client installation in a TS environment. the reason i’ve been using this script (if not clear for you), is the number of hotfixes and the allowed size of the text box on a TS…

fortunately with SCCM 2012, the SCCM product group changed the way they di hotfixes and started to use Updates Rollup, meaning that you would not find the issue we’ve been experiencing on SCCM 2007.

Even it is true, Microsoft had to release few updates out of the Update Rollup and people don’t know how to manage them in a Task Sequence as this has changed a bit.

Fortunately (again), the script has been updates to SCCM 2012 (http://blogs.technet.com/b/deploymentguys/archive/2013/06/04/automatically-populate-the-patch-property-for-the-configmgr-client-installation-script-update.aspx) however, what happen if you don’t have the ZTIUtility.vbs or don’t want do the MDT integration? Well…you need to do it manually…

the bellow steps are only guidance of what i normally “tend” to do on customers.

1- Create a hotfix folder inside the \client folder
2- copy the client hotfix (from the \hoftix\ folder) to the hotfix folder you created inside the \Client
**Note that in this example i’m only worried about the x64 updates 🙂
3- Update the Distribution Point of the DEFAULT Client Package. This package has the ID as 00002 (Of course you can do it on another package, but remember to change the TS for the new package). Make note of it as we’ll be using it on the next step. In this example, it will be RFL00002
4- Once you do that, in your task sequence, step Setup Windows and ConfigMgr add the following PATCH property at the end
PATCH=”%_SMSTSMDataPath%\OSD\RFL00002\Hotfix\configmgr2012ac-r2-kb2910552-x64.msp;%_SMSTSMDataPath%\OSD\RFL00002\Hotfix\configmgr2012ac-r2-kb2928122-x64.msp”

As you can see, we’re installing 2 hotfixes (kb2910552 and kb2928122), but what exactly is the _SMSTSMDataPath?
It is a ts variable that specify the temporary directory for the TS stuff (ie. packages, etc)

well…that’s it. next time you deploy a new OS, it will be installed with the hotfixes you specify on the PATCH line.

but remember, test before because if you don’t test the task sequence can fail. on SCCM 2007 if you deploy a 2 MSP’s and one superseded the other, the TS would fail.

About

Raphael is a 9 times Microsoft MVP with over 20 years of experience in IT, in which 13 years have been dedicated to System Center and Automation. His extended experience has been developed through several IT roles, from first-line support to principal consultant, towards a wide range of clients and sectors. One of the four MVPs in Enterprise Client Management in the UK, Raphael holds more than 30 Microsoft certifications and is an MCT (Microsoft Certified Trainer). Since 2008, Raphael has been providing Microsoft trainings from basic to advanced levels in several categories. Throughout his career, Raphael has joined as speaker in well-known events such as TechEd and Gartner Security Risk Management. He also organised community events and lectured around the world, sharing best practices and knowledge within the industry. Bilingual in English and Portuguese, Raphael has authored diverse articles published in Microsoft's TechEd, served as the editor-in-chief of a magazine focused on System Center in Brazil and wrote two books: "Understanding System Center 2012 SP1 Configuration Manager: The walkthrough book" and "System Center 2012 R2 Configuration Manager: Automation from Zero to Hero".

Tagged with: , , , , , ,