70-643: Windows Server 2008 Applications Infrastructure. Course 01 - Deploying Windows in the Enterprise

Transcription

1 70-643: Windows Server 2008 Applications Infrastructure Course 01 - Deploying Windows in the Enterprise

2 Slide 1 Deploying Windows in the Enterprise How to deploy Windows in the 2008 Server Environment Working with WDS Virtual Machine Deployment Putting in an Activation Infrastructure

3 Slide 2 Topic A: How to Deploy Windows in the 2008 Server Environment Basics of Windows Deployment How Windows can be deployed

4 Slide 3 Basics of Windows Deployment Definition of Deployment Installation of the Windows Operating system to one or more destinations Migrating platforms to newer versions of Windows Levels of Deployment Automation The Planning Phase The Building Phase The Deployment Phase

5 Slide 4 Tools of the Planning Phase Microsoft Assessment and Planning Toolkit (MAP) 4.0 Microsoft Application Compatibility Toolkit (ACT) 5.5 Enterprise Learning Framework Microsoft Deployment Toolkit (MDT) 4.2 Microsoft Desktop Optimization Pack (MDOP) for asset inventory Planning 1.0 System Center Configuration Manager 2007

6 Slide 5 Tools of the Building Phase MDT Deployment Workbench 4.2 Windows Automated Installation Kit (WAIK) 1.0 User State Migration Tool (USMT) 4.0

7 Slide 6 Tools of the Deployment Phase MDT Deployment Workbench Windows Deployment Services (WDS) System Center Configuration Manager 2007 User State Migration Tool

8 Slide 7 Basics of Windows Deployment Common components with a Microsoft Deployment Solution: Windows Automated Installation Kit Tools: Windows PE Image X Windows System Image Manager (SIM) Sysprep

9 Slide 8 Windows PE Bootable version of Windows Does not need to be installed on the hard drive Can use DVD, CD, USB, or network location to boot from Creates a RAM Drive for the operating system Once booted up to Windows PE, you can then add or take an image of the attached hard drive

10 Slide 9 Image X This is a part of the WAIK It s a command line tool used to capture, modify, or apply WIM images This can also be used with Windows PE Boot up to Windows PE and then run Image X

11 Slide 10 Windows SIM Windows SIM: Used to create the unintended Windows setup answer files Originally these were simple text files Now based in XML With Windows SIM, you will have a GUI that can read the image, and help create a custom answer file for that image

12 Slide 11 Sysprep Designed for deploying Windows images Issues with an image, is that it s a copy of an existing Windows installation Deploying the image, would leave you with several servers or workstations that have the same account name and Security Identifiers Sysprep removes all identifying features

13 Slide 12 WIM: A Closer Look WIM: Windows Imaging Format File-Based, not sector based images WIM files can be updated before, during, and after use WIM files are supported by ACLs

14 Slide 13 WIM: A Closer Look Not dependant upon HAL Customizable with Scripts or Answer Files Offline WIM file modification WIM files can share common files Can boot up from a disk image stored in a WIM file Doesn t erase existing disk data

15 Slide 14 Ways to Deploy Windows

16 Slide 15 Manual Deployment Booting from DVD Booting from a network share Answer Files

17 Slide 16 Manual Deployment From the WDS Active Directory DHCP DNS NTFS

18 Slide 17 Lite & Zero-Touch Deployment SCCM 2007 supports many tasks for both lite-touch and zero-touch installations Hardware inventory Distribution of the OS Providing the necessary authorizations Initiating the installation of software packages And many more features MDT Deployment Workbench WDS USMT

19 Slide 18 Topic B: Working with WDS Looking at Windows Deployment Services In depth look at the WDS Components Adding the WDS Role Basic and initial configuration of WDS Creating images with WDS Deploying Windows with WDS images

20 Slide 19 Looking at Windows Deployment Services Overview of WDS Upgrade from Windows RIS Replaces many of the WAIK tools

21 Slide 20 WDS Components Role Services: Deployment: Fully featured Requires AD, DNS, and DHCP Transport: Subset of the Deployment server Great for customizing standalone deployments and can utilize Multicast for a transport protocol to the destination machines Does not require AD, DNS, or DHCP

22 Slide 21 WDS Components Server Side Components Client Side Components Management

23 Slide 22 The WDS Role Installing WDS Server Full Role Installation: Provides the full functionality of WDS PXE Boot Services Microsoft Management Console tools Install image selection from the boot menu Unicast and multicast deployments

24 Slide 23 The WDS Role Transport Server Mode: Provides only the core networking components Useful in custom deployment scenarios Multicast deployments only WDSUTIL command-line tool management only Custom PXE provider creation required

25 Slide 24 Initial WDS Configuration The Image Store Types of images: Install Boot Capture Discover The Answer Policy

26 Slide 25 Initial WDS Configuration Default Boot Image Through the console Using WDSUTIL

27 Slide 26 Initial WDS Configuration Default install image Through the console Using WDSUTIL

