Use Existing WSUS to Patch Client during ConfigMgr OSD Task Sequence

Usually when I go onsite to clients for OSD related projects, once in a while come across those that do not want to adapt to using the Software Update Point (SUP). These clients want the capability for integrating the Software Update process in the Build and Capture as well as the Deployment Task Sequences without SUP.

This is easy to do if you have the MDT 2010 Toolkit packaged.

In the Task Sequence for the Build and Capture (of the Deployment TS)

1. Add the MDT Task Use Toolkit Package

Figure 1

2. Add the task Set Task Sequence Variable. Set the WSUSServer variable to the corporate WSUS.

Figure 2

3. Add the task Run Command Line. Enter the command line as shown below (Figure 3).

Figure 3

One thought on “Use Existing WSUS to Patch Client during ConfigMgr OSD Task Sequence

  1. Hi,

    Just wanted to say thanks for this, it really helped me as we are not interested in using SUP as we have WSUS setup already.

    To get mine working fully I had to add :8530 to the end of the server name (in figure 2). Without the port number it failed on the task sequence.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s