PDC emulator can't be found

Microsoft Windows server 2003 enterprise
January 5, 2010 at 02:28:37
Specs: windows server 2003 r2
Hi all!
i have 9 domain controllers over two sites and one of the domain controllers is running exchange server 2007. when i transfered the PDC and RID roles to a newly installed server, and open 'AD domain and trusts' and right click on properties it shows PDC emulator can't be found.
Kindly help me with this :-)

here's the output of dcdiag:
**************************************************
Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine
ICCSERVERAD, is a DC.
* Connecting to directory service on server
ICCSERVERAD.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 9 DC(s). Testing 9 of them.
Done gathering initial info.

Doing initial required tests

Testing server: ICC\ICCSERVERDC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... ICCSERVERDC
passed test Connectivity

Testing server: HMCT\BOSERVERDC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... BOSERVERDC
passed test Connectivity

Testing server: ICC\ICCSERVERAD
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... ICCSERVERAD
passed test Connectivity

Testing server: HMCT\DIGITALFS
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DIGITALFS passed
test Connectivity

Testing server: HMCT\DIGITALSOFT
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DIGITALSOFT passed
test Connectivity

Testing server: ICC\DIGITALDC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DIGITALDC passed
test Connectivity

Testing server: HMCT\BOSERVER
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... BOSERVER passed
test Connectivity

Testing server: HMCT\corporation-ADC1
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... corporation-ADC1
passed test Connectivity

Testing server: ICC\FLUORESCENT
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... FLUORESCENT
passed test Connectivity

Doing primary tests

Testing server: ICC\ICCSERVERDC
Starting test: Replications
* Replications Check
* Replication Latency Check

DC=ForestDnsZones,DC=domain,DC=local
Latency information for 34 entries in
the vector were ignored.
34 were retired Invocations. 0
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).

DC=DomainDnsZones,DC=domain,DC=local
Latency information for 15 entries in
the vector were ignored.
15 were retired Invocations. 0
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).

CN=Schema,CN=Configuration,DC=domain,D
C=local
Latency information for 37 entries in
the vector were ignored.
37 were retired Invocations. 0
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).

CN=Configuration,DC=domain,DC=local
Latency information for 37 entries in
the vector were ignored.
37 were retired Invocations. 0
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).
DC=domain,DC=local
Latency information for 19 entries in
the vector were ignored.
19 were retired Invocations. 0
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).
DC=branch,DC=domain,DC=local
Latency information for 12 entries in
the vector were ignored.
7 were retired Invocations. 5 were
either: read-only replicas and are not verifiably
latent, or dc's no longer replicating this nc. 0
had no latency information (Win2K DC).
DC=fs,DC=domain,DC=local
Latency information for 17 entries in
the vector were ignored.
11 were retired Invocations. 6
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).
......................... ICCSERVERDC
passed test Replications
Starting test: Topology
* Configuration Topology Integrity Check
[Topology Integrity
Check,ICCSERVERDC] Intra-site topology
generation is disabled in this site.
* Analyzing the connection topology for
DC=ForestDnsZones,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
DC=DomainDnsZones,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
CN=Schema,CN=Configuration,DC=domain,D
C=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
CN=Configuration,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
DC=branch,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
DC=fs,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
......................... ICCSERVERDC
passed test Topology
Starting test: CutoffServers
* Configuration Topology Aliveness
Check
* Analyzing the alive system replication
topology for
DC=ForestDnsZones,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for
DC=DomainDnsZones,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for
CN=Schema,CN=Configuration,DC=domain,D
C=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for
CN=Configuration,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for DC=branch,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for DC=fs,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
......................... ICCSERVERDC
passed test CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all
NC's on DC ICCSERVERDC.
* Security Permissions Check for

DC=ForestDnsZones,DC=domain,DC=local
(NDNC,Version 2)
* Security Permissions Check for

DC=DomainDnsZones,DC=domain,DC=local
(NDNC,Version 2)
* Security Permissions Check for

CN=Schema,CN=Configuration,DC=domain,D
C=local
(Schema,Version 2)
* Security Permissions Check for

