Superseded Updates
A common issue in ConfigMgr 2007 is dealing with superseded updates. Some organizations with a rigorous configuration control process do not allow new updates for immediate deployment to the enterprise. However, when Microsoft publishes new updates that supersede older updates, you have a “Catch 22” situation: ConfigMgr does not allow deployment of the older superseded updates, but the organization’s strict configuration policy does not allow deployment of the new updates.
System Center 2012 Configuration Manager addresses this issue by the choice made on the SUP’s configuration known as supersedence rules, described fully in the “Software Update Point Placement” section.
Get System Center 2012 Configuration Manager Unleashed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
