Layout plan to implement patches

we have windows server 2008 ad ds workstation using windows 7 , legacy system lay around.

my background in development , i'm been reassigned work in security policy implementation , netwrok security configuration settigns.

in last month, have noticed fear on management's face when comes behind in security policies demanded government. last month had upgraded of internet browser (i9) , bunch of user turn-out either block sites or missing internet settings. heard month before when upgraded adobe, encounter conflict settings security policies , prior month have problems implementing security patches microsoft.

my question forum, there impementation guide wehm comes addding patches...

obviously test first, sounds when come implement in production encounterproblems didn't show-up in development.

i know how works....... new policy objects are upgraded in security patches microsoft?

are there guidelines companies can follow reduce burden , keep-up auditors inspections from governements in implementing policies?

any suggestion appreciate!!!!

---

michael john ocasio

hi,

above poster provided method test gpo, it’s common test process.

test cases documentation of procedures, targets, , expected results each individual test performed. when building list of test cases patch, include each of the specified test-case types.

types of tests cases

• installation tests—to validate patch installs without error, , launch conditions contained in windows installer patches working properly.
• verification tests—to verify shortcuts, files, , file associations set or modified patch working properly.
• execution tests—to verify whether files , registry keys created or modified patch can read , updated when application executed typical users not have administrator-level privileges.
• standard tests—to verify installation of patch not negatively impact ability execute application found on desktop or ability connect url, network share, or database.
• rollback tests—to verify safe method of uninstalling patch and/or restoring target computer pre-patch state in event of conflict.

lab testing

initial patch testing should performed on non-production computers. facilitate adequate testing of automatically deployed patches, organizations should use standardized configurations devices as possible. popular technique leverage virtual machine technology provides rollback capability facilitate rapid testing , retesting against common workstation , server configurations.

pilot testing

roll out patches 1 or more pilot groups. discussed, pilot groups should focus on commonly used configurations in production environment.

good pilot groups readily accessible staff in event of failure, computers assigned more technically savvy users, , computers least impact primary business functions of organization in event of failure.

after comparing differences between pilot testing , earlier testing phases, develop rollout plan addresses observed issues. recommended technique of multi-phased rollout discussed under software update rollout strategies section of document.

for more information please refer following articles:

patch management best practices
http://www.symantec.com/business/support/index?page=content&id=howto3124
patch management
http://www.foxit.net/common/white%20papers/patch%20management.pdf

---

lawrence

technet community support

Windows Server  >  Group Policy