If you are installing the first read-only domain controller in an existing forest, you need connectivity to the infrastructure master for each application directory partition, also known as a non-domain naming context or NDNC.īe sure to supply the necessary credentials to run the AD DS installation. Any domain controller installation also requires connectivity to the RID master. To install or remove a domain in an existing forest, you need connectivity to the domain naming master. To install the first DC in a domain where the forest schema is already extended, you only need connectivity to infrastructure master. To install the first DC that runs Windows Server 2012 in an existing domain and forest, the machine where you run the installation needs connectivity to the schema master in order to run adprep /forestprep and the infrastructure master in order to run adprep /domainprep. For more information, see Deprecated features and behavior changes related to AD DS in Windows Server 2012 and Secure default settings in Windows Server 2008 and Windows Server 2008 R2.Ĭheck connectivity to the target server from the computer where you plan to run the installation.Ĭheck for availability of necessary operation master roles: Verify the target server meets system requirements. This list covers general steps to follow before you promote a domain controller that runs a newer version of Windows Server: 
That method is preferable to upgrading the operating system of an existing domain controller.
The recommended way to upgrade a domain is to promote domain controllers that run newer versions of Windows Server and demote older domain controllers as needed. This topic provides background information about Active Directory Domain Services in Windows Server 2012 R2 and Windows Server 2012 and explains the process for upgrading domain controllers from Windows Server 2008 or Windows Server 2008 R2. Upgrade Domain Controllers to Windows Server 2012 R2 and Windows Server 2012Īpplies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
0 kommentar(er)
