1 / 42

Canberra Windows User Group “InTACT - SOEXP” Welcome

Canberra Windows User Group “InTACT - SOEXP” Welcome Michael Vanderheide (InTACT – General Manager) Introduction John Scott (Microsoft – Technical Account Manager) Initiate Zero Touch demonstration Naran McClung (InTACT – SOEXP Technical Lead) The Project Management Perspective

wilda
Download Presentation

Canberra Windows User Group “InTACT - SOEXP” Welcome

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. Canberra Windows User Group “InTACT - SOEXP” • Welcome • Michael Vanderheide (InTACT – General Manager) • Introduction • John Scott (Microsoft – Technical Account Manager) • Initiate Zero Touch demonstration • Naran McClung (InTACT – SOEXP Technical Lead) • The Project Management Perspective • Craig Brown (InTACT – SOEXP Project Manager) • The Vendors Perspective • Nick Beaugeard (Dimension Data) • The Technical Perspective • Naran McClung • Review Zero Touch demonstration • Discussion / Questions

  2. InTACT - SOEXP The Project Management Perspective Craig Brown (SOE XP Project Manager)

  3. Work completed to date Phase 1 • Project Proposal & SOE Design  • Initial Reference Build (BDD) • Implementation of BDD reference build and OSD in ‘TEST’ environment • Fully functional XP based SOE build in 'Production' environment • Stakeholder Consultation & Application identification • Executive Endorsement

  4. Work currently underway Phase 2 • Phase 2.1 - Baselining of  SOEXP Design (Vanilla Trial & Initial Pilot) • Phase 2.2 - Project Plan

  5. Work proposed for 2006 Phase 3 • User Acceptance Testing (Environment, Single Instance & Sociability) • Agency Deployments • Application Consolidation and 'clean-up'

  6. General Lessons Learnt • That the goals (scope) of the project and a budget be defined is defined early • That key project staff are dedicated to the project (PM & Tech Lead) • That the Project works with (not against) the operational area’s responsible for the desktop environment • That the complexity and time required to complete the project is not underestimated • That communications with all stakeholders is commenced early in the project • That all stakeholders make a commitment to being part of the larger project team • That stakeholders are provided with enough time to budget for changes to their applications life-cycle

  7. InTACT - SOEXP The Vendor Perspective Nick Beaugeard Managing Director – Dimension Data

  8. InTACT - SOEXP The Technical Perspective Naran McClung (SOEXP Technical Team Lead)

  9. SOEXP – The new A.C.T. Government Desktop Architecture What will be covered: • COE2000 – Where we’re coming from… • Fundamental design considerations • The Business Desktop Deployment (BDD) Solution Accelerator • The Operating System Deployment Feature Pack (OSD) • Bare Metal Build Integration • The User State Migration Tool (USMT) • Zero Touch Installation

  10. SOEXP – The new A.C.T. Government Desktop Architecture What will be covered: • Dynamic Driver Integration • Dynamic ‘Tablet PC’ Integration • Integration – Java Runtime Environment • Integration - Roaming Profiles • Application Testing - Vmware & The Remote Desktop Protocol • The Windows Firewall • The finished product…

  11. COE2000 – Where we’re coming from… 1. CD-ROM initiated (By technical personnel) 2. Windows 2000 Professional ‘Unattended’ Installation 3. Scripted Installation of ‘Tier 1’ Apps 4. SMS Managed Applications (Tier 2 Apps)

  12. COE2000 – Where we’re coming from… • One-size-fits-all COE • Supporting separate ‘Application’ infrastructure • Erroneous Computer Accounts (Domain Rejoin) • Timely process • SMS 2003 manages ‘Tier 2’ applications • Onsite visit required for rebuild

  13. Fundamental design considerations: • Fast & efficient delivery (No erroneous Accounts) • Ease of administration • Reduced downtime for the end-user • COE2000 -> SOEXP: Low impact upgrade • Holy Grail #1 - Leverage existing infrastructure • Holy Grail #2 - Modular SOE construction • Holy Grail #3 - Remote Deployment

  14. Business Desktop Deployment (BDD): - Technical guides, plus a bunch of scripts & tools…

  15. Business Desktop Deployment (BDD): • The Operating System Deployment Feature Pack (OSD) - • Create, Manage & Deploy Operating Environments • OSD extends SMS 2003 • Holy Grail #1 - Leverage existing infrastructure • OSD: Zero Touch Installation (ZTI) • Holy Grail #3 – Remote Deployment • OSD works with WIM images

  16. WIM image? Windows Vista? • Windows Vista will ship exclusively in the WIM image format • Ximage command line utility • Strategic positioning – SMS 2003 & OSD • … • With Windows XP SP2, we need to create our own WIM image...

  17. Business Desktop Deployment (BDD): Computing Imaging System Feature Team Guide – Reference Build infrastructure (customised)

  18. Business Desktop Deployment (BDD): Computing Imaging System Feature Team Guide Reference Build infrastructure (customised) • Base Operating System (OS) • Current OS Service Pack • Base OS updates • Microsoft Windows Media Player 10 • Microsoft Windows Installer 3.1 • Microsoft .Net Framework 1.1 SP1 • SMS 2003 Advanced Client • Sysprep Core files • No answer file • Machine in Workgroup • Ready for WIM image capture…

  19. Microsoft Windows Imaging Format (WIM): • File-based Imaging format • Hardware-agnostic • One image - Many different hardware configurations • Installs on varying hard-disk or partition sizes • Non-destructive • Supporting USMT • Hardware Abstraction Layer (HAL) sensitive

  20. Microsoft Windows Imaging Format (WIM): Hardware Abstraction Layer (HAL) sensitive Three HAL types within the ACT Government: • ACPI_PC_HAL • i.e. IBM R50 Notebook • ACPI_UNI_PC_HAL • i.e. HP D530 Desktop • ACPI_MULTI_PC_HAL • i.e. HP DC7100 Desktop • Initiate one Reference Build per HAL type • Capture a ‘HAL specific’ WIM image (WIM images integrate as OSD Image Packages)

  21. Operating System Deployment Feature Pack (OSD): 1. Initiate a Reference Build (HAL specific) 2. Capture a Microsoft Windows Image (WIM) 3.Integrate WIM image into SMS 2003 • Create an ‘Image Package’ • Link Default Application Set (Tier 1) • Link ‘Tested’ Security Hotfixes • Link Configuration Packages • Link Driver Package • Link State Capture Processes

  22. Operating System Image Capture • Image Package creation • Image Package Program Properties • XML build file & OS Deployment Agent demonstration

  23. Holy Grail #2 - Modular SOE construction

  24. Bare Metal Build Integration: • No SMS client! • No automatedValidation & State Capture phases • Note: Refresh PC USMT scenario • RIS (Windows Server 2003) to leverage OSD: • Automate RIS options to your heart’s content • Pre-staged Computer Accounts • Padded MAC address (Vendor should provide) • AD Application Group memberships (Tier 2 apps)

  25. Bare Metal Build Integration: • Create a standard Windows XP SP2 OS image • Ensure all required RIS NIC drivers are in place • Create an Operating System Image Installation CD • Overlay CD over the top of the OS image • Creating an OSD specific ‘Windows PE’ RIS image • Modify ristndrd.sif to include the /minint switch and DriverSigningPolicy = Ignore • Under the [WinPE] section, modify WINBOM.ini to include Quiet=Yes • Avoiding the ‘Shut Down Windows PE’ dialog

  26. Creation of Operating System Image Installation CD • TAP_Output.txt • OSD_Setup.vbs • Initiate Bare Metal Build demonstration

  27. The User State Migration Tool (USMT): • Capture and Restore User State: Win2k > WinXP • Outlook settings (Including PST files within view) • Printers • Internet Explorer Favourites • Locally stored files (Including static PST files) • Various Application settings (i.e. Custom Dictionary) • Environmental settings (i.e. Mouse/Keyboard options) • For all Profiles (accessed < 35 days)

  28. The User State Migration Tool (USMT): • Custom action calling scanstate.vbs (State Capture phase) Migsys.inf • Display Properties, Fonts, Internet Settings, Mouse and Keyboard, ODBC Data Source Names Miguser.inf • Internet Explorer Favourites, Printers Migapp.inf • Various Application settings (Office 2000), Outlook Sysfiles.inf • Files that USMT will not migrate (Left as is) ArchiveApp.inf • Migrate legacy applications (Not used) • Stability & ScanState.exe – USMT Bodyguard.vbs • Manage running Process • Manage running Services (thanks Bellerephon / Dimension Data)

  29. User State Migration: • The PC Refresh Scenario: • Capture USMT data the night before deployment • Stored on network resource • A relationship is established • Old PC -> New PC • Referencing central configuration file • USMT data restored as new PC hits the desk

  30. User State Migration: • The Zero Touch Installation (ZTI) Scenario: • Automated OSD process • User State data stored locally (thanks to WIM) • Hard disk requirements determined • USMT estimate: Before deployment • Warning issued during deployment (2GB+) • User State seamlessly restored • Loadstate: Custom action calling loadstate.vbs

  31. Zero Touch Installation (ZTI):

  32. Zero Touch Installation (ZTI): • Modify MOF to include HAL information • Query existing collection

  33. Dynamic Driver Integration: • Drivers divorced of WIM image • Driver package: Majority of Drivers for all Systems • Drivers dynamically integrated during ‘Post Install’ phase • Sysprep.inf: Update OemPnPDriversPath Path • Registry: Update DevicePath • Adding support for new hardware • No requirement to update base images!

  34. Dynamic ‘Tablet PC’ Integration: • During ‘Post Install’ phase: • Utilising TAP.exe: Look for Tablet PC specific device • Dynamically modify sysprep.inf • ProductKey = Windows XP Tablet PC Edition 2005 Key • Comment out ProductID • Copy Tablet PC specific files to ‘C:\Sysprep\’ • Copy Tablet PC specific files to ‘C:\Sysprep\i386’ • SOEXP sell point – New hardware now an option…

  35. Integration – Java Runtime Environment: • JRE: Locked-down, Centrally managed & Supported • Set our managed version of JRE as IE default • Disable Automatic Updating • Set cache size / location • Hide the Java console • Disable JNLP shortcut creation • Disable System Tray icon(s) • Etc… • Engagement with Sun Microsystems • Local file: • WINNT\Sun\Java\Deployment\deployment.config • DFS central configuration file: • deployment.system.config=file://///act.gov.au/software/SOEXP/JRE5/jre.properties

  36. Integration - Roaming Profiles: • Roaming Profiles are here to stay… • Supporting a mixed Desktop Environment • Avoid the use of a common Roaming Profile • Clean slate: NT4 > Win2k > WinXP • Separate Roaming Profile per SOE type • The SOEType System Environment Variable • A change to the AD User Account Profile path • UPHClean Service for good measure!

  37. Using: %SOEType% The SOEType System Environment Variable:

  38. Application Testing - Vmware & RDP • Three major testing phases: • Environmental Testing • Single Instance Application Testing • Application Sociability Testing • Utilising Vmware images & Vmware Player (free): • Centrally managed Vmware images (on SAN volumes) • In-Place testing (No labs or alternate workstations) • Revert to Snapshot • Performance…? • The Remote Desktop Protocol (RDP) • Dedicated testing asset(s)

  39. The Windows Firewall: Within Domain = Firewall Off Away from Domain = Firewall ON (No Exceptions) Due to: • Potential risk to Application Testing timeline (500+ apps) • Ongoing operational cost (GPOs vs. INFs) • A more granular OU structure is coming… SOEXP Phase 2… 

  40. Review completed SOEXP build log • Log on using production User Account (non-Admin) • Review User State Migration demonstration

  41. Questions

More Related