A Roadmap for Success

1

• Migrating to Windows XP Pro
• A Roadmap for Success
• Patrick Fisher

2
OVERVIEW

• Introduction and Assumptions
• Business Drivers
• Stages
• Scope and Objectives
• Value Proposition
• Planning
• Development
• POC/Pilot
• Deployment
• Post-Implementation
• References
• Questions

3
INTRODUCTION
A Continual Process
Prepare
Manage
MIGRATION
Plan/Build
4
ASSUMPTIONS

• Currently on Windows 9.x/NT
• Independent of Existing NOS
• Already Decided on Windows XP Pro
• Project Not Yet Greenlighted
• Already Decided on a Clean Install, Not Upgrade
• Todays Roadmap Aimed at the Project Manager,
  Not Engineering

5
ASSESS THE DRIVERS
Lower TCO Increase
Revenue

• Reduce IT Costs
• Increase Reliability/Stability
• Increase Supportability
• Standardization
• Predictability
• Consistency
• Manageability
• Compatibility

• Increase Productivity
• More Functionality
• More Competitive
• Internal AppDev
• Faster Rollout/DR
• More Collaboration
• Better Communication

6
SCOPE AND OBJECTIVES
Determine the Vision and Goal

• Evaluate the Technology - Windows XP
• Turn Business Drivers into Measurable Objectives
• Map the Benefits of Windows XP to the Objectives
• Corporation
• IT
• Business Units

7
SCOPE AND OBJECTIVES
Determine the Vision and Goal

• Get a Baseline of These Factors and Objectives in
  the Current Environment
• Formulate Initial Cost/Benefit Analysis
• Use MS Deployment ROI Calculator
  -http//66.111.222.105/windows/environment.asp
• Determine Realistic Project Scope
• Establish Checkpoints and Milestones
• Perform Initial Assessment of Environment
• Create a Preliminary Project Plan

8
THE VALUE PROPOSITION
Must Convince Upper Mgmt to Invest

• Competing Against Other Projects
• Find Executive Champion
• Get Key Business Unit Sponsorship
• Demonstrate
• Understanding the Companys Business, Not Just
  Technology
• How Windows XP Will Improve Tasks, Workflow,
  Functions, and Processes
• Cost/Benefit Analysis Economic Justification
• Preliminary Project Plan

9
THE VALUE PROPOSITION
Must Convince Upper Mgmt to Invest

• Set Realistic Expectations/Scope
• Acknowledge Risk And That It Can Be Managed
• Rollback
• Incompatibility
• Budget Overrun
• Dissatisfied Customers
• Business Interruption
• Missing Deadlines
• Anticipate Questions Be Well Prepared
• Know the Current and Expected Environment
• Close the Deal Secure the Funding

10
PLANNING

• Build the Best Team You Can
• Project Sponsor
• Project Manager
• Development/Testing/QA
• Implementation
• Training
• Support
• Communication
• Specialists

11
PLANNING
Assess Current Environment

• Hardware
• Software
• Network
• Users/Organizational
• Keep It Well Documented
• Keep Gathering Facts/Data

12
ASSESS CURRENT ENVIRONMENT

• Inventory
• How Many
• Where Are They
• Desktops v. Laptops
• Replace/Upgrade
• Standards
• Base Image
• Peripherals

• Leased v. Owned
• Windows XP Compatibility
• winnt32.exe /checkupgradeonly
• www.microsoft.com/hcl
• BIOS Levels
• Minimum Requirements
• Naming Conventions

13
HARDWARE CONSIDERATIONS
Windows XP Requirements
14
ASSESS CURRENT ENVIRONMENT
Software Considerations

• Inventory
• Applications
• Versions
• Upgrades/Licensing
• Standards
• Repackaging
• Base Image
• Vendor Support

• Windows XP Compatibility
• App Compat Toolkit
• Internal Application Owners
• Source Code
• Configuration Doc
• In-House Developed

15
ASSESS CURRENT ENVIRONMENT
Network Considerations

• Architecture
• Design
• Security
• Administration
• Bandwidth
• Traffic
• QoS

• Drive Space
• Rights
• Connectivity
• Protocols
• Mixed NOS
• Services
• Physical Infrastructure

16
ASSESS CURRENT ENVIRONMENT
User/Organizational Considerations

