Publishing updates through SCUP from Shavlik

This blog post will show you how to publish 3rd party updates from SCUP through to SCCM and ultimately to your clients.

If you missed it or dont have SCUP setup yet, here is another blogpost on setting up & configuring it.

 This post will cover the following

Assigning And Publishing Software Updates To WSUS

Synchronising SCCM with WSUS

Creating A Deployment Package For Your Software Updates

Verifying Installation On Client Machines

Troubleshooting

Assigning And Publishing Software Updates To WSUS

First open your SCUP console and locate a third party update you wish to deploy. Once you have one right click on it and select Assign

Below I have selected Full Content as I know I want to deploy this right away, but you have the choice of Full content, Metadata, or Automatic.
Metadata and full content are self explanitory, automatic however will not download the content until client machines request it (see my other post here for a look at the thresholds for this)

I just want to point out at this point, that assigning software updates to publications is completely optional. It serves only as a logical grouping of updates, much like updates lists in config mgr. There is nothing stopped you clicking Publish without assigning an update.

Now Select Assign Software update to a new publication, give it a name and press OK

Once done click on Publications from the bottom left and find your newly created publication. You should see that it contains your update. Now hightlight it and click Publish from the ribbon

 This will launch a wizard, be sure to tick the box at the bottom. This will resign any with a new certificate, should your old one expire in the future, very handy indeed!. Once done hit Next

Next again...

Wait for it to download and publish the update, then hit Next

Verify it was successful and click Close

In %temp% you will find scup.log, open it up and wait for the message Publish wizard complete

Now close SCUP. The update has now been sent from SCUP into your WSUS database. If you open your SCCM console you will not yet see this update, you must synchronise your SCCM server with your WSUS database first.

Synchronising SCCM with WSUS

To do this right click on All software updates and select Synchronise software updates

After a successful synchronisation you will see the update in the SCCM console!

Creating A Deployment Package For Your Software Updates

Highlight your software update and click Create Software Update Group from the ribbon

Enter a name for the SUG and click Create

Now if you expand Software Update Groups in the SCCM console you will see your SUG, right click on it and click Deploy

Now fill out the details of the Deployment wizard that launches. Here choose a Collection to target your deployment at and press Next

Fill out these details as you wish then hit Next

  

 Change the time to UTC and if you are in a lab like me or if this is a critical update change the Available time and the Deadline to As soon as possible

Next configure your user experience as you wish. Here you can specify what types of notifications they will see etc. once you are happy hit Next

Configure Ops Mgr alerts as you wish and hit Next

Configure download settings as you wish and click Next

Now to create a Deployment package, Configure yours similar to mine below, giving it a meaningful name and a suitable location. Once done hit Next

Add your Distribution Point(s) or Group(s), and hit Next

Select Download software update from the internet and click Next

Select your language and hit Next

Review the information presented in the Summary and click Next

Now the software update will filter through to any clients in the collection you targeted your deployment at.

Verifying Installation On Client Machines

Given time to filter through, on client machines you should see the update listed in the software Center as shown below and you should be able to install it manually (just to speed things up)

Troubleshooting

if you see this error in your windowsupdate.log file on your client machines:

See my previous blogpost here  and make sure you have configured your GPO correctly and distributed your certificate to your client machines

Wayne