microsoft deployment using mdt and sccm n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Microsoft Deployment Using MDT and SCCM PowerPoint Presentation
Download Presentation
Microsoft Deployment Using MDT and SCCM

play fullscreen
1 / 52

Microsoft Deployment Using MDT and SCCM

364 Views Download Presentation
Download Presentation

Microsoft Deployment Using MDT and SCCM

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Microsoft Deployment Using MDT and SCCM Chad DeGuira Oak Ridge National Laboratory Information Technology Services Division Systems Management

  2. Microsoft Deployment Using MDT and SCCM Introduction • Presentation Focus • Something for everyone • Extension from last years presentation on MDT • Deployment Benefits • ORNL History and Environment • ORNL Deployment Philosophies • Microsoft Desktop Deployment (MDT) and System Center Configuration Manager (SCCM) at ORNL

  3. Microsoft Deployment Using MDT and SCCM Deployment Benefits

  4. Microsoft Deployment Using MDT and SCCM Why is imaging and deployment so important? • How long does it take to deploy a computer manually? • 1 hour: Backup computer • 1 hour: Find and save User Data to backup location • ½ hour: Find, save, and document User Settings • 1 hour: Load operating system • 1 hour: Download and install latest drivers • ½ hour: Load operating system patches (Windows Updates) • ½ hour: Load all required applications • ½ hour: Load optional applications • 1 hour: Restore user data and settings TOTAL = 7 hours

  5. Microsoft Deployment Using MDT and SCCM Why is imaging and deployment so important? (Continued) Questions to ask yourself: • How much manual intervention does your process take at each step? • What does technical knowledge cost? • What is the cost of training when things change? • Every time a new application, application version, OS, computer model, driver, security mechanism, etc….how do we get anything done? • How often do you deploy?

  6. Microsoft Deployment Using MDT and SCCM Why do we image and deploy? • New machines • Replacing existing machines • Replacement and “push downs” (1 new machine can mean many deployments) • Decommissioning • Reloading machines as a function of purpose • Conference rooms, training rooms, interns, etc. • Testing Environments • A clean environment to test in • Migration to new operating systems • Support tool • Fixing that “needle in a haystack” • Refreshing • Application deployment • Task Sequences • I need to perform 15 processes on 3000 computers….

  7. Microsoft Deployment Using MDT and SCCM More benefits? Think of the possibilities…. • Capture the knowledge in one place • Training requirements are simplified • User Support Personnel can focus on real problems • Faster migrations • Disaster Recovery • Improved Security due to reloading versus re-using • Productivity gains using User State Migration • Computer support simplification fixing “needle in the haystack” problems • Standardization • And many, many more…

  8. Microsoft Deployment Using MDT and SCCM The ORNL History and Environment

  9. Microsoft Deployment Using MDT and SCCM ORNL Computing Environment • Approximately 10,000 machines • Approximately 8,000 are Windows desktop machines • All current Windows Operating Systems are supported • 2500 Vista operating systems running today • Managed Hardware Program • ORNL loads approximately 140 machines per week using Operating System Deployment tools

  10. Microsoft Deployment Using MDT and SCCM Complex Deployment Environment

  11. Microsoft Deployment Using MDT and SCCM Complex Deployment Environment

  12. Microsoft Deployment Using MDT and SCCM Complex Deployment Environment

  13. Microsoft Deployment Using MDT and SCCM Complex Deployment Environment

  14. Microsoft Deployment Using MDT and SCCM Complex Deployment Environment

  15. Microsoft Deployment Using MDT and SCCM Complex Deployment Environment

  16. Microsoft Deployment Using MDT and SCCM Complex Deployment Environment

  17. Microsoft Deployment Using MDT and SCCM Complex Deployment Environment

  18. Microsoft Deployment Using MDT and SCCM ORNL’s History of Imaging and Deployment

  19. Microsoft Deployment Using MDT and SCCM Example of ORNL’s (CLEAN) Deployment Wizard

  20. Microsoft Deployment Using MDT and SCCM Example of ORNL’s (CLEAN) Deployment Wizard

  21. Microsoft Deployment Using MDT and SCCM Example of ORNL’s (CLEAN) Deployment Wizard

  22. Microsoft Deployment Using MDT and SCCM Example of ORNL’s (CLEAN) Deployment Wizard

  23. Microsoft Deployment Using MDT and SCCM Example of ORNL’s (CLEAN) Deployment Wizard

  24. Microsoft Deployment Using MDT and SCCM Example of ORNL’s (CLEAN) Deployment Wizard

  25. Microsoft Deployment Using MDT and SCCM Example of ORNL’s (CLEAN) Deployment Wizard

  26. Microsoft Deployment Using MDT and SCCM Example of ORNL’s (CLEAN) Deployment Wizard

  27. Microsoft Deployment Using MDT and SCCM Example of ORNL’s (CLEAN) Deployment Wizard

  28. Microsoft Deployment Using MDT and SCCM The ORNL Philosophy

  29. Microsoft Deployment Using MDT and SCCM The ORNL Philosophy: NO Upgrades • We never perform upgrades on computers at ORNL • Increases overall support costs rather than reducing migration costs • Adequate backups, User State Migration and effective application deployment compensate for not using upgrading mechanisms

  30. Microsoft Deployment Using MDT and SCCM • The ORNL Philosophy: NO Operating System Tweaks • Leave it natural • Perception that the image is “hacked” when visibly modified • Don’t customize look and feel items • Everybody can NEVER be satisfied • Standardize on the only “basis” point…NOTHING • Simplify or prevent OOBE window popups • Group Policy preferred method for modification • Per user, group, machine… • Only exceptions are security modifications, customizations or requirements • Enhancements before domain policy is applied

  31. Microsoft Deployment Using MDT and SCCM The ORNL Philosophy: So easy the end user can do it! • For standard users • Choices are bad • For technicians • Choices are good • Find a compromise… • If I can answer all the IFs, ANDs, and BUTs…. • If I can “re-word” the technical questions THEN • ANYONE can do it…

  32. Microsoft Deployment Using MDT and SCCM The ORNL Philosophy: Image Creation Automation • How do you reduce management of image creation process? • How do you improve security of images being deployed? • Always have the latest Windows and application updates applied • Always have the latest Virus Definitions applied Create your image daily through automation!

  33. Microsoft Deployment Using MDT and SCCM • The ORNL Philosophy: Manufacturer Drivers and Applications • Only install drivers provided by the COMPUTER manufacturer except in severe cases • Proper support from the COMPUTER manufacturer requires this • Drivers are often tweaked by a COMPUTER manufacturer for their computers (although P&P IDs may be the same) • SMALL Driver Pools • Many SMALL pools rather than one LARGE pool • MODEL then OPERATING SYSTEM then BIT (Mixing OS or BIT doesn’t work) • Unknown or “OTHER” models should not fish from the large pool either. They should get nothing • Exception…Hard disk controller and network drivers • OEM Applications But NO “Bell and Whistle” Software • May provide advanced functionality for devices but typically not used by end users (Video Control Panels) • Training and support (i.e. Wireless Managers) • Consumes resources • Can conflict with productivity applications • Can cause migration issues (such as a move to Vista) • Can introduce exploits

  34. Microsoft Deployment Using MDT and SCCM Microsoft OS Deployment Tools: Microsoft Deployment Toolkit and SCCM Operating System Deployment

  35. Microsoft Deployment Using MDT and SCCM • Zero Touch versus Lite Touch • Lite Touch Deployment • Human intervention will be required at the computer • Associated with Microsoft Deployment Toolkit (MDT) • Zero Touch Deployment • The process does not require human touch at the computer • Associated with SCCM Operating System Deployment • These definitions fail to adequately or correctly define either deployment tool

  36. Microsoft Deployment Using MDT and SCCM • MDT versus SCCM • Microsoft Deployment Toolkit (MDT) • Excellent GUI interface to ask questions (variables) prior to deployment • Alternatively, can be fully automated during deployment if variables predefined • No built in mechanism to schedule and initiate itself for deployment • System Center Configuration Manager (SCCM) Operating System Deployment (OSD) • Non-existent GUI interface • All variables configured on SCCM prior to deployment • Excellent built in scheduling and initiating of deployments

  37. Microsoft Deployment Using MDT and SCCM • Deployment Tool Usage • Microsoft Deployment Toolkit (MDT) • Great for GUI driven installations • Out-of-Box • Technician installations requiring choices • SCCM Operating System Deployment • Great for scheduling and initiation • Conference Rooms • Training Room • Large Migrations

  38. Microsoft Deployment Using MDT and SCCM • SCCM Operating System Deployment at ORNL • Migration of daily image creation responsibilities to SCCM • More secure • Integrated with current patching infrastructure • Better integrated with current package infrastructure • Looking at ways to create GUI for SCCM for our environment • Desire to simplify to one deployment tool • GUI front end is the easy part, Collection manipulation more difficult • Replacing the MDT “Refresh” scenario with SCCM OSD Advertisements

  39. Microsoft Deployment Using MDT and SCCM • SCCM Operating System Deployment at ORNL • Distribution Points for MDT for improved redundancy • Task Sequences • Great for complex system management • To be effective, needs scheduling and initiating piece SCCM provides • Reduces scripting effort • Offsite computer OSD installations

  40. Microsoft Deployment Using MDT and SCCM • Scripting

  41. Microsoft Deployment Using MDT and SCCM • Task Sequences

  42. Microsoft Deployment Using MDT and SCCM • Task Sequences

  43. Microsoft Deployment Using MDT and SCCM • Working With MDT and SCCM Simultaneously • Although MDT integrates into SCCM, it is not a migration, just an extension • MDT can be modified to pull same SCCM packages • Can be redundant as described previously • ORNL’s methods for driver support has been simplified to support both systems • ORNL has radically modified the approach to drivers

  44. Microsoft Deployment Using MDT and SCCM • SCCM Gripes… • You will find bugs requiring fixes or workarounds • Pre-execution hook versus R2 Unknown Computer Support • SCCM typically requires the computer be known before security will allow OSD • Task Sequences are not “migratable” • Incredibly complex because incredibly powerful

  45. Microsoft Deployment Using MDT and SCCM • Where are we going now? • Windows 7 • Dell Deployment Pack for Configuration Manager • SCCM OSD GUI • Microsoft Deployment 2010 Beta 2 • Windows 7 RC • USMT 4 • SCCM Service Pack 2

  46. Microsoft Deployment Using MDT and SCCM Closing • Each Deployment Scenario is Unique • Two main goals to balance • Keep management simple • Keep usability simple • Deployment is a Collaborative Effort • Open Forum Discussion • Blogs • Forums • Colleagues • Contact Info • DeGuiraCA@ornl.gov • Thank You!

  47. Questions or Discussion

  48. Microsoft Deployment Using MDT and SCCM SCCM – Distribution Points Improve Redundancy

  49. Microsoft Deployment Using MDT and SCCM MDT is not designed to handle redundancy

  50. Microsoft Deployment Using MDT and SCCM SCCM – Distribution Points Improve MDT Redundancy