Managing 3rd Party Updates in SCCM 2012 using SCUP
This guide will show you how to deploy 3rd party updates alongside Microsoft Updates via SCCM using SCUP plus software update catalogs
Before SCCM may deploy 3rd party updates, we must first get them into SCCM. Here’s how…
For the examples in this guide, we will be publishing Google Chrome 45.0.2454.85
1. Launch SCUP (Systems Center Updates Publisher) 2011 from the SCCM Primary Server
2. Update the Catalogs
Before importing anything, we must update the catalogs by importing them which takes about 10-15 minutes. This doesn’t have to be done each time you publish, but suggest doing so if no one has done it in the past 24 hours. This ensures that the source we select from has the latest updates.
a. In the ribbon bar at the top, click on the “Import” button
b. Place a check in the top-most checkbox to select all options, then click Next
c. At the confirmation screen, click Next once more to confirm the selection and the import will begin. If prompted asking if you trust the publisher listed, select “Always Accept…” then click Accept
d. Once the catalogs have been imported, click OK to return to the main screen
3. In the left column, browse to the folder of the updates publisher then locate the update you wish to publish to SCCM
4. Right click on the update and select “Publish”
Important Note: You can also add updates to Publications (Group of Updates) by right clicking the updates and choosing assign and creating a Publication group. You can publish these groups all at once.
5. The window which appears will have 3 primary choices: Automatic, Full Content, and Metadata Only. Since we want the update files to be downloaded and stored in SCCM alongside Microsoft updates so that it’s ready to deploy, select “Full Content” then click Next
6. Click Next in the “Publish Software Update” Wizard. A progress bar will appear as the update(s) are downloaded and added into SCCM. During this process, you may be prompted with a Security Warning asking if you wish to accept this content. If so, select “Always Accept…” then click “Accept”. Note: If the vendor does not digitally sign their content, you will have to do this every time you Publish or import the catalog
7. Once complete, the window will display how many updates were selected for publishing and how many were published with full content. If the numbers on both lines match, then the Publish was successful. Click Close
Important Note: If there are any issue during Publishing, the SCUP log may be checked which is located at %temp%\scup.log.
Handling the Update Within the SCCM Console
8. Launch the SCCM Console, browse to “Software Library” then expand the “Software Updates” folder
9. Right click “All Software Updates” at the top of the folder then choose “Synchronize Software Updates.” When prompted to verify that you want to run synchronization, choose “Yes”
Once the sync finishes, you should now see the new updates available within the SCCM Console and they will be available for deployment! If you do not see the update after the synchronization completes, see the section named “Vendor Specific SCCM Configuration“ below.
Vendor Specific SCCM Configuration
The First Time you Publish an Update for a Manufacturer which you haven’t ever published from before, it may not appear after the initial synchronization. Here’s how to resolve this issue…
- Using the steps in prior sections, publish the desired update and perform the Software Update Synchronization in the SCCM console
- Confirm that the synchronization is complete and that the update does not appear before continuing
- In the SCCM console, browse to the “Administration” section
- Expand “Site Configuration”, then select “Sites”
- Right click on the site in the main pane, select “Configure Site Components”, then “Software Update Point”
- Select the “Products” tab
- You should see the manufacturer of the update which failed to appear and perhaps the product name underneath it as shown below. Check both boxes for the manufacturer and product, click Apply, then OK.
- Rerun the Software Updates synchronization as described in step #9 in the section above. Once it completed again, the update(s) will appear
Publishing Multiple Updates at Once with “Publications”
More coming soon…