28 Slide 27 Initial WDS Configuration Boot menu List of installed operating systems Different architecture types Limited to no more than 13 boot images Can be changed to the command line with bcdedit

29 Slide 28 WDS Server Properties General PXE Response Settings Directory Services Boot Client DHCP Networking Advanced

30 Slide 29 Image Capturing Images can be made for Server and Client versions of Windows Boot images Windows PE WDS Client Capture image Discover image

31 Slide 30 How Deployment Works Steps during a manual image deployment Boot the target computer Press F12 when prompted Select the desired image from the Boot menu

32 Slide 31 What Happens in the Background 30,000 foot view of the manual deployment DHCP Discover DHCP Response Connecting to the WDS Server File download from the TFTP Server Boot menu displayed Now Windows PE is installed and running

33 Slide 32 Topic C: Virtual Machine Deployment Understanding what a VM is Virtualization options with Microsoft Virtual PC 2007 Virtual Server 2005 Windows Server Virtualization (Hyper-V)

34 Slide 33 Understanding What a VM Is Benefits to Virtualization Consolidations Legacy applications and hardware Lab testing Better availability and uptime More efficient management

35 Slide 34 Prior Virtualization Options Virtual PC 2007 VHDs 64-bit support Many host options

36 Slide 35 Prior Virtualization Options Virtual PC 2007 continued Virtualized Network Host Guest Sharing

37 Slide 36 Prior Virtualization Options Virtual Server 2005 More advanced options than that of Virtual PC 2007 Supported non-windows guests High-availability options Expanded Virtual Networking capabilities Better management options P2V conversion capable

38 Slide 37 Hyper-V Hypervisor technology 64-bit guests Multicore and Multiprocessor capable More memory support Better performance Snapshots High-availability Required hardware and software

39 Slide 38 Hyper-V Disk Types Dynamically expanding Fixed Differencing

40 Slide 39 Hyper-V Networks Supported Network Types: External Internal Private Support for VLANs Overview of what is a VLAN Uses for VLANs

41 Slide 40 Hyper-V Networks Support for VLANs Overview of what a VLAN is Uses for VLANs

42 Slide 41 Topic D: Putting in an Activation Infrastructure Ways to Activate the Product Activation with MAK Activation with KMS Putting it all together

43 Slide 42 Windows Activation Types Overview of Activation Activation Types: MAK Model Volume Activation Management Tool KMS Model Configuring a KMS Host

44 Slide 43 The MAK Model What is MAK MAK independent activation MAK Proxy Activation

45 Slide 44 KMS Activation Overview of KMS Implementing KMS Activation Threshold Host Discovery Autodiscovery Direct Connection

46 Slide 45 KMS Activation Advantages Better for a large organization KMS infrastructure Disadvantages Not best for small networks Not best for lack of network connectivity

47

48 Review Questions: 1. What level of deployment automation requires no intervention from a user? A. Lite-Touch B. Zero-Touch C. No-Touch D. Basic 2. What command line tool can you use to create or install an image of Windows on a machine booted to the Windows PE? A. ImageX B. Windows SIM C. Sysprep D. PXE 3. True or False: You need only 5 MB of storage space on the hard drive to boot up to Windows PE. A. True B. False 4. Which tool is used to strip a Windows deployment of all of its uniquely identifying information? A. ImageX B. Windows SIM C. Sysprep D. PXE 5. What network roles and features must be available for you to use the fully featured WDS Server in your image deployment? A. DNS B. DHCP C. SMB D. AD DS E. All of the above F. A and B G. B, C, and D H. A, B, and D I. B and C

49 6. Which Microsoft role is used to store and respond to image deployment requests with Windows Server 2008? A. Ghost B. Remote Installation Server C. Windows Deployment Server D. Windows PE 7. Which role service for WDS Server provides only the core solution, and supports the use of multicast? A. Transport B. Broadcast C. Deployment D. Simulcast

50 Answer Key: 1. B The Zero-Touch Installation is designed as a complete hands-free method of deploying the Windows operating system. 2. A ImageX is a part of the WAIK tool set, and you can use this command to either capture and create an image from an existing system, or install an image to a target. Generally, in both cases, the source or target system has been booted to Windows PE. 3. B This is false. Windows PE only boots to a RAM drive, and even then only needs a minimum of 512 MB of memory to use. 4. C Sysprep, short for System Preparation, strips the unique and identifying information from the Windows system to get it ready for a new boot. 5. H DNS is used to translate the name of the PXE Server given to a client through DHCP to an IP address, and the AD DS Domain Controller is needed to authenticate either the user or the computer trying to pull down an image. 6. C WDS is the upgrade from the Windows 2003 RIS server. Ghost is a competing 3 rd party tool. 7. A Transport is the basic deployment option for the installation of the WDS Server. It contains the core of WDS, supports unicast/multicast, but it does not rely on any supporting Windows roles for functionality. And you will need to have a custom PXE environment for support.