• What Do They Do? When?
• Roaming
• Remote
• Mobile
• When Are They Busiest?
• What Department?
• Applications
• Security Policies
• Accounts/Rights

• Locked v. Unlocked
• Domain/Directory Membership
• Data/Settings
• Backup/Recovery
• User Settings
• Business Processes
• Document

17
PLANNING
Define the Build Requirements

• Standard Desktop and Laptop Configurations
• Define Hardware Standards
• Determine BIOS Revs.
• List Peripheral Support
• List CPU/RAM/Disk Requirements
• Define the REDIdeploy Image Use Layers

18
PLANNING
REDIdeploy Image and Applications
Ad Hoc
Custom
Departmental Apps
Enterprise Apps
Mandatory
Windows XP/SPs/Patches
19
PLANNING
Gather Application Requirements

• Identify Critical Applications
• Consolidate and Standardize on Apps with
  Like-Functionality-Where Possible
• Gather Configuration Information from App Owners
• Work with Departments to Prioritize
• Work Closely with Internal Application Developers
• Document

20
PLANNING
Perform Risk Assessment

• Focus on Mission Critical Applications
• Identify and Analyze Potential Risks
• Quantify Potential Impact of Risk
• Detail Escalation Processes
• Document Risk Assessment

21
PLANNING
Establish Test Lab Environment

• Physical Space/Access/Design Layout
• Power and Network Connectivity
• Acquire Desktops/Laptops
• Acquire OS, Application, and Utility Software
• Acquire Misc. Hardware

22
PLANNING
Define Communication Strategy

• Define Communication Strategy for Each Phase
• Identify Different Audiences
• Define Alternative Delivery Mechanisms
• Email, Vmail, Intranet, Newsletters, Meetings,
  Network Broadcast, Desktoppers
• Establish Communication Timelines
• Document

23
PLANNING
Define Training Strategy

• Define Training Content Strategies
• IT, Admins
• Help Desk
• End Users
• Execs.
• Third-Party Support
• Define Alternative Delivery Mechanisms
• Establish Timelines By Phase
• Document

24
DEVELOPMENT
Create REDIdeploy Image
Windows XP/SPs/Patches

• Logical Build
• Design Per Requirements Gathered
• Physical Build
• Enable Functionality of Windows XP
• Meet Predefined Business Objectives
• Work with Hardware Standards
• Test Build
• Resolve Design and Development Issues
• Various Testing/QA Stages
• Redesign and Re-Engineer
• Solicit Feedback Keep Open Communication
• Redesign, Re-Engineer, and Retest
• Reiterative Process

25
DEVELOPMENT
Create Enterprise Application Layer
Enterprise Apps

• Mandatory
• Office Suite, Email Client, Virus Protection, DB
  Client, Zip Util, Etc.
• Configure Per Requirements Gathered from App
  Owners
• Repackage Applications Enabling Functionality to
  Meet Predefined Business Objectives
• Test Each Application Individually on Std. Image
• Work Out Configuration, Compatibility, and
  Conflict Issues
• Various Testing/QA Stages
• Repackage
• Test All Enterprise Applications Together on Std.
  Image
• Resolve Conflict Issues
• Solicit Feedback from Application Owners to Get
  Sign-Off
• May Need to Redesign, Repackage, and Retest
• Reiterative Process
• Consider Developing a Centralized Packaging Center

26
DEVELOPMENT
Repackage Departmental Layer of Applications
Departmental Apps

• Most Departments Use Similar Apps
• Finance, Acct, HR, Developers
• Configure Per Requirements Gathered from App
  Owners
• Repackage Applications Enabling Functionality to
  Meet Predefined Business Objectives
• Test Each Application on the Std. Image
• Work Out Configuration, Compatibility, and
  Conflict Issues
• Various Testing/QA Stages
• Repackage
• Test All Departmental Applications Together on
  Std. Image and Enterprise App. Layer
• Resolve Conflict Issues
• Solicit Feedback from Application Owners and
• Depts. to Get Sign-Off
• May Need to Redesign, Repackage, and Retest
• Reiterative Process

27
DEVELOPMENT
Repackage Ad Hoc Layer of Applications
Ad Hoc

• Task-Oriented Applications
• Configure Per Requirements Gathered from App
  Owners
• Repackage Applications Enabling Functionality to
  Meet Predefined Business Objectives
