Solution Training: Microsoft Solution forWindows-based Hosting version 4.0

Planning and Deploying Server Purposing

November 2006

Module Overview

• Overview of Server Purposing• What’s New in Server Purposing?• Getting Started with Server Purposing• Build Server Purposing• Use Server Purposing• Best Practices for Server Purposing

Overview of Server Purposing

Server purposing uses Microsoft Automated Deployment Services (ADS), a server deployment tool included with Microsoft Windows Server® 2003. With server purposing you can do the following:

– Prepare and configure multiple servers from bare metal to fully operational servers without manual interaction

– Ensure your security policies and processes are implemented on each system

– Ensure a consistent, standardized build process

Introduction to Automated Deployment Services

You can use ADS to:– Mount an image as a file and edit the image– Remotely purpose a device that has no operating system

to a useful state or repurpose a device from one state to another state

– Run extensible and configurable operations, such as scripts, on one or more systems from a single administration point

– Use the ADS Microsoft Windows® Management Instrumentation (WMI) Object Model to build custom applications

Benefits of Server Purposing

BENEFITS DESCRIPTION

Significant reduction of server deployment cost

An intelligent Pre-Boot eXecution Environment (PXE) server and dynamically built deployment agent enable remote server builds of PXE-compliant bare metal boxes, reducing the cost to deploy servers.

Consistency in provisioning servers, less human error

Through powerful task sequence-driven automation, sample task sequences can be extended to automate hardware configuration, operating system deployment, and application installation, enabling you to encode your organization's operational practices and eliminate human error.

Flexibility and agility through new imaging tools

Powerful new tools built by Microsoft use knowledge of the NTFS file system structure to create smaller images that can be updated and edited without first being deployed to a server.

Powerful, mass server administration

Through the reliable remote execution framework, ADS enhances existing scripting investments and extends your ability to administer hundreds of servers.

Simpler hardware configuration

Using Virtual Floppy, ADS incorporates standard server vendor MS-DOS® tools into the deployment process to automate hardware configuration.

Easy integration through a choice of user interfaces

ADS offers a simple-to-use graphical user interface, a set of command-line tools, and a rich WMI program interface.

Consistent record of administrative history

ADS offers a centralized data store to maintain a complete history of all administrative tasks carried out using the ADS infrastructure.

What’s New in Server Purposing?

• Windows-based Hosting version 4.0 uses the latest version of ADS, ADS 1.1

• ADS version 1.1 includes:– A rollup of bug fixes– Support for x64 platforms

Server Purposing Features

The Microsoft Solution for Windows-based Hosting version 4.0 contains these server purposing features:

– ADS Web• This extensible Web-based user interface provides easier

remote administration of ADS and additional functionality

– Unattended installation• This installation option enables you to use ADS to deploy an

operating system to servers (devices) with varying hardware configurations

– Sample scripts and task sequences• ADS now includes sample scripts and task sequences you can

use and edit to perform common ADS operations

For More Information: See the Advanced Server Purposing Topics section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

Getting Started with Server PurposingSTEP DESCRIPTION

1.Ensure that you have a single, 100-megabits per second (Mbps) or faster network to connect all devices, ADS servers, and the Dynamic Host Configuration Protocol (DHCP) server.

2.Determine whether you will install all of the ADS services on a single server or whether you plan to distribute the Controller service, the Image Distribution service (IDS), and Network Boot Services (NBS) on two or three servers.

3.

If you plan to capture and deploy images using ADS, ensure that a DHCP server is deployed in the data center. If not, you must add a DHCP server. If you plan to only install the Controller and Administrative Agent to create a scripting environment, a DHCP server is not required.

4.Determine whether PXE is in use in your data center. If so, you need to isolate PXE requests from the devices you plan to use with ADS from the rest of the network.

5.Determine which database you want to use with the Controller service. You can use Microsoft SQL Server™ Desktop Engine (MSDE), which is included with ADS, or an existing Microsoft SQL Server 2005 server.

6.Determine if there is an existing public key infrastructure (PKI) you want to use. If not, ADS will create certificates for you.

7. Confirm that your systems meet the requirements for ADS components.

8.Verify that the volumes where you plan to install ADS are formatted with the NTFS file system.

9.Ensure that the ADS services, the devices, and the Dynamic Host Configuration Protocol (DHCP) server are all part of the same network.

10ADS targets and the ADS controller must have the system basic input/output system (BIOS) clocks in close synchronization (within approximately 30 minutes). Typically, new hardware may have the BIOS clock set to an odd or random value.

11.Install Windows Server 2003, Enterprise Edition on the server on which you will install ADS.

For More Information: See “Get Started with Server Purposing” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

