1 / 11

Ben Berry Chief Information Officer Oregon Department of Transportation July 19, 2010

Microsoft Windows 7 A CIO Council Drill Down Discussion ODOT 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

oshin
Download Presentation

Ben Berry Chief Information Officer Oregon Department of Transportation July 19, 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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

  2. 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

  3. ODOT Tech Roadmap Timeline

  4. ODOT Windows 7 Project Schedule Overview

  5. 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.

  6. 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.

  7. 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.

  8. Risks and Assumptions (cont’d) • Ability to port in-house applications. • Customer acceptance. • Service interruptions to the business.

  9. Windows XP: Applications Testing Framework A Providence Health System Approach

  10. Windows XP Compatibility Research Results A Providence Health System Approach

  11. 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:ben.berry@odot.state.or.us]

More Related