SCTOTD: 10 Patch Management Principles to Live By


When utilizing the update management features in Configuration Manager 2007 or Essentials 2010, in addition to the best practices, your strategy should be developed with these foundational principals from Microsoft in mind. Using all the information at hand and MS knowledge from the field can help you to minimize effort and risk of impact to service delivery.

10 Principles of Patch Management

1. Service packs should form the foundation of your patch management strategy

2. Make Product Support Lifecycle a key element in your strategy

3. Perform risk assessment using the Severity Rating System as a starting point

4. Use mitigating factors to determine applicability and priority

5. Only use workarounds in conjunction with deployment

6. Issues with Security Updates are documented in the Security Bulletin Master Knowledge Base Article

7. Test updates before deployment

8. Contact Microsoft Product Support Services if you encounter problems in testing or deployment

9. Use only methods and information recommended for detection and deployment

10. The Security Bulletin is always authoritative

Read More

Read more about the 10 principals of patch management at

For more on ConfigMgr patch management procedures, see

Previous Installments

May 15, 2010 – SCTOTD: Tips for Deep Analysis of Community Management Packs

May 14, 2010 – SCTOTD: Leaving an Audit Trail of Update Management Activity in ConfigMgr 2007

Follow System Center Central


Sponsors and Supporters

Quest | Veaam | System Center Influencers

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.