replicate the schema and configuration partition to the new first domain controller using iManager.
For more information, see
edir88/data/fbgciaad.html)
18.2.1 To Transfer the PDC Emulator Role from the First
Domain Controller to a Subsequent Domain Controller
In this scenario, the machine functioning as the first domain controller is functional. But you want to
transfer the PDC Emulator role from the first domain controller to an another domain controller for
load-balancing purposes.
From the machine that will serve the new PDC Emulator role, execute the following steps:
1 Transfer all the FSMO roles using the MMC utility. For details, see
FSMO Roles (http://support.microsoft.com/kb/255690)
2 Get the domain administrator's kerberos ticket by executing following command:
/opt/novell/xad/bin/kinit Administrator@_DOMAIN NAME_
3 Update the samba configuration, msdfs links and the DNS SRV record for the first domain
controller by running the following script:
/opt/novell/xad/share/dcinit/UpdatePDCMaster.p
18.2.2 To Seize PDC Emulator Role from First Domain
Controller to an Another Domain Controller (DNS is Functional)
In this scenario, the directory services on the first domain controller has gone down but the DNS
service is up. As the directory services are not functional, the FSMO roles have to be forcibly seized
and transferred to an another domain controller using the following procedure:
1 From the Windows workstation joined to the domain, seize all the FSMO roles using the
utility.
ntsdutil
2 From the machine that will serve as the new domain controller, get the domain administrator's
kerberos ticket by executing following command:
/opt/novell/xad/bin/kinit Administrator@_DOMAIN NAME_
3 Update the samba configuration, msdfs links and the DNS SRV record for first domain
controller by running the following script:
/opt/novell/xad/share/dcinit/UpdatePDCMaster.p
18.2.3 To Seize PDC Emulator Role from First Domain
Controller to an Another Domain Controller (DNS is Not
Functional)
In this scenario, the directory service and the DNS service is not functional. To resolve this, the DNS
service has to be migrated to the new domain controller and the FSMO roles also have to be forcibly
seized and transferred to an another domain controller using the following procedure:
1 From the Windows workstation joined to the domain, seize all the FSMO roles using the
utility.
ntsdutil
Administering Replicas (http://www.novell.com/documentation/edir88/
How to View and Transfer
l
l
Flexible Single Master Operation (FSMO) Roles 203
Need help?
Do you have a question about the OPEN ENTERPRISE SERVER 2.0 SP2 - DOMAIN SERVICE FOR WINDOWS and is the answer not in the manual?
Questions and answers