10 Tips for Your Windows 7 Migration

Planning a Windows 7 Migration?
Whether or not a Windows 7 upgrade is inevitable for your organization, it’s almost a guarantee at some point you’ll have to manage a major OS migration. Whenever you’re faced with that battle, there are some key things you need do to ensure success.

1. Plan to be off Windows XP by Year-End 2012 — Microsoft® will support Windows XP with security fixes into April of 2014, but past experience has shown that independent software vendors (ISVs) will stop testing much earlier. “New releases of critical business software will require Windows 7 long before Microsoft support for Windows XP ends,” said Steve Kleynhans, research vice president at Gartner. “Organizations that get all of their users off Windows XP by the end of 2012 will avoid significant potential problems.”

2. Start Working on Migration Projects Now — The typical organization requires 12 to 18 months waiting, testing, and planning before it can start deploying a new client OS. There is a lot of work to be done in preparation, and delays in getting started will only result in added costs later.

3. Don’t Wait for Windows 7 SP1 to Begin Testing and Deployment — Many organizations say they plan to wait until SP1 ships to begin testing and deploying a new client OS. Gartner analysts suggest starting work now (especially if companies have skipped Windows Vista), but are planning to switch to SP1 before their actual rollout.

4. Don’t Skip Windows 7 — Gartner categorizes Windows 7 as a “polishing” release on top of the architectural change that the Windows Vista “plumbing” release delivered. Gartner analysts said polishing releases should never be skipped. Per Michael Silver, vice president and distinguished analyst at Gartner, “While organizations that skipped Windows 2000 and waited for XP had some problems spanning the gap, organizations that adopted Windows 2000 and tried to skip Windows XP, waiting for Vista, had a much harder time.”

5. Budget Carefully — Migration Costs to Vary Significantly — Gartner’s model shows that migration costs could be $1,035 to $1,930 per user to move from Windows XP to Windows 7, and $339 to $510 per user to move from Windows Vista to Windows 7 depending on an organization’s approach.

6. Conduct Reconnaissance: Take stock of your IT hardware and create a comprehensive “map” of your IT environment.

7. Create a Plan of Attack: Determine what hardware and software you need to upgrade, replace, retire, re-lease, and so on so they’re compatible with Windows 7. Also design a rollout plan and timeline that will cause the least disruption to users.

8. Brief those in Charge: Create and present reports clearly outlining required updates before migration; time and budget required for updating and upgrading; and how users will be impacted and when. You’ll also need to produce regular progress reports and updates for stakeholders along the way.

9. Bolster the Troops: No matter how smooth the migration, you will inevitably get calls from users who need help using the new features or can no longer access an non-compliant application. You need to make sure the right service and support tools and staff are in place to handle the increase of incoming inquiries.

10. Deploy: Use tried and true deployment automation tools to rollout Windows 7, with minimal time required by IT staff, and little disruption to end-users.

Visit http://www.itts.com.au/ to Learn More about Windows 7 Training

*This information was originally published in a whitepaper by Numara Software