Information Technology Reference
In-Depth Information
4. Right-click the Active Directory Users and Computers node again , point to All Tasks , and
click Operations Masters .
5. In the Operations Masters dialog box, click the Infrastructure tab. Click the Change button
to transfer the infrastructure master to Server1XX.
6. Click Yes when asked to confirm the transfer, and then click OK in the success message.
Notice that Server1XX is shown as the operations master in the Infrastructure tab. Click
Close .
7. Close Active Directory Users and Computers.
The procedure to transfer the PDC emulator and RID master roles is similar to transferring
the infrastructure master role.
Seizing Operations Master Roles An operations master role is seized when the cur-
rent role holder is no longer online because of some type of failure. Seizing should never be done
when the current role holder is accessible and should usually be done only when it's unlikely the
original server can be restored to service. If a DC is scheduled to be decommissioned, you should
transfer the role while the DC is still online. If the operations master DC becomes inaccessible
because of network failure or a temporary hardware failure, you should wait until this server is
back online rather than seize the operations master role.
An exception might be the PDC emulator role, which can affect user logons, or the RID
master, which might be needed to create Active Directory objects. If either role holder is going
to be offline for an extended period, seizing the role and then transferring it to the original DC
when it's back online might be best for continued Active Directory operation. To seize an oper-
ations master role, follow these steps:
1. Open a command prompt window, type ntdsutil , and press Enter .
2. Type roles and press Enter to get the FSMO Maintenance prompt.
3. Type connections and press Enter to get the Server Connections prompt.
4. Type connect to server DCName , replacing DCName with the domain controller where
you're transferring the FSMO role.
5. Type quit to get back to the FSMO Maintenance prompt.
6. Type seize RoleName and press Enter , replacing RoleName with the name of the role you
want to seize. Possible role names are domain naming master, schema master, PDC, RID
master, and infrastructure master.
7. Windows attempts to transfer the role first, and if a transfer fails, the role is seized. Type
quit and press Enter to exit Ntdsutil.
Chapter Summary
Instead of requiring administrators to upgrade all current servers before installing a new
server version, administrators can configure functional levels on new domain controllers to
maintain backward compatibility.
Functional levels can be raised from an earlier version to a newer version but can't be
changed from a newer version to an earlier version.
Windows Server 2008 supports three forest functional levels: Windows 2000, Windows
Server 2003, and Windows Server 2008. The supported domain functional levels have
nearly identical names. A domain controller can't be configured to run at a lower domain
functional level than the functional level of the forest in which it's installed.
You can raise the functional levels when you run Dcpromo.exe to install Active Directory
(the recommended method), or you can raise them manually. Before you raise functional
levels, be sure your domain controllers meet the requirements for the functional level you
want.
 
Search WWH ::




Custom Search