Using ZTIWindowsUpdate.wsf To Install Updates In A System Center Configuration Manager Task Sequence
There are instances were you may want to install updates during a ConfigMgr Task Sequence without using Software Updates in ConfigMgr. Maybe you don’t have it implemented yet, or maybe you are still using WSUS for updates. I’ve seen it asked many times if there is a way to pull updates from WSUS during a ConfigMgr TS, so I just wanted to show you a few ways to handle this situation.
Using ZTIWindowsUpdates.wsf in a ConfigMgr Task Sequence
You can use ZTIWindowsUpdate.wsf in a non-MDT integrated task sequence without very much configuration at all. It basically consists of using the ztiwindowsupdates.wsf script and setting a WSUSServer variable.
In order to use the ztiwindowsupdate.wsf script, we also need to have ZTIUtility.vbs available to the script. So first, lets create a package called “ZTIWindowsUpdate” that contains the ztiwindowsupdate.wsf and ztiutility.vbs script.
Next, we’ll need to add a few steps to our task sequence. First we need to set a value for a variable “WSUSServer”, this tells it what WSUS Server to contact for the updates. This is a Set Task Sequence Variable step.
Next we need to add a step to call the ZTIWindowsUpdate.wsf script. This is a Run Command Line step.
We need to make sure that we reference the package we created earlier containing the ztiwindowsupdates.wsf and ztiutility.vbs scripts.
Using ZTIWindowsUpdates.wsf in a MDT-Integrated Task Sequence
You can also use the script in a MDT integrated Task Sequence. In order to do this, we need to set the variable for WSUSServer and add a Run Command Line step to call the script.
First, you can set the variable in the Task Sequence, OR you can set the variable in your setting package that contains customsettings.ini
Setting the value using customsettings.ini
Setting the value using a Set Task Sequence Variable step
Next we need to add a Run Command Line step to call the script. We don’t have to specify a package for this because the script already exists in the Toolkit Package \scripts directory. (The Use Toolkit Package task sequence step specifies the package that contains the MDT scripts)