大网数据广告活动
域与目录服务

Mapping Your Requirements to an AD DS Deployment Strategy

· 52CE 我爱测

Learn more about: Mapping Your Requirements to an AD DS Deployment Strategy

After you finish reviewing and identifying the Active Directory Domain Services (AD DS) design and deployment requirements and you determine which of them are related to your specific deployment, you can map those requirements to a specific AD DS deployment strategy.

Use the following table to determine which AD DS deployment strategy maps to the appropriate combination of AD DS design and deployment requirements for your organization. ("Yes" means that a specific requirement is necessary for your deployment strategy; "No" means that a specific requirement is not necessary for your deployment strategy.)

This table refers only to the three primary AD DS deployment strategies as described in this guide:

However, you can create a hybrid or custom AD DS deployment strategy by using any combination of the AD DS design and deployment requirements to meet the needs of your organization.

AD DS design and deployment requirements Deploying AD DS in a New Organization Deploying AD DS in a Windows Server 2003 Organization Deploying AD DS in a Windows 2000 Organization
Designing the Logical Structure for Windows Server 2008 AD DS Yes Yes Yes
Designing the Site Topology for Windows Server 2008 AD DS Yes Yes Yes
Planning Domain Controller Capacity Yes Yes Yes
Deploying a Windows Server 2008 Forest Root Domain Yes No No
Deploying Windows Server 2008 Regional Domains Yes Yes Yes
Enabling Advanced Features for AD DS Yes Yes, but all domain controllers in the environment must run Windows Server 2008 before you set the domain or forest functional level to Windows Server 2008. Yes, but all domain controllers in the environment must run Windows Server 2008 before you set the domain or forest functional level to Windows Server 2008.
Upgrading Active Directory Domains to Windows Server 2008 and Windows Server 2008 R2 AD DS Domains No Yes Yes
ADMT Guide: Migrating and Restructuring Active Directory Domains Yes, if you want to migrate a pilot domain into your production environment, merge with another organization and consolidate the two information technology (IT) infrastructures, or consolidate resource and account domains that you upgraded in place from Windows 2000 or Windows Server 2003 environments. Yes, if you want to merge with another organization and consolidate the two IT infrastructures or consolidate resource and account domains that you upgraded in place from Windows 2000 or Windows Server 2003 environments. Yes, if you want to merge with another organization and consolidate the two IT infrastructures or consolidate resource and account domains that you upgraded in place from Windows 2000 or Windows Server 2003 environments.
ADMT Guide: Migrating and Restructuring Active Directory Domains No Yes, if you need to reduce the number of domains, reduce replication traffic and the amount of required user and group administration, or simplify the administration of Group Policy. Yes, if you need to reduce the number of domains, reduce replication traffic and the amount of required user and group administration, or simplify the administration of Group Policy.

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: robinharwood). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 05/12/2025
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。