3. Existing forest domain controller deployment
There are two basic ways of deploying Windows Server 2012 domain
controllers in a forest whose domain controllers are running earlier
versions of Windows Server:
The sections that follow provide more details about these
approaches.
Note
Upgrading domain
controllers
Although performing in-place upgrades can help reduce hardware
costs, the margin for error is greater. If possible, avoid
performing in-place upgrades of your existing domain controllers;
instead, introduce new domain controllers and then, if desired,
retire your existing domain controllers.
Installing additional domain controllers
Installing additional domain controllers that are running
Windows Server 2012 in a forest whose domain controllers are running
an earlier version of Windows Server involves the following
steps:
-
Install Windows Server 2012 on the servers that will
become the new domain controllers.
-
Join the new servers to the domain.
-
Use Server Manager or Windows PowerShell to install the AD
DS role on the new servers, and promote them to domain
controllers.
Once deployed, the new Windows Server 2012 domain controllers
can coexist with the domain controllers running earlier versions of
Windows Server if you want them to. Alternatively, you can move the
flexible single master operations (FSMO) roles from the earlier
domain controllers that are running earlier versions of Windows
Server to the new domain controllers that are running Windows Server
2012, and finally demote and retire the earlier domain
controllers.
Note
Preparing the schema
Introducing Windows Server 2012 domain controllers into a
forest whose domain controllers are running earlier versions of
Windows Server automatically causes the AD DS schema to be
extended to the latest version.