ADS Hands-off ImagingZero-touch server builds from bare metal

Database

HardDisk

RAM

PXE Firmware

Logs All Activity

ADS Controller

Bare metal server PXE boots and task sequence is initiated

Controller transfers deployment agent to RAM disk

Controller downloads MS-DOS image for hardware configuration

1

Deployment agent authenticates/requests image

Image is personalized and boots to full operating system with administration agent

Encrypted image is downloaded and deployed

PossiblyMulticast

Secure Sockets Layer (SSL)

Administration Agent Windows-Present

Deployment Agent Pre-Operating System

Target Server2

3

4

5

6

SSL

Script-based Administration

Initiate script-based administration on thousands of servers from the central controller

Gather all output from task and store in database

Administer 1,000 servers as easily as 1 server

Database

ADS Controller Administration Agent

Target Server

Administration Agent

Administration Agent

Log All Activity

Send Job (Script/Path)

1

2

ADS Architecture Single Server

DocumentationDocumentation

Administrative ToolsAdministrative Tools

ADS Management

Snap-in

ADS Management

Snap-in

Sequence Editor

Sequence Editor

Command-line Tools

Command-line Tools

Workstation

ADS Controller Server

DocumentationDocumentation

Administrative ToolsAdministrative Tools

ADS Management

Snap-in

ADS Management

Snap-in

Sequence Editor

Sequence Editor

Command-line Tools

Command-line Tools Volume Imaging

ToolsVolume Imaging

Tools

Network Boot ServicesNetwork Boot Services

Sample ScriptsSample Scripts

Image Distribution Service

Image Distribution Service

DHCPServer

Devices

ControllerDatabase

Controller ServiceController Service

Image Store

Computers That Host the ADS Services

ADS Services consist of the Controller service, Network Boot Service, and Image Distribution service. Computers that host the ADS services must meet these requirements:

For More Information: See “System Requirements for Server Purposing” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

COMPONENT DESCRIPTION NOTES

Processor x86-based architecture ADS 1.1 supported on the 64-bit Itanium-based architecture

Processor speed

1 gigahertz (GHz) minimum

Intel, Advanced Micro Devices (AMD), or compatible recommended

Operating system

Windows Server 2003, Enterprise Edition R2

ADS 1.1 supported on the 64-bit version Enterprise Edition

Hard disk 2 gigabytes (GB) free space for setup; additional for images

Windows-based Hosting recommends a 5-GB partition for the operating system source image

Memory256 megabytes (MB) of RAM recommended

Up to 32 GB of RAM supported; for computers with more than 4 GB, confirm hardware compatibility

LicenseVolume licensing with a single product ID recommended

CD-ROM For CD installation Can also use a DVD drive

Network Interface Card (NIC)

For network installation Requires server from which to offer network access for the setup files

MonitorVGA or higher-resolution monitor

As an alternative, for operation without a monitor or keyboard, you can choose a remote diagnostic and support processor that is designed for products in the Windows Server 2003 family

Computers Used to Remotely Administer ADS

You can install the ADS volume imaging tools, administration tools, and documentation on a separate x86-based computer and use it to remotely administer ADS. The workstation must run the English, Japanese, or German version of one of the operating systems listed in the following table:

For More Information: See “System Requirements for Server Purposing” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

OPERATING SYSTEM SERVICE PACK NOTES

Windows 2000 Professional

Service Pack 4 or later

Requires downloading and installing the .NET Framework runtime version 1.1 to run the Sequence Editor

Windows 2000 Server

Service Pack 4 or later

Windows 2000 Advanced Server

Service Pack 4 or later

Windows XP Professional

Service Pack 1 or later

Requires downloading and installing the .NET Framework runtime version 1.1 to run the Sequence Editor

Windows Server 2003, Standard Edition

R2 release

The required version of the .NET Framework runtime is includedWindows

Server 2003, Enterprise Edition

R2 release

Computers Used As Devices

You can use ADS to administer x86-based computers that are devices in your network and that meet the requirements listed in the table:

For More Information: See “System Requirements for Server Purposing” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

REQUIREMENTS DESCRIPTION

Windows operating system

Windows 2000 Server with Service Pack 4 or later Windows 2000 Advanced Server with Service Pack 4 or later Windows Powered with Service Pack 4 or later Windows Server 2003, Standard Edition Windows Server 2003, Web Edition Windows Server 2003, Enterprise Edition

Administration Agent

Pre-Boot eXecution Environment (PXE)

Version 0.99c or later enabled network adapter

Updated BIOS for certain servers functioning as devices

Dell PowerEdge 2650 update Compaq/Hewlett-Packard ProLiant DL360 G2 servers

Computers in a Network