CN=Configuration,DC=domain,DC=local
(Configuration,Version 2)
* Security Permissions Check for
DC=domain,DC=local
(Domain,Version 2)
* Security Permissions Check for
DC=branch,DC=domain,DC=local
(Domain,Version 2)
* Security Permissions Check for
DC=fs,DC=domain,DC=local
(Domain,Version 2)
......................... ICCSERVERDC
passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share
\\ICCSERVERDC\netlogon
Verified share \\ICCSERVERDC\sysvol
......................... ICCSERVERDC
passed test NetLogons
Starting test: Advertising
The DC ICCSERVERDC is advertising
itself as a DC and having a DS.
The DC ICCSERVERDC is advertising
as an LDAP server
The DC ICCSERVERDC is advertising
as having a writeable directory
The DC ICCSERVERDC is advertising
as a Key Distribution Center
The DC ICCSERVERDC is advertising
as a time server
The DS ICCSERVERDC is advertising
as a GC.
......................... ICCSERVERDC
passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=ICCSERVERDC,CN=Servers,CN
=ICC,CN=Sites,CN=Configuration,DC=domain,
DC=local
Role Domain Owner = CN=NTDS
Settings,CN=ICCSERVERDC,CN=Servers,CN
=ICC,CN=Sites,CN=Configuration,DC=domain,
DC=local
Role PDC Owner = CN=NTDS
Settings,CN=FLUORESCENT,CN=Servers,CN
=ICC,CN=Sites,CN=Configuration,DC=domain,
DC=local
Role Rid Owner = CN=NTDS
Settings,CN=FLUORESCENT,CN=Servers,CN
=ICC,CN=Sites,CN=Configuration,DC=domain,
DC=local
Role Infrastructure Update Owner =
CN=NTDS
Settings,CN=DIGITALDC,CN=Servers,CN=ICC
,CN=Sites,CN=Configuration,DC=domain,DC=l
ocal
......................... ICCSERVERDC
passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is
13603 to 1073741823
* Fluorescent.domain.local is the RID
Master
* DsBind with RID Master was
successful
* rIDAllocationPool is 10103 to 10602
* rIDPreviousAllocationPool is 10103 to
10602
* rIDNextRID: 10223
......................... ICCSERVERDC
passed test RidManager
Starting test: MachineAccount
Checking machine account for DC
ICCSERVERDC on DC ICCSERVERDC.
* SPN found
:LDAP/ICCSERVERDC.domain.local/domain.l
ocal
* SPN found
:LDAP/ICCSERVERDC.domain.local
* SPN found :LDAP/ICCSERVERDC
* SPN found
:LDAP/ICCSERVERDC.domain.local/domain
* SPN found :LDAP/45e5fba5-39a3-
4d47-a33e-
7930e4c7a9ca._msdcs.domain.local
* SPN found :E3514235-4B06-11D1-
AB04-00C04FC2DCD2/45e5fba5-39a3-4d47-
a33e-7930e4c7a9ca/domain.local
* SPN found
:HOST/ICCSERVERDC.domain.local/domain.l
ocal
* SPN found
:HOST/ICCSERVERDC.domain.local
* SPN found :HOST/ICCSERVERDC
* SPN found
:HOST/ICCSERVERDC.domain.local/domain
* SPN found
:GC/ICCSERVERDC.domain.local/domain.loc
al
......................... ICCSERVERDC
passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... ICCSERVERDC
passed test Services
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure
Channels test
because /testdomain: was not entered
......................... ICCSERVERDC
passed test OutboundSecureChannels
Starting test: ObjectsReplicated
ICCSERVERDC is in domain
DC=domain,DC=local
Checking for
CN=ICCSERVERDC,OU=Domain
Controllers,DC=domain,DC=local in domain
DC=domain,DC=local on 9 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=ICCSERVERDC,CN=Servers,CN
=ICC,CN=Sites,CN=Configuration,DC=domain,
DC=local in domain
CN=Configuration,DC=domain,DC=local on 9
servers
Object is up-to-date on all servers.
......................... ICCSERVERDC
passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL
ready test
File Replication Service's SYSVOL is
ready
......................... ICCSERVERDC
passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log
test
......................... ICCSERVERDC
passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory
Service Event log in the last 15 minutes.
......................... ICCSERVERDC
passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in
the last 60 minutes.
......................... ICCSERVERDC
passed test systemlog
Starting test: VerifyReplicas
......................... ICCSERVERDC
passed test VerifyReplicas
Starting test: VerifyReferences
The system object reference
(serverReference)

CN=ICCSERVERDC,OU=Domain
Controllers,DC=domain,DC=local and

backlink on


CN=ICCSERVERDC,CN=Servers,CN=ICC,CN
=Sites,CN=Configuration,DC=domain,DC=loca
l

are correct.
The system object reference
(frsComputerReferenceBL)

CN=ICCSERVERDC,CN=Domain
System Volume (SYSVOL share),CN=File
Replication
Service,CN=System,DC=domain,DC=local

