Module 10: Designing Operating System Deployment and Maintenance
Module Overview
Determining Operating System Deployment Requirements Designing Windows Deployment Services
Windows Deployment Services Images
Designing Multicast Transmission of Images Designing a Software Update Process
Lesson 1: Determining Operating System Deployment Requirements
Reasons for Planning the Operating System Deployment Design Options for Deploying Operating Systems
Determining Storage Requirements
Security Considerations for Operating System Deployment Tools for Operating System Deployment
Reasons for Planning the Operating System Deployment
Reasons for operating system deployment planning:
Ensuring continued productivity during workstation rollouts Ensuring critical network services continue to be available during server upgrades or installations Alleviating application compatibility issues Ensuring new features are evaluated properly and all impacts to the current environment are considered Ensuring all deployment processes and scripts are properly tested
Design Options for Deploying Operating Systems
Options
Bare metal Light touch Zero touch
Description
Install on computer without existing software Limited manual interaction No manual interaction
Determining Storage Requirements
Storage requirements include:
Deployment images User state migration data Computer backups Application and operating system source files
Security Considerations for Operating System Deployment
Security considerations for operating system deployment planning:
Secure user credentials, PIDS, company information, or other restricted data in answer files, log files or image files
Secure the storage locations for images, user state, and backups
Scan source and destination computers for viruses
Do not transmit data over the Internet unless the connection is encrypted Secure the PXE network boot process to prevent unauthorized users from joining computers to the domain Windows Server 2008 domain controllers do not allow the NETSETUP_JOIN_UNSECURE option
Tools for Operating System Deployment
Tool
Windows Automated Installation Kit (WAIK) Business Desktop Deployment (BDD) Microsoft Deployment Solution Accelerator Windows Deployment Services System Center Configuration Manager
Description
Generates unattended installation files
Configures Lite and Zero Touch
installations
Next version of BDD including detailed
guidance on operating system deployment
Windows Server 2008 service for
deploying operating system images
Enhances operating system deployment
for images or unattended installations with additional security
Lesson 2: Designing Windows Deployment Services
Enhanced Features in WDS Network Infrastructure Requirements
Comparing Transport Server and Deployment Server
Considerations for Upgrading from RIS to WDS Considerations for Designing WDS
Designing WDS Deployment
Enhanced Features in WDS
Enhanced features in WDS from RIS are:
Support for deployment of Windows Vista and Windows Server 2008 Higher performing PXE and TFTP servers
New boot menu format
Support for .wim format Windows PE as boot operating system
Multicast support
Network Infrastructure Requirements
Requirement
Active Directory Domain Services DHCP
domain.
Description
WDS server must be a member of a
Configures workstations with an IP
during PXE boot
DNS
NTFS volume
Required for WDS server
Required for image storage Must be a local administrator on WDS
Credentials
server to install client
Must be a domain user to start WDS
Comparing Transport Server and Deployment Server
Deployment Server
Server requirements
PXE Image server Transmission method Management tools Client
Requires AD DS, Dynamic Host Configuration Protocol (DHCP), and Dynamic Name Services (DNS) in the environment Supports PXE boot with the default PXE provider Includes the Windows Deployment Services Image Server (WdsImgSrv) Allows unicasting and multicasting You manage using the Windows Deployment Services MMC snap-in or WDSUTIL
Transport Server
Does not require other servers
in the environment
Supports PXE boot using the
default PXE provider, or if you have a custom PXE provider Deployment Services Image Server (WdsImgSrv)
Does not include the Windows
Allows only multicasting
You manage with WDSUTIL only
Use the Windows Deployment Services client, WDSMCAST, or custom multicast client application
Use WDSMCAST or custom
client application only
Considerations for Upgrading from RIS to WDS
Windows Server 2003 RIS to Windows Server 2008 WDS upgrade process: Upgrade RIS to WDS on Windows Server 2003 Change WDS from legacy mode to native mode Upgrade to Windows Server 2008
Considerations for Designing WDS
Considerations for designing WDS are:
IPv6 is not supported for this version of Windows Deployment Services You should use only the [Link] file from the Windows Server 2008 DVD If you are running Windows Deployment Services and a nonMicrosoft DHCP server on the same computer, in addition to configuring the server to not listen on UDP port 67, you will need to use your DHCP tools to add Option 60 to their DHCP scopes
If DHCP is installed on a server that is located on a different subnet, you will need to do one of the following:
Configure DHCP relay to the DHCP server and WDS PXE server Add DHCP options 66 and 67
Discussion: Designing WDS Deployment
How will you implement WDS in your organization?
Lesson 3: Windows Deployment Services Images
Features of WDS Images Image Capture Utilities
Discussion: Considerations for Creating a Custom Install
Image
Considerations for Maintaining Boot and Install Images
Features of WDS Images
Boot images:
Are used to perform the imaging process
Install images:
Include the operating system Are in WIM format Multiple images can be stored in a single image group Sysprep must be used before creation ImageX can be used to manually create an image
Are based on WindowsPE
Capture images are used to image a sysprepped workstation
Discover images are used to perform imaging on non-PXE clients
Image Capture Utilities
Functionality
Captures a partial volume? Captures a non-Sysprep image? Specifies compression type? Uploads directly to WDS Server? Can the process be automated? Has a GUI? Provides additional functionality beyond image capture? Specifies capture exclusion list? Captures directly to network location without making a local image copy? No No
WDSCapture
Yes Yes
ImageX
Yes: only LZX or XPRESS
Yes Yes Yes No Yes
Yes: LZX, XPRESS, or no compression
No Yes No Yes Yes
No
Yes
Discussion: Considerations for Creating a Custom Install Image
What are the considerations for creating a custom install image?
Considerations for Maintaining Boot and Install Images
Boot images:
Must be Windows PE in .wim format
Must be marked as boot from RAMDISK
Install images:
Windows Vista can only be rearmed three times You can mount and edit offline images by using ImageX Editing offline images is not suitable for application installs You must export the image from WDS to edit offline
[Link] must not be older than the operating system being deployed
Must have all necessary drivers
Lesson 4: Designing Multicast Transmission of Images
Scenarios for Using Multicasting Types of Multicast Transmissions
Considerations for Designing Multicast Transmissions
Scenarios for Using Multicasting
Use multicasting when:
Network routers support multicasting
You require many concurrent installations
You need to minimize network traffic
There is enough disk space on the client to download the image before installing
Types of Multicast Transmissions
Auto-cast:
Multicast begins when a single computer requests it Additional computers can join in
Scheduled-cast:
Multicast begins when criteria are met Criteria are: number of clients joined or specific day and time
Clients cannot join after multicast has started
Considerations for Designing Multicast Transmissions
Considerations for designing multicast transmissions are:
All routers must support multicasting [Link] from Windows Vista does not support multicasting If multiple servers are using multicast, they must use unique multicast addresses Use MADCAP to avoid conflicting multicast addresses You must restart WDS for network configuration changes to take effect
Lesson 5: Designing a Software Update Process
Overview of Update Management Tools How WSUS Works
WSUS Deployment Scenarios
Guidelines for Planning WSUS Infrastructure
Overview of Update Management Tools
Software update management tools are:
Microsoft and Windows Update
Automatic Updates client Microsoft Baseline Security Analyzer
Windows Server Update Services
System Center Configuration Manager 2007
How WSUS Works
The process for applying updates by using WSUS:
1. The WSUS server downloads specified update types 2. Updates are approved by an administrator 3. The Automatic updates client retrieves and installs updates from the WSUS server
WSUS Deployment Scenarios
WSUS deployment scenarios are:
Single WSUS server Multiple independent WSUS servers Multiple internally synchronized WSUS servers Disconnected WSUS servers
Guidelines for Planning a WSUS Infrastructure
When planning the number and placement of servers:
Connect one WSUS server to the Internet
Chain WSUS servers
Place servers close to client computers
When planning the configuration of servers:
Download updates in the languages required Use a local database or Microsoft Update Create a synchronization schedule for downloads
Lab: Designing Operating System Deployment and Maintenance
Exercise 1: Designing an Operating System Deployment
Solution
Exercise 2: Designing WDS Deployment Exercise 3: Designing WDS Images Exercise 4: Designing a WSUS Deployment Exercise 5: Discussing Operating System Deployment and
Maintenance Images
Exercise 6: Implementing Multicast Transmissions for
Logon information
Virtual machine User name Password
NYC-DC1
Administrator Pa$$w0rd
Estimated time: 90 minutes
