P
Phantom
Hi,
I just put up a fourth domain controller (a GC server and
w/ADC-integrated DNS)in my single domain, single forest, single site
environment. In Active Directory Sites and Services, default-first-site,
only the two domain controllers configured as DNS servers can see it in
the NTDS Settings branch. It can display those two, but not the domain
controller with the FMSO role of PDC emulator (also RID and
Infrastructure master). The PDC emulator can't display it in its NTDS
branch either.
Running repadmin.exe /showrepl servername /verbose /all /intersite on
the new domain controller shows
"Last attempt @ 2009-08-16 01:50:56 was successful"
all around, with the exception that the new domain controller just
doesn't register the PDC emulator (act on it with repladmin) when
running this command.
I see event id 1586 warnings in the new domain controller's directory
service event log. Here is the text:
"The Windows NT 4.0 or earlier replication checkpoint with the PDC
emulator master was unsuccessful.
A full synchronization of the security accounts manager (SAM)
database to domain controllers running Windows NT 4.0 and earlier
might take place if the PDC emulator master role is transferred to
the local domain controller before the next successful checkpoint.
The checkpoint process will be tried again in four hours."
I'm baffled by all of this. Do I have a problem? I've never seen this
before with any of my domain controllers not seeing each other in NTDS
Settings.
Thanks,
- Brian
I just put up a fourth domain controller (a GC server and
w/ADC-integrated DNS)in my single domain, single forest, single site
environment. In Active Directory Sites and Services, default-first-site,
only the two domain controllers configured as DNS servers can see it in
the NTDS Settings branch. It can display those two, but not the domain
controller with the FMSO role of PDC emulator (also RID and
Infrastructure master). The PDC emulator can't display it in its NTDS
branch either.
Running repadmin.exe /showrepl servername /verbose /all /intersite on
the new domain controller shows
"Last attempt @ 2009-08-16 01:50:56 was successful"
all around, with the exception that the new domain controller just
doesn't register the PDC emulator (act on it with repladmin) when
running this command.
I see event id 1586 warnings in the new domain controller's directory
service event log. Here is the text:
"The Windows NT 4.0 or earlier replication checkpoint with the PDC
emulator master was unsuccessful.
A full synchronization of the security accounts manager (SAM)
database to domain controllers running Windows NT 4.0 and earlier
might take place if the PDC emulator master role is transferred to
the local domain controller before the next successful checkpoint.
The checkpoint process will be tried again in four hours."
I'm baffled by all of this. Do I have a problem? I've never seen this
before with any of my domain controllers not seeing each other in NTDS
Settings.
Thanks,
- Brian