and backlink on

CN=ICCSERVERDC,OU=Domain
Controllers,DC=domain,DC=local are

correct.
The system object reference
(serverReferenceBL)

CN=ICCSERVERDC,CN=Domain
System Volume (SYSVOL share),CN=File
Replication
Service,CN=System,DC=domain,DC=local

and backlink on

CN=NTDS
Settings,CN=ICCSERVERDC,CN=Servers,CN
=ICC,CN=Sites,CN=Configuration,DC=domain,
DC=local

are correct.
......................... ICCSERVERDC
passed test VerifyReferences
Starting test: VerifyEnterpriseReferences
......................... ICCSERVERDC
passed test VerifyEnterpriseReferences
Starting test: CheckSecurityError
* Dr Auth: Beginning security errors
check!
Found KDC ICCSERVERDC for domain
domain.local in site ICC
Checking machine account for DC
ICCSERVERDC on DC ICCSERVERDC.
* SPN found
:LDAP/ICCSERVERDC.domain.local/domain.l
ocal
* SPN found
:LDAP/ICCSERVERDC.domain.local
* SPN found :LDAP/ICCSERVERDC
* SPN found
:LDAP/ICCSERVERDC.domain.local/domain
* SPN found :LDAP/45e5fba5-39a3-
4d47-a33e-
7930e4c7a9ca._msdcs.domain.local
* SPN found :E3514235-4B06-11D1-
AB04-00C04FC2DCD2/45e5fba5-39a3-4d47-
a33e-7930e4c7a9ca/domain.local
* SPN found
:HOST/ICCSERVERDC.domain.local/domain.l
ocal
* SPN found
:HOST/ICCSERVERDC.domain.local
* SPN found :HOST/ICCSERVERDC
* SPN found
:HOST/ICCSERVERDC.domain.local/domain
* SPN found
:GC/ICCSERVERDC.domain.local/domain.loc
al
[ICCSERVERDC] No security related
replication errors were found on this DC! To
target the connection to a specific source DC
use /ReplSource:<DC>.
......................... ICCSERVERDC
passed test CheckSecurityError

Testing server: HMCT\BOSERVERDC
Starting test: Replications
* Replications Check
* Replication Latency Check

DC=ForestDnsZones,DC=domain,DC=local
Latency information for 34 entries in
the vector were ignored.
34 were retired Invocations. 0
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).

CN=Schema,CN=Configuration,DC=domain,D
C=local
Latency information for 37 entries in
the vector were ignored.
37 were retired Invocations. 0
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).

CN=Configuration,DC=domain,DC=local
Latency information for 37 entries in
the vector were ignored.
37 were retired Invocations. 0
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).
DC=domain,DC=local
Latency information for 23 entries in
the vector were ignored.
19 were retired Invocations. 4
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).

DC=DomainDnsZones,DC=branch,DC=domain
,DC=local
Latency information for 5 entries in
the vector were ignored.
5 were retired Invocations. 0 were
either: read-only replicas and are not verifiably
latent, or dc's no longer replicating this nc. 0
had no latency information (Win2K DC).
DC=branch,DC=domain,DC=local
Latency information for 5 entries in
the vector were ignored.
5 were retired Invocations. 0 were
either: read-only replicas and are not verifiably
latent, or dc's no longer replicating this nc. 0
had no latency information (Win2K DC).
DC=fs,DC=domain,DC=local
Latency information for 15 entries in
the vector were ignored.
10 were retired Invocations. 5
were either: read-only replicas and are not
verifiably latent, or dc's no longer replicating
this nc. 0 had no latency information (Win2K
DC).
......................... BOSERVERDC
passed test Replications
Starting test: Topology
* Configuration Topology Integrity Check
[Topology Integrity
Check,BOSERVERDC] Intra-site topology
generation is disabled in this site.
* Analyzing the connection topology for
DC=DomainDnsZones,DC=branch,DC=domain
,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
DC=ForestDnsZones,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
DC=branch,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
CN=Schema,CN=Configuration,DC=domain,D
C=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
CN=Configuration,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
DC=fs,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the connection topology for
DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
......................... BOSERVERDC
passed test Topology
Starting test: CutoffServers
* Configuration Topology Aliveness
Check
* Analyzing the alive system replication
topology for
DC=DomainDnsZones,DC=branch,DC=domain
,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for
DC=ForestDnsZones,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for DC=branch,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for
CN=Schema,CN=Configuration,DC=domain,D
C=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for
CN=Configuration,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for DC=fs,DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
* Analyzing the alive system replication
topology for DC=domain,DC=local.
* Performing upstream (of target)
analysis.
* Performing downstream (of target)
analysis.
......................... BOSERVERDC
passed test CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all
NC's on DC BOSERVERDC.
* Security Permissions Check for

