Many of us try to enable as few categories as possible in ConfigMgr for software updates synchronization. You may encounter a need to deploy an update from a classification or product you don’t normally synchronize. To accomplish this task, you could choose one of the following:
Follow these steps to import an update from the Windows Update Catalog:
Happy Patching!
- Create a standard Package/Program/Advertisement, which means you will have to take care of proper targeting
- Modify the Software Update Component on your central site to allow synchronization of the new classification and/or product, but then you may end up synchronizing a lot more than you did previously.
- Use System Center Updates Publisher (SCUP) to create deployment rules. This would work great, but requires additional effort on your part also.
- Use the Windows Update Catalog to import the update. This works great for many reasons: 1) it requires the least effort, 2) has the least database bloat, 3) will handle the detection rules for you, and 3) deploy like a ‘normal’ Microsoft Update, giving you the best end-user experience possible.
Follow these steps to import an update from the Windows Update Catalog:
- From your ConfigMgr Central Site server, launch the Windows Server Update Services console.
- Expand the tree to “Updates”, then select “Import Updates” from the action pane. This launches the Microsoft Update Catalog in your web browser (internet access required).
- Search by keyword, KB number, or even plug-and-play ID!
- Click “Add” on desired updates:
- Click “View basket”
- Click “Import” – this action imports the update into your top WSUS Server for ConfigMgr.
- From ConfigMgr, launch the “Run Synchronization” action on the ConfigMgr Update Repository node.
- Select and deploy updates as you normally do.
Happy Patching!
No comments:
Post a Comment