J
jjohnson
We recently tried to install a new domain controller to replace our
old one. The new domain controller is running windows server 2003. I
ran dcpromo on the new controller and made it an additional domain
controller, I then made it seize all FSMO roles. The sad part is is I
ran DCPROMO to demote the old domain controller before everythign
replicated through. Therefore, because everything is out of sync we
ran directory services restore, and restored it to the pre new dc
state. However, because the exchange 2000 box is also a domain
controller the records been somewhat mangled in replication to the
point that the current FSMO role holder which is the old domain
controller does not realize it itself is the FSMO holder. I also went
in DNS and replaced all of the records that had the new DC as the FSMO
to the old one. The new domain controller is totally out of the
picture, until I get this fixed. The bottom line is this is what I get
when I run DCDIAG on my FSMO role holder.
Results:
Doing initial required tests
Testing server: KoyoCorp\KCUOBGENT01
Starting test: Connectivity
......................... KCUOBGENT01 passed test
Connectivity
Doing primary tests
Testing server: KoyoCorp\KCUOBGENT01
Starting test: Replications
......................... KCUOBGENT01 passed test
Replications
Starting test: NCSecDesc
......................... KCUOBGENT01 passed test NCSecDesc
Starting test: NetLogons
......................... KCUOBGENT01 passed test NetLogons
Starting test: Advertising
......................... KCUOBGENT01 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: CN="NTDS Settings
DEL:fbeae0d9-5525-4fdd-9212-e9636c29e338",CN="KCUOBGDC01
DEL:9a02a90f-732f-41f3-beff-
f78d84df550e",CN=Servers,CN=KoyoCorp,CN=Sites,CN=Con
figuration,DC=koyocorp,DC=com is the Schema Owner, but is deleted.
Warning: CN="NTDS Settings
DEL:fbeae0d9-5525-4fdd-9212-e9636c29e338",CN="KCUOBGDC01
DEL:9a02a90f-732f-41f3-beff-
f78d84df550e",CN=Servers,CN=KoyoCorp,CN=Sites,CN=Con
figuration,DC=koyocorp,DC=com is the Domain Owner, but is deleted.
......................... KCUOBGENT01 failed test
KnowsOfRoleHolders
Starting test: RidManager
No rids allocated -- please check eventlog.
......................... KCUOBGENT01 passed test RidManager
Starting test: MachineAccount
......................... KCUOBGENT01 passed test
MachineAccount
Starting test: Services
......................... KCUOBGENT01 passed test Services
Starting test: ObjectsReplicated
......................... KCUOBGENT01 passed test
ObjectsReplicated
Starting test: frssysvol
......................... KCUOBGENT01 passed test frssysvol
Starting test: kccevent
......................... KCUOBGENT01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x0000410A
Time Generated: 05/28/2008 09:23:29
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000410A
Time Generated: 05/28/2008 09:54:29
(Event String could not be retrieved)
......................... KCUOBGENT01 failed test systemlog
Running enterprise tests on : koyocorp.com
Starting test: Intersite
......................... koyocorp.com passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
......................... koyocorp.com failed test FsmoCheck
Also, I seen on other threads with similar issues, I should seize the
role, however I get a error when I try to seize the role
(LsaOpenPolicy error 0x6ba(The RPC server is unavailable.)
Everything is working, as far as users logging on, and basic group
policy. However, I cannot change any group policies such as password
complexity, lockout settings, and PDC type settings because these are
specific to the FSMO holder, and it is currently only letting me
access the policies on the mail server.
Anyone know where I can start to get on the road to fixing this
problem I have gotten myself into?
Thanks in advance,
Jonathan Johnson
old one. The new domain controller is running windows server 2003. I
ran dcpromo on the new controller and made it an additional domain
controller, I then made it seize all FSMO roles. The sad part is is I
ran DCPROMO to demote the old domain controller before everythign
replicated through. Therefore, because everything is out of sync we
ran directory services restore, and restored it to the pre new dc
state. However, because the exchange 2000 box is also a domain
controller the records been somewhat mangled in replication to the
point that the current FSMO role holder which is the old domain
controller does not realize it itself is the FSMO holder. I also went
in DNS and replaced all of the records that had the new DC as the FSMO
to the old one. The new domain controller is totally out of the
picture, until I get this fixed. The bottom line is this is what I get
when I run DCDIAG on my FSMO role holder.
Results:
Doing initial required tests
Testing server: KoyoCorp\KCUOBGENT01
Starting test: Connectivity
......................... KCUOBGENT01 passed test
Connectivity
Doing primary tests
Testing server: KoyoCorp\KCUOBGENT01
Starting test: Replications
......................... KCUOBGENT01 passed test
Replications
Starting test: NCSecDesc
......................... KCUOBGENT01 passed test NCSecDesc
Starting test: NetLogons
......................... KCUOBGENT01 passed test NetLogons
Starting test: Advertising
......................... KCUOBGENT01 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: CN="NTDS Settings
DEL:fbeae0d9-5525-4fdd-9212-e9636c29e338",CN="KCUOBGDC01
DEL:9a02a90f-732f-41f3-beff-
f78d84df550e",CN=Servers,CN=KoyoCorp,CN=Sites,CN=Con
figuration,DC=koyocorp,DC=com is the Schema Owner, but is deleted.
Warning: CN="NTDS Settings
DEL:fbeae0d9-5525-4fdd-9212-e9636c29e338",CN="KCUOBGDC01
DEL:9a02a90f-732f-41f3-beff-
f78d84df550e",CN=Servers,CN=KoyoCorp,CN=Sites,CN=Con
figuration,DC=koyocorp,DC=com is the Domain Owner, but is deleted.
......................... KCUOBGENT01 failed test
KnowsOfRoleHolders
Starting test: RidManager
No rids allocated -- please check eventlog.
......................... KCUOBGENT01 passed test RidManager
Starting test: MachineAccount
......................... KCUOBGENT01 passed test
MachineAccount
Starting test: Services
......................... KCUOBGENT01 passed test Services
Starting test: ObjectsReplicated
......................... KCUOBGENT01 passed test
ObjectsReplicated
Starting test: frssysvol
......................... KCUOBGENT01 passed test frssysvol
Starting test: kccevent
......................... KCUOBGENT01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x0000410A
Time Generated: 05/28/2008 09:23:29
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000410A
Time Generated: 05/28/2008 09:54:29
(Event String could not be retrieved)
......................... KCUOBGENT01 failed test systemlog
Running enterprise tests on : koyocorp.com
Starting test: Intersite
......................... koyocorp.com passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
......................... koyocorp.com failed test FsmoCheck
Also, I seen on other threads with similar issues, I should seize the
role, however I get a error when I try to seize the role
(LsaOpenPolicy error 0x6ba(The RPC server is unavailable.)
Everything is working, as far as users logging on, and basic group
policy. However, I cannot change any group policies such as password
complexity, lockout settings, and PDC type settings because these are
specific to the FSMO holder, and it is currently only letting me
access the policies on the mail server.
Anyone know where I can start to get on the road to fixing this
problem I have gotten myself into?
Thanks in advance,
Jonathan Johnson