Windows and Office Upgrade

Vicki Garry
Information Services
11th January 2011
Brief, scope and justification

• Brief - upgrade the current operating system and office
  package

• Scope – upgrade the OS and Office Suite in Units
  where IS supports hardware:
   • RCL, CTU, LHA, NC3Rs
   • c.405 PCs and laptops

• Justification – time consuming and costly project
   • Microsoft support for Windows XP and Office 2003
     ends 2014
   • Data incompatibility
   • New features
   • Other reasons
What to upgrade to

• Windows 7




• Microsoft Office 2010
Advice

• Internal
   • CTU Technical Strategy Group
   • CTU Data Management Systems
   • CTU Training Committee
   • Operational staff from LHA and NC3Rs

• External
   • Other MRC Units who have completed the upgrade
   • JISC
   • Microsoft
   • Our IT partner (Imerja)
   • Head Office’s IT partner (Logica)
   • Suppliers e.g. Dell
Compatibility

• Key stage of the project

• Need to work closely with Data Management Systems

• Identify what will be affected:

    • Known
    • Unknown
    • Externally supported

• For all that will be affected:

    • Create test criteria
    • Test
    • Identify and install fix if required
Implementation planning

• Staging
   • By department/team/functional group?
   • TSG recommendation?
   • Timings
   • Additional resources / overtime

• Technical “how to”
   • Consult with others
   • Put together a test plan
Training

• Required for all users
• CTU Training Committee

• To   be addressed:
   •   Scheduling
   •   Logistics
   •   Training provider
   •   Course content
   •   Presentation/Classroom/e-learning
   •   Handouts/crib sheets
Costs

•   OS and Office licensing
•   OS and Office support
•   Hardware upgrades to make compatible
•   Application and software development to make
    compatible
•   Staff time
•   Systems upgrades
•   Potential consultancy
•   Implementation
•   Training
CTU Technical Strategy Group
• Feedback on initial plans

• Assist with identifying members of a Project Steering
  Group

   • Input into project plans, justification, funding

   • Compatibility - assist with identifying user
     “champions” for each department/functional group
       •   Point of contact
       •   Identify what will be affected by the upgrade
       •   Acceptance criteria
       •   Testing and sign off
CTU Technical Strategy Group

  • Advise on implementation stage

  • Input into planning for training
What IS is doing now

• Current steps are:

   • Consulting partners with previous experience of
     Windows and MS Office migrations

   • Building a software list (programs, databases,
     internal systems (e.g. VPN), external systems) of
     everything that would be affected by an upgrade
Any questions?

Windows and office update jan2012

  • 1.
    Windows and OfficeUpgrade Vicki Garry Information Services 11th January 2011
  • 2.
    Brief, scope andjustification • Brief - upgrade the current operating system and office package • Scope – upgrade the OS and Office Suite in Units where IS supports hardware: • RCL, CTU, LHA, NC3Rs • c.405 PCs and laptops • Justification – time consuming and costly project • Microsoft support for Windows XP and Office 2003 ends 2014 • Data incompatibility • New features • Other reasons
  • 3.
    What to upgradeto • Windows 7 • Microsoft Office 2010
  • 4.
    Advice • Internal • CTU Technical Strategy Group • CTU Data Management Systems • CTU Training Committee • Operational staff from LHA and NC3Rs • External • Other MRC Units who have completed the upgrade • JISC • Microsoft • Our IT partner (Imerja) • Head Office’s IT partner (Logica) • Suppliers e.g. Dell
  • 5.
    Compatibility • Key stageof the project • Need to work closely with Data Management Systems • Identify what will be affected: • Known • Unknown • Externally supported • For all that will be affected: • Create test criteria • Test • Identify and install fix if required
  • 6.
    Implementation planning • Staging • By department/team/functional group? • TSG recommendation? • Timings • Additional resources / overtime • Technical “how to” • Consult with others • Put together a test plan
  • 7.
    Training • Required forall users • CTU Training Committee • To be addressed: • Scheduling • Logistics • Training provider • Course content • Presentation/Classroom/e-learning • Handouts/crib sheets
  • 8.
    Costs • OS and Office licensing • OS and Office support • Hardware upgrades to make compatible • Application and software development to make compatible • Staff time • Systems upgrades • Potential consultancy • Implementation • Training
  • 9.
    CTU Technical StrategyGroup • Feedback on initial plans • Assist with identifying members of a Project Steering Group • Input into project plans, justification, funding • Compatibility - assist with identifying user “champions” for each department/functional group • Point of contact • Identify what will be affected by the upgrade • Acceptance criteria • Testing and sign off
  • 10.
    CTU Technical StrategyGroup • Advise on implementation stage • Input into planning for training
  • 11.
    What IS isdoing now • Current steps are: • Consulting partners with previous experience of Windows and MS Office migrations • Building a software list (programs, databases, internal systems (e.g. VPN), external systems) of everything that would be affected by an upgrade
  • 12.