Introduction

This guide focuses on the design of the deployment services solution.

The Windows Server System Reference Architecture (WSSRA) deployment services design was created using the guidance provided in the Reference Blueprints, specifically the Deployment Services Blueprint. The designs detailed in this guide were formulated using real world scenario specifications, specifically the Centralized Data Center (CDC) and Satellite Branch Office (SBO) scenarios. These scenarios are outlined in the Introduction to Windows Server System Reference Architecture document, and a further level of detail is provided in the Lab Implementation of Windows Server System Reference Architecture document.

On This Page

	Who Should Read This Guide
	Knowledge Prerequisites
	Business Need

Who Should Read This Guide

This guide is written for information technology (IT) professionals who are responsible for the design and implementation of a deployment service infrastructure in enterprises that are similar in scale and scope to the CDC or SBO scenarios. This guide provides service-level guidance, and the reader is expected to be able to follow the technical discussions and understand the details provided.

Top of page

Knowledge Prerequisites

The reader should have a practitioner-level understanding of deploying the Windows operating system, target server hardware, and networking. In addition, the reader should have specific knowledge and experience of working with the following technologies:

Top of page

Business Need

The deployment service design needs were defined in the Reference Blueprints and are summarized as follows:

The reliable deployment of software onto servers is required for hosting enterprise services. Creating a deployment service solution involves addressing several key issues, including support for disparate hardware; support for new hardware, software, and enterprise services; loss of knowledgeable staff; and reduction of human error and cost of problem resolution.

A natural solution involves completely automated computer builds; however, such a solution usually involves significant development costs. A solution that uses a mix of automation and manual tasks generally yields the best return on investment. The best approach is to first automate those tasks that are more prone to human error to reduce troubleshooting costs and to produce a more reliable and repeatable computer build. Next, automate mundane repetitive tasks to increase the number of computers that can be simultaneously built and reduce the operator skill level required. Once these tasks have been automated, more automation can enable the organization to support more services and provide newer support services to their clients.

Top of page