DC=DomainDnsZones,DC=branch,DC=domain
,DC=local
(NDNC,Version 2)
* Security Permissions Check for

DC=ForestDnsZones,DC=domain,DC=local
(NDNC,Version 2)
* Security Permissions Check for
DC=branch,DC=domain,DC=local
(Domain,Version 2)
* Security Permissions Check for

CN=Schema,CN=Configuration,DC=domain,D
C=local
(Schema,Version 2)
* Security Permissions Check for

CN=Configuration,DC=domain,DC=local
(Configuration,Version 2)
* Security Permissions Check for
DC=fs,DC=domain,DC=local
(Domain,Version 2)
* Security Permissions Check for
DC=domain,DC=local
(Domain,Version 2)
......................... BOSERVERDC
passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share
\\BOSERVERDC\netlogon
Verified share \\BOSERVERDC\sysvol
......................... BOSERVERDC
passed test NetLogons
Starting test: Advertising
The DC BOSERVERDC is advertising
itself as a DC and having a DS.
The DC BOSERVERDC is advertising
as an LDAP server
The DC BOSERVERDC is advertising
as having a writeable directory
The DC BOSERVERDC is advertising
as a Key Distribution Center
The DC BOSERVERDC is advertising
as a time server
The DS BOSERVERDC is advertising
as a GC.
......................... BOSERVERDC
passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=ICCSERVERDC,CN=Servers,CN
=ICC,CN=Sites,CN=Configuration,DC=domain,
DC=local
Role Domain Owner = CN=NTDS
Settings,CN=ICCSERVERDC,CN=Servers,CN
=ICC,CN=Sites,CN=Configuration,DC=domain,
DC=local
Role PDC Owner = CN=NTDS
Settings,CN=BOSERVERDC,CN=Servers,CN
=HMCT,CN=Sites,CN=Configuration,DC=dom
ain,DC=local
Role Rid Owner = CN=NTDS
Settings,CN=BOSERVERDC,CN=Servers,CN
=HMCT,CN=Sites,CN=Configuration,DC=dom
ain,DC=local
Role Infrastructure Update Owner =
CN=NTDS
Settings,CN=BOSERVERDC,CN=Servers,CN
=HMCT,CN=Sites,CN=Configuration,DC=dom
ain,DC=local
......................... BOSERVERDC
passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is
6107 to 1073741823
* boserverdc.branch.domain.local is the
RID Master
* DsBind with RID Master was
successful
* rIDAllocationPool is 4107 to 4606
* rIDPreviousAllocationPool is 4107 to
4606
* rIDNextRID: 4221
......................... BOSERVERDC
passed test RidManager
Starting test: MachineAccount
Checking machine account for DC
BOSERVERDC on DC BOSERVERDC.
* SPN found
:LDAP/boserverdc.branch.domain.local/branch
.domain.local
* SPN found
:LDAP/boserverdc.branch.domain.local
* SPN found :LDAP/BOSERVERDC
* SPN found
:LDAP/boserverdc.branch.domain.local/BRAN
CH
* SPN found :LDAP/9a2347c6-a238-
4d7c-8c4b-
78e4fd646b62._msdcs.domain.local
* SPN found :E3514235-4B06-11D1-
AB04-00C04FC2DCD2/9a2347c6-a238-4d7c-
8c4b-78e4fd646b62/branch.domain.local
* SPN found
:HOST/boserverdc.branch.domain.local/branch
.domain.local
* SPN found
:HOST/boserverdc.branch.domain.local
* SPN found :HOST/BOSERVERDC
* SPN found
:HOST/boserverdc.branch.domain.local/BRAN
CH
* SPN found
:GC/boserverdc.branch.domain.local/domain.lo
cal
......................... BOSERVERDC
passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... BOSERVERDC
passed test Services
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure
Channels test
because /testdomain: was not entered
......................... BOSERVERDC
passed test OutboundSecureChannels
Starting test: ObjectsReplicated
BOSERVERDC is in domain
DC=branch,DC=domain,DC=local
Checking for
CN=BOSERVERDC,OU=Domain
Controllers,DC=branch,DC=domain,DC=local
in domain DC=branch,DC=domain,DC=local
on 9 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=BOSERVERDC,CN=Servers,CN
=HMCT,CN=Sites,CN=Configuration,DC=dom
ain,DC=local in domain
CN=Configuration,DC=domain,DC=local on 9
servers
Object is up-to-date on all servers.
......................... BOSERVERDC
passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL
ready test
File Replication Service's SYSVOL is
ready
......................... BOSERVERDC
passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log
test
There are warning or error events within
the last 24 hours after the

