System Center Updates Publisher allows updates from other vendors, including internal products, to be integrated into Configuration Manager Software Updates. In SMS 2003 this capability was known as Inventory Tool for Custom Updates (ITCU). Updates and definitions can be downloaded from select vendors including Dell, Hewlett-Packard, and Adobe. They can also be created through editing tools to support products from other vendors and ones developed internally.
Read the complete
documentation before planning your implementation. Key points include:
- Install SCUP from the SCCM media or download separately
- Create a certificate used to sign updates (if one doesn't already exist on the updates server) and copy it to all clients that may use SCUP updates
- Configure other security requirements as needed
- Select the vendors and products you want to support, and add their catalogs to the Import list
- Many can be defined in SCUP, so it will automatically check for new updates
- Some vendors, such as Adobe, require licensing their SCUP catalog and downloading it manually
- Select desired updates and publish them
- This downloads the source file to the WSUS server and makes the update available through SCCM Software Updates, just like any Microsoft updates
- SCUP updates can be deployed with Microsoft updates in a normal monthly security update deployment or separately, using the usual Software Update Deployment process
- Vendor and product names become available in Search Folders and other functions after corresponding updates are published
The recommended upgrade process is:
- Download WSUS 3.0 SP1 from Microsoft Downloads.
- Install WSUS 3.0 SP1
- Disable the SUP component in SCCM, and apply that change
- Wait for update activity to complete
- Enable the SUP component using standard settings including ports 8530 & 8531, and apply that change
- Wait for resynch to complete. This took eight hours on my test system, so prepare to run this overnight if you have more than a few updates already in WSUS.
NOTE: Todd Hemsell found the solution to the bug in downloading SCUP updates reported here previously. Just select to download the updates from the local folder where they are created when published:
- Download desired catalogs from Microsoft or vendors
- Download SCUP updates from a loction on the local network:
- Select the proper location: