Windows XP Service Pack 2 (SP2) Support Advisory Center

Best practices and Guidelines for Deployment of Windows XP SP2 Step 4 - Test, Deploy, and Test Again Pre-Deployment Testing - Nothing substitutes for testing before deployment if it is practical. Pre-Deployment testing can help validate your findings from the impact assessment phase, particularly if you documented where you expected to find an impact Not everyone has the luxury of additional hardware and systems for testing before deployment, that is a reality of life If a test environment is available, use it to test deployment of XP SP2 and applications before you actually deploy in production. Whether a test environment is available or not, you may want to have your first production rollout of XP SP2 be on machine(s) where if problems occur with the rollout, the impact on your ongoing operations is relatively low while you work out the issues. Consider picking a "pilot test area" to be the first area you rollout XP SP2 on. When it is time to deploy Be methodical If something doesn't look right, think before charging ahead If there are problems, change one variable at a time and retest the affected behavior. Your chances of resolution are better if you approach the problem one step at a time. Post-Deployment Testing Focus on the areas you identified in the impact assessment phase and documented. Disclaimer: The information contained in these pages is based on our testing with the release candidate of XP Service Pack 2. Although this information is based on "best practices" as judged by the authors, Software Toolbox and the authors of this document assume no responsibility or direct, indirect, or consequential liability for its accuracy or suitability for a users particular application. The reader is responsible for proper application to their particular situation.

| Home | XPSP2_BestPractices | XPSP2_DCOMSetup | XPSP2_ProductStatus