Introduction

Published: March 31, 2005

An automated server deployment service can reduce the time required for installing and configuring servers and enhance the overall quality of each deployment. Automated deployment ultimately leads to a reduced total cost of ownership (TCO) through reduced deployment and operational support costs.

This blueprint focuses on designing a solution for automating the software installation and configuration of servers in an organization's data center. As the design process is explained in this blueprint, a number of design options will be discussed along with their advantages and disadvantages.

Specific implementation details of how the Windows Server System Reference Architecture (WSSRA) product team used this guidance to build a test instance are provided in the Deployment Services Planning Guide and the Deployment Services Build Guide.

On This Page
Who Should Read This BlueprintWho Should Read This Blueprint
Knowledge PrerequisitesKnowledge Prerequisites
Business NeedBusiness Need
ReferencesReferences

Who Should Read This Blueprint

This blueprint is written for information technology (IT) professionals who are responsible for designing and implementing a server deployment service in enterprise environments. The reader of this blueprint is expected to have an understanding of its technical details; however, service-level expertise is not needed to follow the enterprise-level discussions and understand the decisions that are made.

Knowledge Prerequisites

This blueprint assumes a knowledge level equivalent to an IT professional with at least two years of experience as a Microsoft Certified Systems Engineer (MCSE). Readers who do not meet this prerequisite may also benefit from this guidance, although additional reading might be required to ensure that the relevant terms and processes are understood. The reader should also have a good working knowledge of the Windows operating system installation process, the target server hardware, and networking.

The “References” section at the end of this blueprint provides addresses of Web sites that provide further information on deployment technologies.

Business Need

The reliable deployment of software onto servers is a requirement for hosting enterprise services. Organizations face many issues when deploying software, including:

Disparate hardware: A varied vendor pool for hardware can result in deployment issues because builds must be tailored for each platform (Gartner, Where Cost Reductions Lie: Total Cost of Ownership (TCO) Lessons Learned, 02 March 2001).

Solution support: Many in-house solutions are built around custom applications. Once the developer of an application leaves an organization, it may become impossible to support the application.

Support boundaries: Using a variety of deployment solutions from different vendors can lead to disputes around support boundaries. Such disputes may result in higher organizational support costs as well as lower confidence in the solution.

Inflexibility: Many solutions are tailored for very specific scenarios. As requirements change or new versions of operating systems or drivers are released, updates can be difficult to integrate and lead to the build solution being discarded in favor of a handcrafted solution.

Auditing: It is important that there is a high degree of confidence in a build's quality and the settings or components installed during the build process. Audit logs can be used to confirm that a build was successful and help in troubleshooting problems when they occur.

Maintenance: Changes in requirements or operating system versions cause modifications in the build solution, which means it should be adaptable. Build modifications must be documented to maintain confidence in the build and also help in troubleshooting failed builds.

Human error: A fully automated solution reduces the probability of typing mistakes that may lead to faulty builds during manual deployment. Therefore, human involvement in the build process should be kept to a minimum.

Organizations also strive to keep the costs of operating a data center as low as possible. While deploying a server only makes up a fraction of the cost of running a service (Gartner: Information Technology (IT) Asset Management: The ‘E’ of Life-Cycle Management, 20th April 2001), a consistently well-deployed operating system can reduce the time spent on troubleshooting.

Installing the operating system and associated layered products in a progressive manner can rapidly become complex as the number of items to configure goes up. Such items include different computer models, operating system components, network settings, layered products and associated configuration settings, patches, and security settings. Managing thousands of configuration parameters for a build can be a daunting task.

References

Further information about Windows Server 2003 and deployment services may be found at the following URLs:

Windows Server 2003 Deployment Kit:

http://www.microsoft.com/windowsserver2003/techinfo/reskit/deploykit.mspx

Windows Server 2003 Resource Kit:

http://www.microsoft.com/windowsserver2003/techinfo/reskit/resourcekit.mspx


**
**