• Test Each Application on the Std. Image
• Work Out Configuration, Compatibility, and
  Conflict Issues
• Various Testing/QA Stages
• Repackage
• Test All Individual Applications Together on Std.
  Image, Enterprise App. Layer, and Departmental
  Layer Where Needed
• Resolve Conflict Issues
• Solicit Feedback from Application Owners and
• Depts. to Get Sign-Off
• May Need to Redesign, Repackage, and Retest
• Reiterative Process

28
DEVELOPMENT
A Few Words on Testing

• Testing is only valid if what your testing for is
  in a known state.
• Testing in a controlled lab environment is
  required, but not foolproof.

29
DEVELOPMENT
Installation Process

• Determine the Best Deployment Mechanism for Your
  Environment
• Binary Imaging (ghosting) with Sysprep
• Unattended/Scripted Install
• RIS
• Bootable CD-ROM
• OEM Preinstall
• Develop Solution to Backup/Restore Data and User
  Settings
• Windows XP USMT
• Third-Party
• Custom

30
DEVELOPMENT

• Risk Assessment
• Review Assessment
• Identify Solutions
• Communicate
• Evaluate Day-to-Day
• Communications
• Review Standards
• Develop/Review Materials
• Training/Education
• Review Assessment
• Develop/Acquire Materials
• Review Objectives On Target?

31
PROOF OF CONCEPT
Pre-Pilot

• Perform Dry-Run of All Deployment Steps
• Revise Areas in Need of Improvement
• Perform Pre-Pilot on Friendly Group
• Revise Areas in Need of Improvement

32
PILOT
Planning

• Identify Pilot Users and Groups
• Plan for Time of Least Impact
• Conduct Site Survey
• Procure Additional HW, SW, and Deployment Tools
• Identify and Train Installation Team
• Plan to Utilize All Deployment Methods
• Institute Feedback Mechanism
• Communicate/Prepare Support Groups
• Document Post-Installation Checklist
• Identify Escalation Path
• Develop Contingency Plan

33
PILOT
Deployment

• Communicate with Pilot Users
• Train Users During Deployment
• Deploy the Rollout Process
• Collect Deployer Feedback, Checklists
• Perform Random User Tests
• Connectivity, Functionality
• Data/Settings Restoration
• Document the Entire Process
• Events, Issues, Timing, Workflow Etc.

34
PILOT
Post-Pilot Evaluation

• Have On-Site Support Personnel
• Listen, Obtain End-User Feedback
• Listen, Obtain Support Feedback
• Analyze Data Gathered from Pilot Deployment
• Evaluate Lessons Learned
• Identify Scope Changes
• Review Cost Factors
• Communicate Findings
• Make Necessary Improvements, Refine Plan
• Modify Documentation for Next Steps
• Mgmt Decision Needed to Proceed
• Re-Pilot?

35
DEPLOYMENT
Same Steps As Pilot Planning and Deployment

• Communicate
• Train
• Deploy Incrementally But Swiftly
• Support
• Listen, Collect Feedback
• Document
• Collect Data

36
POST-IMPLEMENTATION

• Monitor Be Proactive
• Executives, Departments, End-Users
• IT, Helpdesk, Third-Tier Support
• Network, Servers, Security
• Remote, Mobile, Branch, Dial-In
• Review Project
• Analyze Data Collected
• Document Lessons Learned
• Prepare for Maintenance

37
MEASURE SUCCESS
Did We Meet Our Goals?

• Business Objectives?
• On Time?
• Within Budget?
• Perception?
• Calculate ROI
• Meet with Mgmt

• Increase Productivity
• More Functionality
• More Competitive
• Internal AppDev
• Faster Rollout/DR
• More Collaboration
• Better Communication

• Reduce IT Costs
• Increase Reliability/Stability
• Increase Supportability
• Standardization
• Predictability
• Consistency
• Manageability
• Compatibility

38
SOURCES OF INFORMATION

• www.microsoft.com/windowsxp/pro/techinfo/deploymen
  t/ default.asp
• www.microsoft.com/business/services/mcsmsf.asp
• www.microsoft.com/windowsxp/officexp/deploy/defaul
  t.asp
• www.microsoft.com/windowsxp/pro/techinfo/productdo
  c/ resourcekit.asp