Microsoft Windows 7 A CIO Council Drill Down DiscussionODOT Information Systems Branch Ben Berry Chief Information Officer Oregon Department of Transportation July 19, 2010 http://www.oregon.gov/ODOT/CS/ISB/cio_report.shtml
ODOT Windows 7 Business Case • Microsoft announced the end of life for Windows XP support as of April 8, 2014 • Anticipated waning of third-party application support for Windows XP beginning in late 2011 and accelerating though 2012 as identified by Gartner
ODOT Tech Roadmap Timeline
Key Considerations • Volume Licensing (VL) strategy - Microsoft policy requires the activation of all editions of Windows 7, including those obtained through a VL program • Windows 7: 32-bit or 64-bit – What O/S will your applications work with best • Deployment method. Mass rollout, slow rollout, or just install on new machines through PC lifecycle replacement? • Deployment tools - Microsoft has some nice tools to help with a Windows 7 migration. • Windows XP Mode – Requires the Virtual PC image kept up to date with security patches etc.
Key Considerations (cont’d) • Training - technicians and end users will require training • XP support - 2014 was the original end of life date for XP. Lessons learned - Leverage your XP migration project documentation. • In-House applications - Coordination between desktop support group and application development to ensure applications work with new operating system. • Resources - Use Gartner Research for project costing and scheduling.
Risks and Assumptions • Commitment. Securing commitment and resources from technical and business leaders. • Lack of adequate technical training may impede the effectiveness and quality of decisions made throughout the prototyping of a Windows 7 build and the subsequent evaluation. • Federal. Federal requirements may determine need for a mixed environment. • Evaluation Process. Availability and inclusion of Office 2010 may delay the evaluation process. • Funding. Lack of available funding to upgrade incompatible hardware and software. • Critical Application compatibility.
Risks and Assumptions (cont’d) • Ability to port in-house applications. • Customer acceptance. • Service interruptions to the business.
Windows XP: Applications Testing Framework A Providence Health System Approach
Windows XP Compatibility Research Results A Providence Health System Approach
Microsoft Windows 7 A CIO Council Drill Down This presentation was supported by Jessica Tucker, second year MBA student and ODOT IS Business Systems Intern. For information contact Ben Berry at [Mailto:email@example.com]