SYSVOL has been shared. Failing
SYSVOL replication problems may cause

Group Policy problems.
An Error Event occured. EventID:
0xC0003500
Time Generated: 01/05/2010
07:06:17
(Event String could not be retrieved)
......................... BOSERVERDC failed
test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory
Service Event log in the last 15 minutes.
......................... BOSERVERDC
passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in
the last 60 minutes.
......................... BOSERVERDC
passed test systemlog
Starting test: VerifyReplicas


See More: PDC emulator cant be found

Report •

#1
January 5, 2010 at 03:43:26
What domain functional level are you at?

From the report above it seems as if you also have an older windows 2000 server on the network, is that true?


Report •

#2
January 5, 2010 at 03:45:27
domain and forest is in win2003 functional level

Report •

#3
January 5, 2010 at 09:05:35
Microsoft specifically does not recommend Exchange be on a DC.

ICCSERVERDC
Role PDC Owner = CN=NTDS

BOSERVERDC
Role PDC Owner = CN=NTDS

Did you wait for the transfer to complete? Which of these is the "new" server? Are you doing this across a wan link?

You have two PDC emulators.


Report •

Related Solutions

#4
January 5, 2010 at 19:51:53
my new server is Fluorescent. and our site ICC & HTMT are
connected by Hi-speed wan link.
BOserverDC is in child domain.
the stucture is like a parent domain.local and two child domains.

Report •

#5
January 5, 2010 at 20:23:55
BOSERVERDC is in child domain.

Report •

#6
January 5, 2010 at 21:29:16
Looks like you are missing a pdc emulator if you have one primary and two child domains.

Dcdiag is too long to go thru.

if I hear what you are saying Domain.local is parent
ICC and HMCT are child domains.

But name spaces say that branch.domain.local is a subdomain of domain.local. I am not seeing a second child domain like branch2.domain.local in the log.

child domains take the form of child.domain.local and child1.doman.local

Fluorescent is in domain.local
"Fluorescent.domain.local"
Boserverdc is in branch as a subdomain of domain.local
"boserverdc.branch.domain.local"
["" means copied and pasted from dcdiag log]

You write
"when i transfered the PDC and RID roles to a newly installed server"
"my new server is Fluorescent"
"BOserverDC is in child domain"

I have to assume you tried to move the pdc role from boserverdc to fluorescent. But they appear to be in different namespace levels in the forest.

If you only have one root and one child domain then you have the right amount of pdc emulators.


Report •

#7
January 5, 2010 at 21:47:27
Well let me explain the structure of my setup:-

parent domain "domain.local" is at site "ICC" with four DC's i.e.

"DIGITALDC", "ICCSERVERDC", "ICCSERVERAD", "FLUORESCENT",

and at site "HTMT" child domain "BRANCH.domain.local" i have three DC's

"BOSERVERDC", "BOSERVER", "CORPORATION-ADC1",

and at the same site "HTMT" i have another child domain "FS.domain.local" having two DC's i.e.

"DIGITALFS", "DIGITALSOFT".

initially PDC and RID roles were on "ICCSERVERDC" then i shifted them to newly installed "FLUORESCENT" in parent domain.


Report •

#8
January 6, 2010 at 11:18:56
can't find FS.DOMAIN.LOCAL in the dcdiag output anywhere.

"Testing server: HMCT\DIGITALFS"
"Testing server: HMCT\DIGITALSOFT"
don't show digitalsoft and digitalfs servers in FS.DOMAIN.LOCAL context but site HMCT. I don't see any dns info for them in the dcdiag output.

Might want to run DCDIAG /TEST:DNS /V /E to get dns output related to all dcs.

according to the dcdiag ICCSERVERDC is still the pdc emulator.
boserverdc.branch.domain.local is the pdc for the child domain branch.

just looking at dns I only see a root domain DOMAIN.LOCAL and a child domain BRANCH.DOMAIN.LOCAL. Where is this FS child domain?

You have three sites
ICC, HMCT, and HTMT
but only a root and child domain. You have the correct amount of pdc emulators. PDC emulators does not appear to be a issue.


Report •

Ask Question