1 / 44

Technology Refresh Programme Overview - Windows 7 and Office 2010 Upgrade

This comprehensive programme encompasses the deployment of Windows 7, support for mobile devices, Exchange and Office upgrades, along with server enhancements and compatibility assessments. It outlines steps for new operating systems, architecture considerations, replacement budget guidelines, user profile migration procedures, security measures, and deployment scenarios. The project emphasizes compatibility testing, application packaging, secure build configurations, encryption protocols, authorized applications, and deployment methods for various scenarios.

kdumas
Download Presentation

Technology Refresh Programme Overview - Windows 7 and Office 2010 Upgrade

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. Technology Refresh Programme Project Overview4TH December 2012 Derek Askew www.britishcouncil.org

  2. Agenda • Tech Refresh Project Overview • Windows 7 Build Overview • Applications • Deployment Scenarios • USMT & State Migration • SCCM Site Preparation • AD Site Preparation • Other Preparation Tasks • Migration Portal • Questions www.britishcouncil.org

  3. Tech Refresh Overview

  4. Scope • Windows 7 Deployment • Support from Smartphones and Tablets • Exchange 2010 Upgrade • Office 2010 Upgrade • AD Upgrade – Server 2008 • SharePoint 2014 Upgrade – Evaluation of Office 365

  5. Incompatibility and Standardisation Costs • Moving to a new Operating System and Architecture will inevitably mean some incompatible hardware and software. • Where computers are incompatible Technology Refresh will provide budget for replacements • Where software is incompatible the business will need to provide budget for replacements • Where peripherals (printers, scanners etc.) are incompatible the business will need to provide budget for replacements www.britishcouncil.org

  6. Windows 7 Build Overview

  7. Core Build • Windows 7 Enterprise SP1 64bit • Office 2010 SP1 32bit • Windows and Office Language Packs as required • Other “Core” applications are delivered in SCCM Task Sequence • License management of MS products via KMS • “Non-Core” applications should go through compatibility testing and packaging • Supported Computer Models www.britishcouncil.org

  8. Core Applications List www.britishcouncil.org

  9. Supported Models www.britishcouncil.org

  10. Profiles and Folder Redirection • Windows XP profiles are incompatible with Windows 7 • Created in the same share as XP profile • New profile created with a .V2 suffix • As with XP most “Special Folders” will be redirected to the users Home Drive • No other profile migration process will be conducted • Any settings in the NTUser.dat will not be migrated • Favourites, My Documents etc. will be available due to Redirection www.britishcouncil.org

  11. Security • Laptop HDD will be encrypted using BitLocker • Backup to AD • Transparent Operation Mode – TPM • 256 Bit – Build 3.5, Prior to that 128 Bit with DiffUser • Requirements for China and Russia TBD • Full suite of McAfee applications will be in installed (except Endpoint Encryption) • USB access will be controlled by McAfee DLP • As with XP; Windows Updates will be managed via SCCM www.britishcouncil.org

  12. Applications www.britishcouncil.org

  13. Overview

  14. Application Packaging Team

  15. Office Files & IE9 www.britishcouncil.org

  16. Deployment Scenarios

  17. Deployment Scenarios – Refresh (Same HW) www.britishcouncil.org

  18. Deployment Scenarios – Replace (New HW) www.britishcouncil.org

  19. Deployment Scenarios – Standalone (No USMT) www.britishcouncil.org

  20. USB On-Network Build Media • Source • SCCM Console • ISO in MiManager • An offline copy of the SCCM Task Sequence • Requires network access during build process • Includes all “Core Build” software • Does not include security updates • Manual USMT process required

  21. USB Off-Network Build Media • Enables building machines with VPN only access • Uses a local account to initially join the domain and RunAs to cache the users credentials • Has limitations • VPN Client does not support connection without interactive logon. • VPN Client does not support “Switch User” • Computer GPOs run at start-up when the machine is not connected therefore are not applied • User GPPs run at login when the machine is not connected therefore are not applied (manual drive mappings required)

  22. SCCM Deployment Overview SCCM Router MDT PXE SCCM 4 2 1 3 • F12 PXE Boot • Download PXE Boot Image • Run SCCM Task Sequence • MDT Provides Settings

  23. Microsoft User State Migration Tool www.britishcouncil.org

  24. USMT components • Tool Version 4.0 • Conceptual Design • Collect the user state • Save the user state to Migration Store • Restore the user state to the Target computer • Scanstate • Scans the machine, collects the data (files and settings) and creates the store in the .mig format- encrypted • Loadstate • Restores the data from the store to the machine • Migration Store • State Migration Point • Data Retention Period • Migration Rules • MigUser.XML ( rules specific to collect data) www.britishcouncil.org

  25. State Migration Solution Overview www.britishcouncil.org

  26. State Migration Solution Overview • Why USMT? • USMT 4.0 seamlessly integrates with SCCM and MDT 2010 • No Licensing cost involved • Design Principles and Assumptions • Enough Space on the server/ NAS • Migration process to only include the user data • Data will be stored to and restored from a network share (State migration point) • Solution allows the site to customize the XML file per the site requirements • Local Users and Admin accounts (_ accounts) excluded from scanning • Solution caters to migrate known file types only. www.britishcouncil.org

  27. State Migration Solution Overview • Scenarios Covered • Refresh (Source and Destination Machines are the same) • Replace (Source Machine different from the destination machine) • Data Retention Period • File Types *.123,*.accdb,*.ch3,*.csv,*.dif,*.doc*,*.dot*,*.dqy,*.fp,*.fpt,*.gmb,*.iml,*.iqy,*.jsd,*.jsd,*.mcw,*.mda,*.mdb*,*.mde,*.mpp,*.msg,*.one,*.one*,*.oqy,*.or6,*.pdf,*.pot*,*.ppa,*.ppam,*.pps*,*.ppt*,*.pre,*.pst,*.pub,*.qdf,*.qel,*.qph,*.qsd,*.rep,*.rqy,*.rtf,*.scd,*.sh3,*.slk,*.txt,*.vl*,*.vsc,*.vsd,*.vss,*.vst,*.vsw,*.wbk,*.wdb,*.wk*,*.wpd,*.wps*,*.wq1,*.wri,*.xl*,*.xla,*.xlb,*.xls*,*.xsn www.britishcouncil.org

  28. SCCM Site Preparation www.britishcouncil.org

  29. SCCM Site Preparation – Pre-requisites • IDU document 000757 available in MiManager • Disk Space • Build and Core applications need ~14GB • Repackaged applications will need approximately the same again as the XP applications • If site currently has 200GB of apps distributed it will need at least a further 200GB of free space • Free space must be on one of the SCCM DP shares although sufficient cache must be available on C Drive • More is obviously better to allow for growth • Need to start planning for upgrades now • Shuchi Chopra’s team are end to end service owners www.britishcouncil.org

  30. Operating System Deployment (OSD) • Some locations have already installed OSD for XP • Where OSD for XP HASNOT been installed • Stop Ghost service • Install Windows Deployment Service (WDS) • Install PXE Boot Point • Distribute Boot Image to SCCM server • Configure and Initialise WDS • Configure Microsoft Deployment Toolkit 2010 (MDT) XP • Distribute XP and reference applications • Where OSD for XP HAS or HAS NOT been installed • Enable iSCSI Initiator (required for NAS drive) • Install State Migration Point (SMP) • Configure Microsoft Deployment Toolkit 2010 (MDT) W7 • Distribute Windows 7, Core applications and required Non-Core applications www.britishcouncil.org

  31. AD Site Preparation www.britishcouncil.org

  32. AD Work • Who is does this? • Currently Ops Bridge Team – Shuchi Chopra • Stephen Addy recruited by the project reports to Shuchi • All Site Ous and Empty Shell GPOs have been created • Change Request • Parent-Child CR process created • HUB PM responsible for collecting data (drive mappings, proxy settings etc.) www.britishcouncil.org

  33. Active Directory Tasks – Create OUs • IDU document 000773 available in MiManager www.britishcouncil.org

  34. Other Site Preparation Tasks www.britishcouncil.org

  35. Printers • Identify unsupported printers • Check vendor for Windows 7 64bit drivers • Update portal • Install 64bit drivers • Must have same model name as 32bit driver • Must be done from a 64bit device • Configure location tracking • Allows users to easily find printers in their site • Function enabled by GPO • By default when searching for a printer first 20 in the local site are displayed • Country/Site/Specific – UK/LON9/FirstFloor • Need all regions to supply list of Printers www.britishcouncil.org

  36. Peripherals • Identify other peripheral types and models • Identify unsupported models • Check vendor for Windows 7 64bit drivers • Update portal www.britishcouncil.org

  37. During Site Migration • During Migration Process • Move user account to new OU as machine is deployed • Clear the login script attribute in AD • Add Lead Management Services • Skype • On Delete Computer accounts from SCCM – Tool provided • Clean up the Lead Management Services • McAfee • Skype www.britishcouncil.org

  38. Post Migration • Format NAS Drive – Important, don’t leave site with any data. • Move All Groups to new • Completion of Each Migration • Delete XP profile once user has confirmed migration successful • Move Computers to “Global -> Stale Records” OU www.britishcouncil.org

  39. Migration Portal www.britishcouncil.org

  40. Why do we need a Portal • Central point of deployment data • Live view of progress • Reporting • Asset Information for Logica is mandatory for handover • KPI progress reports • Reduce dependency on spread sheets • Corruption • Versioning • Concurrency • Control data quality using business logic • Maintain overall picture of readiness and progress • Accountability • All actions are audited in the portal www.britishcouncil.org

  41. Technology Overview • Data • SQL Azure – hosted in Western Europe • Web Server • Windows Azure Web Role – hosted in Western Europe • All web service traffic is secured via SSL • User Interface • Silverlight Windows Azure SQL Azure Web Services HTTPS Western Europe www.britishcouncil.org

  42. Document List www.britishcouncil.org

  43. Documents • 000755 Windows 7 Solution Overview • 000775 State Migration Solution Overview • 000767 Windows 7 Administration Guide • 000757 Configuring a site for Windows 7 Deployment • 000774 Migrating from Windows XP to Windows 7 • 000773 Window XP to Windows 7 Migration – Site Preparation • 000932 Installing a Windows XP using Configuration Manager • 000938 Installing a Windows 7 using Configuration Manager • 000973 Configuring QNAP NAS TS-259 Pro + for Windows 7 USMT Migration • 000939 Manual USMT Process • 000953, 000954, 000963 USB On-Network Build Prep and Process • Always get the latest version from MiManager www.britishcouncil.org

  44. Questions www.britishcouncil.org

More Related