AD DS Design and Planning
Applies To: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
By deploying Windows Server Active Directory Domain Services (AD DS) in your environment, you can take advantage of the centralized, delegated administrative model and single sign-on (SSO) capability that AD DS provides. After you identify the deployment tasks and current environment for your organization, you can create the AD DS deployment strategy that meets your organization's needs.
About this guide
This guide provides recommendations to help you develop an AD DS deployment strategy based on the requirements of your organization and the particular design that you want to create. This guide is intended for use by infrastructure specialists or system architects. Before you read this guide, you should have a good understanding of how AD DS works on a functional level. You should also have a good understanding of the organizational requirements that will be reflected in your AD DS deployment strategy.
This guide describes sets of tasks for several possible starting points of a Windows Server 2008 AD DS deployment. The guide helps you determine the most appropriate deployment strategy for your environment.
Although the strategies that are presented in this guide are appropriate for almost all server operating system deployments, they have been tested and validated specifically for environments that contain fewer than 100,000 users and fewer than 1,000 sites, with network connections of a minimum of 28.8 kilobits per second (Kbps). If your environment does not meet these criteria, consider using a consulting firm that has experience deploying AD DS in more complex environments.
For more information about testing the AD DS deployment process, see the article Testing and Verifying the Deployment Process.
In this guide
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.