Make sure computers in your network meet the requirements shown in the table:

For More Information: See “System Requirements for Server Purposing” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

REQUIREMENTS NOTES

All devices in the network must reside in the same multicast domain as the Imaging Distribution service

Multicast Domain:Hosts listen for specific IP multicast address and receive all information for that address.

All devices in the network must reside in the same broadcast domain as the ADS PXE service and DHCP server

Broadcast Domain:All the hosts on the same physical network bounded by IP routers share the same broadcast traffic.

All services and devices must be connected to the same network

If the ADS services are installed on separate servers, they must communicate over the same network adapter to access the devices on the network.

DHCP server can be an existing DHCP server in the test network or DHCP services can be installed on the same computer running the ADS Controller service

DHCP server software comes with Windows 2000 Advanced Server or Windows Server 2003, Enterprise Edition.

To build your ADS Controller, you perform the following set of tasks:

Ensure prerequisites are met

Install Windows Server 2003, Enterprise Edition R2

Add and configure DHCP services

Install and configure ADS Controller software

Verify ADS Installation

Build Server Purposing

For More Information: See “Build Server Purposing” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

1

2

3

4

5

Install Windows Server 2003, Enterprise Edition

1. Perform a default installation of Windows Server 2003, Enterprise Edition R2

2. Apply any released updates to Windows Server 2003

Add and Configure DHCP Services

• Before building your server hosting the ADS controller, configure DHCP to use Network Boot Services (NBS)

• If DHCP is not currently installed on ADSC01, add DHCP to the server and configure DHCP with addresses on your provisioning network for the DNS server and the domain (fabrikam.com)

Note: If DHCP is installed prior to installing ADS, the ADS Installation wizard will modify DHCP to work properly

Install and Configure ADS Controller Software

To build your ADS Controller, you perform the following set of tasks:

Install the ADS software on the designated ADS controller(ADS component services can be located on multiple servers to increase performance)

Configure Controller service discover options

Add sample jobs to the Controller

Share the Controller certificate

1

2

3

4

Note: It is important to read the Readme file or release notes that accompany the version of ADS that you download

Verify ADS Installation

• Verify the installation of ADS by running jobs on a destination device

• Perform the following tests:– Confirm the Controller service discovery options– Run the PXE boot verification test– Verify the PXE boot and Controller functionality

Use Server Purposing

• Overview of capturing and deploying images– Flexible image capture

• Local (using Windows Preinstallation Environment [Windows PE]) or Remote (using deployment agent)

– Requires Sysprep (included in Windows Server)

– Hardware independence• With Sysprep, you only need one image per Hardware

Abstraction Layer (HAL)– Computers not compliant with Advanced Configuration

and Power Interface (ACPI) will require different image– Single-processor computers will have degraded

performance running images with multiprocessor HALs

– Versatile set of imaging tools• Imaging can be driven from the Microsoft Management

Console (MMC), command-line tools, or Web interface (ADS Web)

For More Information: See “Create and Deploy an Image” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

Use ADS to Capture and Deploy Images (1 of 2)

For More Information: See “Create and Deploy an Image” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

Create a master image

Install an operating system

Analyze the master image

Install the Administration Agent

Run Sysprep

Install the IP configuration script

1

2

3

4

5

Use ADS to Capture and Deploy Images (2 of 2)

For More Information: See “Create and Deploy an Image” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

Capture and deploy a master image

Prepare the image capture sequence

Run the Utils Capture Sequence (Compaq DL360 computers only)

Run the image capture sequence

Edit the deployment task sequence

Discover and configure devices

1

2

3

4

5

Run the image capture sequence

Deploy an image to a destination device

Verify disk images

6

7

8

How ADS Deploys anOperating System

Common ADS Tasks

The ADS product documentation provides descriptions on how to perform these common ADS tasks:

– Configure ADS services– Manage Network Boot Services– Manage images– Manage devices– Manage sets– Manage jobs– Manage job templates– Manage ADS certificates– Back up and restore ADS

For More Information: See the Windows Server 2003 Automated Deployment ServicesWeb site at http://www.microsoft.com/windowsserver2003/technologies/management/ads/default.mspxi

Best Practices for Server Purposing

• Security Best Practices• Best Practices for Configuring ADS• Controller Best Practices• Network Boot Services (NBS) Best Practices• Best Practices for Images

For More Information: See “Best Practices for Server Purposing” in the Server Purposing section of the Microsoft Solution for Windows-based Hosting version 4.0 documentationi

Questions and Answers

© 2006 Microsoft Corporation. All rights reserved.Microsoft, MS-DOS, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United

States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and

Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Schedules and features contained in this document are subject to change.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, places, or events is intended or

should be inferred.