DFS Replication failed to contact Domain Controller.....

I have seen this error since the inception of this stand alone AD PDC instance of Windows server 2012 R2 Essentials. I understand that Essentials does not support other Domain Controllers ; Member servers ; or trust between Domains of any kind. I also
understand that DSF Replication is a service that replicates files between other servers and other domain servers that Essentials dose not want to talk to.
So my question is why am I seeing this DFSR error 1202  in my event log, if Essentials does not support communication to other servers and domain servers? Maybe a better question is why does Essentials even try to implement this
service? Do I even need to try to resolve this issue or should I just disable it and move on? 
Contents of Error:
Log Name:      DFS Replication
Source:        DFSR
Date:          2/6/2014 1:57:57 PM
Event ID:      1202
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Hxxx2.xxxxxxxxxxxxx.local
Description:
The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused
by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DFSR" />
    <EventID Qualifiers="49152">1202</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-06T19:57:57.000000000Z" />
    <EventRecordID>194</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>Hxxx2.Hxxxxxxxxxxxxx.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Data>60</Data>
    <Data>160</Data>
    <Data>One or more arguments are not correct.</Data>
  </EventData>
</Event>

Hi, 
Did you mean that you did not configure a DFS server in the new DC but you get the DFSR error 1202 in your event log? Then the issue is not related to the existing SBS domain. 
Please try to turn off the Windows Firewall to check if it causes the issue. You could also refer to the articles below to troubleshoot the issue:
Newly Promoted Win2K8 DC is not advertising as Domain Controller.
http://blogs.technet.com/b/niraj_kumar/archive/2009/04/23/newly-promoted-win2k8-dc-is-not-advertising-as-domain-controller.aspx
Restrictions for Unauthenticated RPC Clients: The group policy that punches your domain in the face
https://blogs.technet.com/b/askds/archive/2011/04/08/restrictions-for-unauthenticated-rpc-clients-the-group-policy-that-punches-your-domain-in-the-face.aspx
Regards, 
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • DFSR failed to contact domain controller

    Im having an odd problem with DFSR group we created to replicate web content between two of our web servers.
    In event viewer we have this event 1202 for DFSR.
    "The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can
    be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
    Additional Information:
    Error: 160 (One or more arguments are not correct.)"
    In the DFSR logs I see this.
    20140303 12:18:27.874 1404 CFAD 8300 Config::AdConfig::GetLocalComputerNameWithDns Computer's fully-qualified DNS name: DFSRSERVER.domain.tld
    20140303 12:18:27.920 1404 CFAD 311 Config::AdConnection::Connect Binding to dcAddr:\\1.1.1.1 dcDnsName:\\MYDC.domain.tld
    20140303 12:18:27.936 1404 CFAD 143 Config::AdConnection::BindToAd Trying to connect. hostName:MYDC.domain.tld
    20140303 12:18:28.467 1404 CFAD 162 Config::AdConnection::BindToAd Bound. hostName:MYDC.domain.tld
    20140303 12:18:28.467 1404 CFAD 199 Config::AdConnection::BindToDc Try to bind. hostName:\\MYDC.domain.tld domainName:<null>
    20140303 12:18:28.514 1404 CFAD 3373 [ERROR] Config::DsSession::Bind Failed to DsBind(). dc:\\MYDC.domain.tld domainName:<null> Error:5
    20140303 12:18:28.514 1404 CFAD 215 Config::AdConnection::BindToDc (Ignored) Failed to bind. hostName:\\MYDC.domain.tld domainName:<null> Error:[Error:5(0x5) Config::DsSession::Bind ad.cpp:3380 1404 W Access is denied.]
    20140303 12:18:28.514 1404 CFAD 199 Config::AdConnection::BindToDc Try to bind. hostName:\\1.1.1.1 domainName:<null>
    20140303 12:18:28.514 1404 CFAD 3373 [ERROR] Config::DsSession::Bind Failed to DsBind(). dc:\\1.1.1.1 domainName:<null> Error:87
    20140303 12:18:28.514 1404 CFAD 215 Config::AdConnection::BindToDc (Ignored) Failed to bind. hostName:\\1.1.1.1 domainName:<null> Error:[Error:87(0x57) Config::DsSession::Bind ad.cpp:3380 1404 W The parameter is incorrect.]
    20140303 12:18:28.514 1404 SCFS 150 [WARN] ServiceConfig::DsPollIsDue Failed to enable lightweight polling. Error:
    + [Error:160(0xa0) Config::AdConfig::ConnectToLocalDc ad.cpp:8365 1404 W One or more arguments are not correct.]
    + [Error:160(0xa0) Config::AdConfig::Connect ad.cpp:8113 1404 W One or more arguments are not correct.]
    + [Error:160(0xa0) Config::AdConnection::Connect adconnection.cpp:377 1404 W One or more arguments are not correct.]
    + [Error:160(0xa0) Config::AdConnection::BindToDc adconnection.cpp:226 1404 W One or more arguments are not correct.]
    20140303 12:18:28.514 1404 CREG 1419 Config::RegReader::IsSysVolCommitFlagSet key: System\CurrentControlSet\Services\DFSR\Parameters\SysVols\Demoting SysVols valueName:'SysVol Information is Committed' result:0
    20140303 12:18:28.514 1404 W2CH 266 ConfigurationHelper::PollAdConfigNow Trying to connect to AD
    20140303 12:18:28.514 1404 CFAD 311 Config::AdConnection::Connect Binding to dcAddr:\\1.1.1.1 dcDnsName:\\MYDC.domain.tld
    20140303 12:18:28.514 1404 CFAD 143 Config::AdConnection::BindToAd Trying to connect. hostName:MYDC.domain.tld
    20140303 12:18:28.514 1404 CFAD 162 Config::AdConnection::BindToAd Bound. hostName:MYDC.domain.tld
    20140303 12:18:28.514 1404 CFAD 199 Config::AdConnection::BindToDc Try to bind. hostName:\\MYDC.domain.tld domainName:<null>
    20140303 12:18:28.514 1404 CFAD 3373 [ERROR] Config::DsSession::Bind Failed to DsBind(). dc:\\MYDC.domain.tld domainName:<null> Error:5
    20140303 12:18:28.514 1404 CFAD 215 Config::AdConnection::BindToDc (Ignored) Failed to bind. hostName:\\MYDC.domain.tld domainName:<null> Error:[Error:5(0x5) Config::DsSession::Bind ad.cpp:3380 1404 W Access is denied.]
    20140303 12:18:28.514 1404 CFAD 199 Config::AdConnection::BindToDc Try to bind. hostName:\\1.1.1.1 domainName:<null>
    20140303 12:18:28.514 1404 CFAD 3373 [ERROR] Config::DsSession::Bind Failed to DsBind(). dc:\\1.1.1.1 domainName:<null> Error:87
    20140303 12:18:28.514 1404 CFAD 215 Config::AdConnection::BindToDc (Ignored) Failed to bind. hostName:\\1.1.1.1 domainName:<null> Error:[Error:87(0x57) Config::DsSession::Bind ad.cpp:3380 1404 W The parameter is incorrect.]
    20140303 12:18:28.514 1404 EVNT 1194 EventLog::Report Logging eventId:1202 parameterCount:4
    20140303 12:18:28.514 1404 EVNT 1214 EventLog::Report eventId:1202 parameter1:
    20140303 12:18:28.514 1404 EVNT 1214 EventLog::Report eventId:1202 parameter2:60
    20140303 12:18:28.514 1404 EVNT 1214 EventLog::Report eventId:1202 parameter3:160
    20140303 12:18:28.514 1404 EVNT 1214 EventLog::Report eventId:1202 parameter4:One or more arguments are not correct.
    20140303 12:18:28.530 1404 W2CH 318 [ERROR] ConfigurationHelper::PollAdConfigNow (Ignored) Failed to connect to AD. Error:
    + [Error:160(0xa0) Config::AdConfig::ConnectToLocalDc ad.cpp:8365 1404 W One or more arguments are not correct.]
    + [Error:160(0xa0) Config::AdConfig::Connect ad.cpp:8113 1404 W One or more arguments are not correct.]
    + [Error:160(0xa0) Config::AdConnection::Connect adconnection.cpp:377 1404 W One or more arguments are not correct.]
    + [Error:160(0xa0) Config::AdConnection::BindToDc adconnection.cpp:226 1404 W One or more arguments are not correct.]
    When I run "dfsrdiag pollad":
    [ERROR] PollDsNow method executed unsuccessfully. ReturnValue: 12 (0xc)
    [ERROR] Failed to execute PollAD command Err: -2147217407 (0x80041001)
    However I can run "dfsrdiag dumpadcfg" and it outputs everything fine.
    We don't have any other problems with AD.  It seems like this started after we installed KB2467173 & KB2538242.  We are going to uninstall those and see if it works.

    I can successfully run "dfsrdiag.exe dumpadcfg" and it outputs the entire config.  Why does "dfsrdiag pollad" fail then if the config can be read.
    Why did it work before I rebooted the server?  In both cases it broke after rebooting.
    PS C:\Windows\system32> dfsrdiag dumpadcfg
    LDAP Bind : mydc.domain.tld
    SitesDn : cn=sites,cn=configuration,dc=domain,dc=tld
    ServicesDn : cn=services,cn=configuration,dc=domain,dc=tld
    SystemDn : cn=system,dc=domain,dc=tld
    DefaultNcDn : dc=domain,dc=tld
    ComputersDn : cn=computers,dc=domain,dc=tld
    DomainCtlDn : ou=domain controllers,dc=domain,dc=tld
    SchemaDn : CN=Schema,CN=Configuration,dc=domain,dc=tld
    COMPUTER: web1
    DN : cn=web1,ou=web,ou=virtual servers,ou=servers,dc=domain,dc=tld
    GUID : 152E849C-4D7B-4AE8-B034-83747DBC1E89
    DNS : web1.domain.tld
    Server Ref : (null)
    USN Changed : 10862129
    When Created : Friday, January 31, 2014 8:41:06 PM
    When Changed : Tuesday, March 4, 2014 2:54:36 PM
    LOCAL SETTINGS: DFSR-LOCALSETTINGS
    DN : cn=dfsr-localsettings,cn=web1,ou=web,ou=virtual servers,ou=servers,dc=domain,dc=tld
    GUID : 3FD696E7-6598-4CDB-B2AB-98F148C0D2F7
    Version : 1.0.0.0
    USN Changed : 10932017
    When Created : Thursday, March 6, 2014 2:11:12 PM
    When Changed : Thursday, March 6, 2014 2:15:25 PM
    SUBSCRIBER: FF88A312-A0EB-44CC-A614-7A3D06DCC0AB
    DN : cn=ff88a312-a0eb-44cc-a614-7a3d06dcc0ab,cn=dfsr-localsettings,cn=web1,ou=web,ou=virtual servers,ou=servers,dc=domain,dc=tld
    GUID : 1119B663-F02A-4F1F-A904-23A87CFC93C3
    Member Ref : cn=ff88a312-a0eb-44cc-a614-7a3d06dcc0ab,cn=topology,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    USN Changed : 10931931
    When Created : Thursday, March 6, 2014 2:11:12 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    SUBSCRIPTION: 6783DDE1-C795-4E8B-B07D-4EA8D7D0317F
    DN : cn=6783dde1-c795-4e8b-b07d-4ea8d7d0317f,cn=ff88a312-a0eb-44cc-a614-7a3d06dcc0ab,cn=dfsr-localsettings,cn=web1,ou=web,ou=virtual servers,ou=servers,dc=domain,dc=tld
    GUID : 3737B1F2-7E38-47E2-90E7-E57D82B145F1
    ContentSetGuid: 6783DDE1-C795-4E8B-B07D-4EA8D7D0317F
    Root Path : c:\inetpub\internetsites
    Root Size : 10240 (MB)
    Staging Path : c:\inetpub\internetsites\dfsrprivate\staging
    Staging Size : 4096 (MB)
    Conflict Path : c:\inetpub\internetsites\dfsrprivate\conflictanddeleted
    Conflict Size : 4096 (MB)
    USN Changed : 10931919
    When Created : Thursday, March 6, 2014 2:11:13 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    SUBSCRIPTION: F2F1F3A2-B36F-4170-B371-8E8043DF73F4
    DN : cn=f2f1f3a2-b36f-4170-b371-8e8043df73f4,cn=ff88a312-a0eb-44cc-a614-7a3d06dcc0ab,cn=dfsr-localsettings,cn=web1,ou=web,ou=virtual servers,ou=servers,dc=domain,dc=tld
    GUID : 57E7F8D7-1121-4334-BC81-74226ADF8969
    ContentSetGuid: F2F1F3A2-B36F-4170-B371-8E8043DF73F4
    Root Path : c:\internet_data
    Root Size : 10240 (MB)
    Staging Path : c:\internet_data\dfsrprivate\staging
    Staging Size : 4096 (MB)
    Conflict Path : c:\internet_data\dfsrprivate\conflictanddeleted
    Conflict Size : 4096 (MB)
    USN Changed : 10931921
    When Created : Thursday, March 6, 2014 2:11:13 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    SUBSCRIPTION: D0438B52-B706-4E40-B4C3-FE7A1ACA5FCF
    DN : cn=d0438b52-b706-4e40-b4c3-fe7a1aca5fcf,cn=ff88a312-a0eb-44cc-a614-7a3d06dcc0ab,cn=dfsr-localsettings,cn=web1,ou=web,ou=virtual servers,ou=servers,dc=domain,dc=tld
    GUID : F8217091-F71A-4D4A-A676-097583171A63
    ContentSetGuid: D0438B52-B706-4E40-B4C3-FE7A1ACA5FCF
    Root Path : c:\php\phpsites
    Root Size : 10240 (MB)
    Staging Path : c:\php\phpsites\dfsrprivate\staging
    Staging Size : 4096 (MB)
    Conflict Path : c:\php\phpsites\dfsrprivate\conflictanddeleted
    Conflict Size : 4096 (MB)
    USN Changed : 10931923
    When Created : Thursday, March 6, 2014 2:11:13 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    GLOBAL SETTINGS: DFSR-GLOBALSETTINGS
    DN : cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : 2E98CE5E-5CC7-4322-B5EA-2B6B340C689F
    USN Changed : 12525
    When Created : Saturday, October 22, 2011 1:56:38 AM
    When Changed : Saturday, October 22, 2011 1:56:38 AM
    REPLICATION GROUP: WEB CONTENT
    DN : cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : 9C94A417-6F6C-4F6C-BBFA-B8F52854C4DF
    Type : 0 (UNKNOWN REPLICATION GROUP TYPE)
    Options : 0x1 [Local Time Schedule]
    USN Changed : 10931906
    When Created : Thursday, March 6, 2014 2:11:12 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    CONTENT: CONTENT
    DN : cn=content,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : 6714C533-E631-4E71-930D-E4934FB7BD7E
    USN Changed : 10931908
    When Created : Thursday, March 6, 2014 2:11:12 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    CONTENT SET: INTERNET_DATA
    DN : cn=internet_data,cn=content,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : F2F1F3A2-B36F-4170-B371-8E8043DF73F4
    File Filter : ~*, *.bak, *.tmp
    Compression Excl : (null)
    Dir Filter : (null)
    USN Changed : 10931916
    When Created : Thursday, March 6, 2014 2:11:13 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    CONTENT SET: INTERNETSITES
    DN : cn=internetsites,cn=content,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : 6783DDE1-C795-4E8B-B07D-4EA8D7D0317F
    File Filter : ~*, *.bak, *.tmp
    Compression Excl : (null)
    Dir Filter : (null)
    USN Changed : 10931915
    When Created : Thursday, March 6, 2014 2:11:13 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    CONTENT SET: PHPSITES
    DN : cn=phpsites,cn=content,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : D0438B52-B706-4E40-B4C3-FE7A1ACA5FCF
    File Filter : ~*, *.bak, *.tmp
    Compression Excl : (null)
    Dir Filter : (null)
    USN Changed : 10931917
    When Created : Thursday, March 6, 2014 2:11:13 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    TOPOLOGY: TOPOLOGY
    DN : cn=topology,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : 16053002-7B99-4DA7-BFE5-2A6418040640
    USN Changed : 10931907
    When Created : Thursday, March 6, 2014 2:11:12 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    MEMBER: FF88A312-A0EB-44CC-A614-7A3D06DCC0AB
    DN : cn=ff88a312-a0eb-44cc-a614-7a3d06dcc0ab,cn=topology,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : 75A99277-C401-409F-A32D-6D8EE18E5D0C
    Server Ref : (null)
    Computer Ref : cn=web1,ou=web,ou=virtual servers,ou=servers,dc=domain,dc=tld
    Keywords : (null)
    Computer DNS : web1.domain.tld
    USN Changed : 10931933
    When Created : Thursday, March 6, 2014 2:11:12 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    CXTION: 9ECE3EB7-FE97-4A1B-8DE3-47A77B2C625B
    DN : cn=9ece3eb7-fe97-4a1b-8de3-47a77b2c625b,cn=ff88a312-a0eb-44cc-a614-7a3d06dcc0ab,cn=topology,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : 1D26B348-3875-4BD1-9473-E72506AFA222
    Inbound : true
    Partner DN : cn=46f913db-8509-4581-a66d-d37e4ea3ef29,cn=topology,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    Enabled : TRUE
    Options : 0x1 [Local Time Schedule]
    USN Changed : 10931924
    When Created : Thursday, March 6, 2014 2:11:13 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    CXTION: 2BFA8BE2-0444-4AAF-8293-A5486CF8D7A3
    DN : cn=2bfa8be2-0444-4aaf-8293-a5486cf8d7a3,cn=46f913db-8509-4581-a66d-d37e4ea3ef29,cn=topology,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : A7203451-D95F-44D5-AC04-13056DCE5A89
    Inbound : false
    Partner DN : cn=46f913db-8509-4581-a66d-d37e4ea3ef29,cn=topology,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    Enabled : TRUE
    Options : 0x1 [Local Time Schedule]
    USN Changed : 10931925
    When Created : Thursday, March 6, 2014 2:11:13 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    MEMBER: 46F913DB-8509-4581-A66D-D37E4EA3EF29
    DN : cn=46f913db-8509-4581-a66d-d37e4ea3ef29,cn=topology,cn=web content,cn=dfsr-globalsettings,cn=system,dc=domain,dc=tld
    GUID : 1BA26D07-45F5-44A0-8450-9274AFD99B1C
    Server Ref : (null)
    Computer Ref : cn=fccu01web,ou=web,ou=virtual servers,ou=servers,dc=domain,dc=tld
    Keywords : (null)
    Computer DNS : fccu01web.domain.tld
    USN Changed : 10931927
    When Created : Thursday, March 6, 2014 2:11:12 PM
    When Changed : Thursday, March 6, 2014 2:11:27 PM
    Operation Succeeded

  • DFSR Replication Event ID 1202 The DFS Replication service failed to contact domain controller Additional Information: Error: 160 (One or more arguments are not correct.)

    Hi,
    hummmm...
    The client had 1 Server with AD and All Apps, IIS, Terminal Servers (30 device Cal), File Server, SQL2008R2 on it
    Task: Install new AD server promote it to DC,  bring in 2nd server, Replicate the File Server (DFSR) on these 2 servers, and demote it to standard server. 
    1) Old AD with name "Server" with OS-2008R2 SP1 and is a DC.
    2) Brought in a new server "PrimaryAD", Installed 2008R2, done DC Promo, and added it as Additional Domain controller
    3) Transferred roles from old server "Server" to "PrimaryAD"
    4) Brought in a new File Server replicating server "Backup-Server"
    5) Copied all the data from Server to Backup-server as DFS initial file sync with robocopy
    6) here the problem started, after the copy finished, next morning the "Server" server crashed.....
    7) thank god the data was backed up on Backup-server. but we didnt get the time to Demote the server "Server" and remove AD from it.
    8) Since AD was replicated so "PrimaryAD" was are DC, brought 2nd Server "SecondaryDC" as additional domain controller.
    9) we cleaned up the metadata and used ASIEDIT to clean the remaining stuff.
    10) the "Server" server was formatted and renamed as "Primary-Server" and OS2008R2 SP1 was installed with rest of required apps
    11) so now the PrimaryAD the DC, SecondaryAD the Additional Domain controller, Primary-Server the mail server and File server, the Backup-server, the replicated server.
    Now configured DFS Replication from Primary-Server to Backup-server and receive following Event ID 1202
    If i Configure DFS Replication as follows
    PrimaryAD <<>> SecondaryAD -= Works... no errors...
    PrimaryAD <<>> Backup-Server = Creates but Dosent works Event ID 5012, error The DFS Replication service failed to communicate with partner BACKUP-SERVER, Additional Information: Error: 9026 (The connection is invalid)
    PrimaryAD <<>> Primary-Server = Dosent creates replication job just hangs,
    on primaryad continious Eveni ID 10009, DCOM was unable to communicate with the computer "SERVER" using any of the configured protocols
    ......something on PrimaryAD is still trying to connect to old corrupt AD server "Server"
    No errors with AD replication, SYSVOL & Netlogon shares also working fine and accessible.
    DFS Diagnose report says
    DNS name: backup-server.mydomain.com
    Domain name: mydomain.COM
    Reference domain controller: --           (HERE there is NO DOMAIN CONTROLLER mentioned) 
    IP address: 192.168.1.248,192.168.1.251,::1
    Site: Default-First-Site-Name
    Forgot to mention, gave full rights with ADSIEDIT to DFSR-LocalSettings  for all server to Administrator and read permissions to "Authenticated Users"
    DFSRDIAG POLLAD throws following error
    c:\Dfsrdiag pollad /verbose
    [INFO] Computer Name: BACKUP-SERVER
    [INFO] Computer DNS: Backup-Server.mydomain.COM
    [INFO] Domain Name: mydomain
    [INFO] Domain DNS: mydomain.COM
    [INFO] Site Name: Default-First-Site-Name
    [INFO] Connected to WMI services on computer: Backup-Server.mydomain.COM
    [INFO] Invoke PollDsNow() method on Backup-Server.mydomain.COM
    [ERROR] PollDsNow method executed unsuccessfully. ReturnValue: 12 (0xc)
    [ERROR] Failed to execute PollAD command Err: -2147217407 (0x80041001)
    Can anyone point me to any direction which can lead to resolution of this ERROR and make DFS_R work..
    Thanks
    bikram

    Hi,
    It seems that DCPROMO did its work without complaints, still the DFSR references remained in AD. You could refer to the article below to clean up the DFS Replication object.
    How to remove data in Active Directory after an unsuccessful domain controller demotion
    http://support.microsoft.com/kb/216498
    In additional, please refer to the following thread to troubleshoot the issue:
    DFS is not working anymore.
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/953be9ef-e9e3-4885-a5c4-47fc475ba562/dfs-is-not-working-anymore?forum=winserverfiles
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SharePoint 2013 - Word Automation Services - Conversion fails ErrorCode 10 - Domain Controller on same (development) server as SharePoint

    I have code attached below, running inside SharePoint (in a page), used to convert .docx document to .pdf using Word Automation Services.
    SPFile inputWordFile = ##CODE THAT RETRIEVE THE SPFile ##
    using (Stream inputWordStream = inputWordFile.OpenBinaryStream())
       using (MemoryStream outputPdfStream = new MemoryStream())
    SyncConverter sc = new SyncConverter(wordAutomationServiceName);
    sc.UserToken = web.CurrentUser.UserToken;
    sc.Settings.UpdateFields = true;
    sc.Settings.OutputFormat = SaveFormat.PDF;
    ConversionItemInfo info = sc.Convert(inputWordStream, outputPdfStream);
    if (info.Succeeded)
    What happens is that the conversion fails. errorCode is 10.
    What I came to, is that this is related to the Domain Controller being installed on the same machine.
    I have examinated and excluded all several other possible issues (memory resources, etc.).
    What I had undestood as far, is that the problem is that "the
    converter is executed in the context of a very unprivileged local account, and there are no local accounts on DCs"
    Is this a KNOWN ISSUE?
    Is there a workaround for development enviroment having DC+SQL+VisualStudio+SharePoint on the same machine?

    Hi,
    It is recommended to try the code demo in this documentation below in a Console Application to see if it can work in your environment:
    http://msdn.microsoft.com/en-us/library/office/ff181518(v=office.14).aspx
    If it still can’t work, you can restart the Word Automation Services in SharePoint Central Administration in case it is a service issue.
    Feel free to reply with the test result if the issue still exists.
    Thanks
    Patrick Liang
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Patrick Liang
    TechNet Community Support

  • DFS Replication Failing

    What kind of storage is E: running on?  Have you checked for physical disk failure?

    I have a 2012 R2 server where DFS replication is spotty.I have this in the event log:The DFS Replication service has detected an unexpected shutdown on volume E:. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. The service has automatically initiated a recovery process. The service will rebuild the database if it determines it cannot reliably recover. No user action is required. Additional Information: Volume: E: GUID: 07051EDF-B0EF-4095-A003-117D3D70B220But it does not finish the process, or at least I do not see anything about it completed in the event log. Its been 24 hours and a reboot.If I try to run manually
    wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="07051EDF-B0EF-4095-A003-117D3D70B220"call ResumeReplicationThe comand...
    This topic first appeared in the Spiceworks Community

  • Only contact Domain Controller when on a particular network

    As per subject, I have a laptop joined to a domain and logging on is slow when outside the network. Obviously it is trying to contact the domain contoller but fails. Can we set it to immediately use the last saved password when not within the network?

    That might be the reason.
    but as you could logon it, the cached info is worked here. the logon is slow might caused by the mapped drives. and disable the always wait ..policy should fit this, which is not recommended when mapped drive is in use.
    Run Xperf to take a check with the slow logon process.
    http://blogs.technet.com/b/yongrhee/archive/2013/10/15/tool-windows-performance-toolkit-xperf-wprui-and-wpr-updated-version-as-of-aug-2013.aspx
    Rgds

  • Server 2012 Domain Controller Logging event 2004, with error "crc check"...

    Pretty new domain, and domain controller, running server 2012 as a Hyper-V VM.
    Getting this error when it reboots.  I have done a chkdsk, thinking maybe the vhdx file is corrupt in some way.  Have also checked the system log for events talking about file corruption.  Nothing.
    The disk in question has 10+ GB free, so disk space is not an issue.  I ran dcdiag /q /a & it told me that DFSR has logged events in the last 24 hours, but nothing else.  AD seems to think everything is cool.
    Not sure what to look at next...  Thanks for any pointers/help.
    The DFS Replication service stopped replication on volume C:. This failure can occur because the disk is full, the disk is failing, or a quota limit has been reached. This can also occur if the DFS Replication service encountered errors while attempting to
    stage files for a replicated folder on this volume. 
    Additional Information: 
    Error: 23 (Data error (cyclic redundancy check).) 
    Volume: 0F55C346-589F-11E2-93EB-806E6F6E6963

    I have a series of the following Events logged, and then the 2nd event.  The 2nd event is being logged every 8 hours.
    Log Name:      DFS Replication
    Source:        DFSR
    Date:          2/15/2013 7:36:49 AM
    Event ID:      2212
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      MyDC.Domain.lan
    Description:
    The DFS Replication service has detected an unexpected shutdown on volume C:. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. The service has automatically initiated a recovery process.
    The service will rebuild the database if it determines it cannot reliably recover. No user action is required.
    Additional Information:
    Volume: C:
    GUID: 0F55C346-589F-11E2-93EB-806E6F6E6963
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="DFSR" />
        <EventID Qualifiers="32768">2212</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-02-14T23:36:49.000000000Z" />
        <EventRecordID>196</EventRecordID>
        <Channel>DFS Replication</Channel>
        <Computer>MyDC.domain.lan</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0F55C346-589F-11E2-93EB-806E6F6E6963</Data>
        <Data>C:</Data>
      </EventData>
    </Event>
    Log Name:      DFS Replication
    Source:        DFSR
    Date:          2/15/2013 7:36:49 AM
    Event ID:      2004
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MyDC.Domain.lan
    Description:
    The DFS Replication service stopped replication on volume C:. This failure can occur because the disk is full, the disk is failing, or a quota limit has been reached. This can also occur if the DFS Replication service encountered errors while attempting to
    stage files for a replicated folder on this volume.
    Additional Information:
    Error: 23 (Data error (cyclic redundancy check).)
    Volume: 0F55C346-589F-11E2-93EB-806E6F6E6963
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="DFSR" />
        <EventID Qualifiers="49152">2004</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-02-14T23:36:49.000000000Z" />
        <EventRecordID>197</EventRecordID>
        <Channel>DFS Replication</Channel>
        <Computer>MyDC.Domain.lan</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0F55C346-589F-11E2-93EB-806E6F6E6963</Data>
        <Data>C:</Data>
        <Data>23</Data>
        <Data>Data error (cyclic redundancy check).</Data>
      </EventData>
    </Event>

  • Findout previous deleted domain controller computer name frome SID

    Hi
    I recently suspicious that some one in my company join new additional domain controller  to my primary DC and after replication and get the domain controller partitions ,he disjoint the new additional dc .
    I got the his event in my dns log :
    The DNS server was unable to create a resource record for  d630907c-e2f4-41cf-a2c6-adc087f25f46._msdcs.metro.com. in zone metro.com. The Active Directory definition of this resource record is corrupt or contains an invalid DNS name. The event
    data contains the error.
    I want to translate the DNS alias sid :d630907c-e2f4-41cf-a2c6-adc087f25f46
    to computer name in order to find who did this?
    is there a way to find out previous DC computer name after hey disconnected or DC computer account deleted?
    I wonder to know ho did this?
    Regards

    The guid you're referring to corresponds to the NTDS Settings object for the "lost" DC. You can do this in Powershell to get the DirectoryEntry for that guid:
    [adsi]"LDAP://<GUID=d630907c-e2f4-41cf-a2c6-adc087f25f46>"
    However, if the object has been deleted, you need to perform another query (in Powershell as well):
    $guid = ([guid]"d630907c-e2f4-41cf-a2c6-adc087f25f46")
    Get-ADObject -SearchBase "DC=metro,DC=com" -IncludeDeletedObjects -Filter { objectGuid -eq $guid }
    Note that by default you need to be a member of Domain Admins or Administrators to be able to query AD for deleted objects.
    Best Regards,
    Carl S
    All code is provided as-is with no guarantees. Always try it out in a test environment before applying it in a production environment.

  • Rebuilding Domain controller & Transport Routes after system refresh

    I have refreshed Dev from Prdn, now my domain controller only shows single system
    I have documentation but, it is confusing to me how to have QAS and Prdn join the domain controller again and show the domain as a three tier system
    When I log into QAS and Prdn I still see the old 3 tier system including the domain and the other systems.
    Please advise
    maria
    Edited by: Maria Graziano on Mar 27, 2008 3:53 PM

    You don't perform backup of domain controller.
    You only designate in STMS one of servers as "Backup Domain Controller"
    when Primary  controller fails than "Backup domain Controller" takes his role and becomes a primary.
    So action to refresh domain controller is:
    1. Designate one of servers as backup domain controller
    2. Backup transport directory if it is on refreshed server (just in case)
    3. Switch backup controller to become primary
    4. Refresh primary system
    5. Join refreshed system to domain
    6. Switch back primary function to refreshed server
    Regards,
    Wojtek

  • ISSUE: "This domain controller must register a DNS SRV resource record, which is required for replication to function correctly"

    so we currently have three domain controllers set up, two of them on 2012r2 and one of them on 2008r2. prior to any of these domain controllers being added to the domain there was only one, running on 2003r2. the 2003r2 server was up and running when the
    first 2012r2 was added and that's when running 'dcdiag /e /c /v' would yield an issue with "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local" in the DNS portion of the diagnostics, specifically:
    TEST: Records registration (RReg)
    Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
    Error:
    Missing SRV record at DNS server 192.168.22.4:
    _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
    after adding the second 2012r2 to the domain, this issue is still there... adding the 2008r2 server to the domain and running BPA it gives the following:
    Title:
    This domain controller must register a DNS SRV resource record, which is required for replication to function correctly
    Severity:
    Error
    Date:
    7/3/2014 11:24:48 AM
    Category:
    Configuration
    Issue:
    The "DcByGuid" DNS service (SRV) resource record that advertises this server as an available domain controller in the domain and ensures correct replication is not registered. All domain controllers (but not RODCs) in the domain must register this record.
    Impact:
    Other member computers and domain controllers in the domain or forest will not be able to locate this domain controller. This domain controller will not be able to provide a full suite of services.
    Resolution:
    Ensure that "DcByGuid" is not configured in the "DnsAvoidRegisteredRecords" list, either through Group Policy or through the registry. Restart the Netlogon service. Verify that the DNS service (SRV) resource record "_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local", pointing to the local domain controller "CM-DC4-NY01.cmedia.local", is registered in DNS.
    More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=126968
    I've tried scanning and then re-scanning every single entry in DNS Manager and do not see any reference to this specific GUID mentioned, nor do I see any other domain controllers referenced that should not be in there. The two 2012r2 and the 2008r2 domain
    controllers are the only ones listed in DNS Manager... the 2003r2 mentioned earlier failed and was removed.

    Just to chime in, I noticed that you said you have one 2008 R2 DC, and two 2012 DCs.
    I also noticed in the ipconfig /all that all DCs are pointint to themselves for DNS. We usually like to see them point to a partner, then itslelf as the second entry, w hether loopback or by its own IP.
    Based on that, what I suggest to level the playing field by choosing the WIndows 2008 R2 DC as the first DNS on all DCs and only administer DNS using that DC. The reason I chose that is because of the least common denominator is what we rather use so we
    don't invoke any new features in the newer 2012 DNS console that 2008 R2 may not understand.  After that's done, on each DC run (and you can use a PowerShell window to run this):
    Rename the system32\config\netlogon.dns and netlogon.dnb files by suffixing ".old" to the file.
    ipconfig /registerdns
    net stop netlogon
    net start netlogon
    Then re-run the dcdiag /e /c /v.
    Post your results, please.
    Ace Fekay
    MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.
    I thought the DNS entries were supposed to be the other way around? point to themselves first and a partner as secondary? regardless, as requested, I've changed it to what you've prescribed where they point to the 2008r2 server as the primary with themselves
    as the secondary. I've also followed the steps to what seems like refreshing the DNS? on each of the DCs. Here's the output from dcdiag /e /c /v
    Directory Server Diagnosis
    Performing initial setup:
    Trying to find home server...
    * Verifying that the local machine CM-DC1-NY01, is a Directory Server.
    Home Server = CM-DC1-NY01
    * Connecting to directory service on server CM-DC1-NY01.
    * Identified AD Forest.
    Collecting AD specific global data
    * Collecting site info.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory
    =ntDSSiteSettings),.......
    The previous call succeeded
    Iterating through the sites
    Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia
    ,DC=local
    Getting ISTG and options for the site
    * Identifying all servers.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=cmedia,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=nt
    DSDsa),.......
    The previous call succeeded....
    The previous call succeeded
    Iterating through the list of servers
    Getting information for the server CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites
    ,CN=Configuration,DC=cmedia,DC=local
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    * Identifying all NC cross-refs.
    * Found 3 DC(s). Testing 3 of them.
    Done gathering initial info.
    Doing initial required tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC1-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC3-NY01 passed test Connectivity
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    * Active Directory RPC Services Check
    ......................... CM-DC4-NY01 passed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site-Name\CM-DC1-NY01
    Starting test: Advertising
    The DC CM-DC1-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC1-NY01 is advertising as an LDAP server
    The DC CM-DC1-NY01 is advertising as having a writeable directory
    The DC CM-DC1-NY01 is advertising as a Key Distribution Center
    The DC CM-DC1-NY01 is advertising as a time server
    The DS CM-DC1-NY01 is advertising as a GC.
    ......................... CM-DC1-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    [CM-DC1-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC1-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC1-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC1-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC1-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC1-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC1-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC1-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local
    * SPN found :LDAP/CM-DC1-NY01
    * SPN found :LDAP/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :LDAP/a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a29d12f1-2869-44bf-8e43-adf7ddf33865/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC1-NY01.cmedia.local
    * SPN found :HOST/CM-DC1-NY01
    * SPN found :HOST/CM-DC1-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC1-NY01.cmedia.local/cmedia.local
    ......................... CM-DC1-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC1-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC1-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC1-NY01\netlogon
    Verified share \\CM-DC1-NY01\sysvol
    ......................... CM-DC1-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC1-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC1-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC1-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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).
    ......................... CM-DC1-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 4609 to 5108
    * rIDPreviousAllocationPool is 4609 to 5108
    * rIDNextRID: 4629
    ......................... CM-DC1-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC1-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    A warning event occurred. EventID: 0x0000002F
    Time Generated: 07/08/2014 13:19:14
    Event String:
    Time Provider NtpClient: No valid response has been received from manually configured peer 0.ca.pool.ntp.org
    after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a n
    ew peer with this DNS name. The error was: The peer is unreachable.
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC1-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC1-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC1-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC1-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC1-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC1-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC1-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC3-NY01
    Starting test: Advertising
    The DC CM-DC3-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC3-NY01 is advertising as an LDAP server
    The DC CM-DC3-NY01 is advertising as having a writeable directory
    The DC CM-DC3-NY01 is advertising as a Key Distribution Center
    The DC CM-DC3-NY01 is advertising as a time server
    The DS CM-DC3-NY01 is advertising as a GC.
    ......................... CM-DC3-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC3-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC3-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC3-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC3-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC3-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC3-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC3-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC3-NY01 on DC CM-DC3-NY01.
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local
    * SPN found :LDAP/CM-DC3-NY01
    * SPN found :LDAP/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :LDAP/5e9d1971-39ca-484c-922d-411c2364c96e._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/5e9d1971-39ca-484c-922d-411c2364c96e/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC3-NY01.cmedia.local
    * SPN found :HOST/CM-DC3-NY01
    * SPN found :HOST/CM-DC3-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC3-NY01.cmedia.local/cmedia.local
    ......................... CM-DC3-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC3-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC3-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC3-NY01\netlogon
    Verified share \\CM-DC3-NY01\sysvol
    ......................... CM-DC3-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC3-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC3-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC3-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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).
    ......................... CM-DC3-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15109 to 15608
    * rIDPreviousAllocationPool is 15109 to 15608
    * rIDNextRID: 15110
    ......................... CM-DC3-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC3-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC3-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC3-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC3-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC3-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC3-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC3-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC3-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC3-NY01 passed test VerifyReplicas
    Testing server: Default-First-Site-Name\CM-DC4-NY01
    Starting test: Advertising
    The DC CM-DC4-NY01 is advertising itself as a DC and having a DS.
    The DC CM-DC4-NY01 is advertising as an LDAP server
    The DC CM-DC4-NY01 is advertising as having a writeable directory
    The DC CM-DC4-NY01 is advertising as a Key Distribution Center
    The DC CM-DC4-NY01 is advertising as a time server
    The DS CM-DC4-NY01 is advertising as a GC.
    ......................... CM-DC4-NY01 passed test Advertising
    Starting test: CheckSecurityError
    * Dr Auth: Beginning security errors check!
    Found KDC CM-DC1-NY01 for domain cmedia.local in site Default-First-Site-Name
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC1-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 2 servers
    Object is up-to-date on all servers.
    [CM-DC4-NY01] No security related replication errors were found on this DC! To target the connection to a
    specific source DC use /ReplSource:<DC>.
    ......................... CM-DC4-NY01 passed test CheckSecurityError
    Starting test: CutoffServers
    * Configuration Topology Aliveness Check
    * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the alive system replication topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    ......................... CM-DC4-NY01 passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    Skip the test because the server is running FRS.
    ......................... CM-DC4-NY01 passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test SysVolCheck
    Starting test: FrsSysVol
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... CM-DC4-NY01 passed test FrsSysVol
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... CM-DC4-NY01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role Domain Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
    guration,DC=cmedia,DC=local
    Role PDC Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Rid Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configur
    ation,DC=cmedia,DC=local
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=CM-DC1-NY01,CN=Servers,CN=Default-First-Site-Name,CN
    =Sites,CN=Configuration,DC=cmedia,DC=local
    ......................... CM-DC4-NY01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC CM-DC4-NY01 on DC CM-DC4-NY01.
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local
    * SPN found :LDAP/CM-DC4-NY01
    * SPN found :LDAP/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :LDAP/37830012-1f10-43c9-a0ff-2a0e8a912187._msdcs.cmedia.local
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/37830012-1f10-43c9-a0ff-2a0e8a912187/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia.local
    * SPN found :HOST/CM-DC4-NY01.cmedia.local
    * SPN found :HOST/CM-DC4-NY01
    * SPN found :HOST/CM-DC4-NY01.cmedia.local/cmedia
    * SPN found :GC/CM-DC4-NY01.cmedia.local/cmedia.local
    ......................... CM-DC4-NY01 passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC CM-DC4-NY01.
    The forest is not ready for RODC. Will skip checking ERODC ACEs.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=cmedia,DC=local
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=cmedia,DC=local
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=cmedia,DC=local
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=cmedia,DC=local
    (Domain,Version 3)
    ......................... CM-DC4-NY01 passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\CM-DC4-NY01\netlogon
    Verified share \\CM-DC4-NY01\sysvol
    ......................... CM-DC4-NY01 passed test NetLogons
    Starting test: ObjectsReplicated
    CM-DC4-NY01 is in domain DC=cmedia,DC=local
    Checking for CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local in domain DC=cmedia,DC=local o
    n 3 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
    n,DC=cmedia,DC=local in domain CN=Configuration,DC=cmedia,DC=local on 3 servers
    Object is up-to-date on all servers.
    ......................... CM-DC4-NY01 passed test ObjectsReplicated
    Starting test: OutboundSecureChannels
    * The Outbound Secure Channels test
    ** Did not run Outbound Secure Channels test because /testdomain: was not entered
    ......................... CM-DC4-NY01 passed test OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    DC=ForestDnsZones,DC=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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=cmedia,DC=local
    Latency information for 4 entries in the vector were ignored.
    4 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).
    ......................... CM-DC4-NY01 passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 16109 to 1073741823
    * CM-DC1-NY01.cmedia.local is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 15609 to 16108
    * rIDPreviousAllocationPool is 15609 to 16108
    * rIDNextRID: 15609
    ......................... CM-DC4-NY01 passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: NtFrs
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... CM-DC4-NY01 passed test Services
    Starting test: SystemLog
    * The System Event log test
    Found no errors in "System" Event log in the last 60 minutes.
    ......................... CM-DC4-NY01 passed test SystemLog
    Starting test: Topology
    * Configuration Topology Integrity Check
    * Analyzing the connection topology for DC=ForestDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=DomainDnsZones,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for CN=Configuration,DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    * Analyzing the connection topology for DC=cmedia,DC=local.
    * Performing upstream (of target) analysis.
    * Performing downstream (of target) analysis.
    ......................... CM-DC4-NY01 passed test Topology
    Starting test: VerifyEnterpriseReferences
    ......................... CM-DC4-NY01 passed test VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference) CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local
    and backlink on
    CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=cmedia,DC=local are
    correct.
    The system object reference (serverReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on
    CN=NTDS Settings,CN=CM-DC4-NY01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=chiefmed
    ia,DC=local
    are correct.
    The system object reference (frsComputerReferenceBL)
    CN=CM-DC4-NY01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=cmedia,D
    C=local
    and backlink on CN=CM-DC4-NY01,OU=Domain Controllers,DC=cmedia,DC=local are correct.
    ......................... CM-DC4-NY01 passed test VerifyReferences
    Starting test: VerifyReplicas
    ......................... CM-DC4-NY01 passed test VerifyReplicas

  • The processing of Group Policy failed because of lack of network connectivity to a domain controller

    We are setting up a new AD environment  with one AD/DC running DNS services,  and a secondary DNS server configured with secondary zone. The problem is that none of the machines in the the domain are getting GPO.
    When I run a gpupdate /force from a machine, I get the following output:
    "Updating Policy...
    User Policy update has completed successfully.
    Computer policy could not be updated successfully. The following errors were enc
    ountered:
    The processing of Group Policy failed because of lack of network connectivity to
     a domain controller. This may be a transient condition. A success message would
     be generated once the machine gets connected to the domain controller and Group
     Policy has succesfully processed. If you do not see a success message for sever
    al hours, then contact your administrator.
    To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
    rom the command line to access information about Group Policy results."
    While the system event log outputs the following:
    "The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy
    has succesfully processed. If you do not see a success message for several hours, then contact your administrator." 
    All the machines that were joined to the domain are able to resolve in forward and reverse lookups, ping the DC and ping each other so  I dont understand how the error can be resolved.
    Here are few things I have tried:
    1. I came across this KB which checked ok for me: http://support.microsoft.com/kb/241515
    2. Made a copy of the default GPO, applied to a OU with one machine, and made sure to remove any GPO links from above
    3. Enabled the following  two local Group policies on a test member:
    GP slow link detection
    Startup policy processing wait time
    4. Modified firewall to allow everything on both member and DC
    5. Verified DSN logs, SRV records, access to sysvol ( added authenticated users to sysvol)
    I have yet to figure out the reason for this issue. Has anyone seen anything like this before?

    1. I checked the NIC, it only has one IP. and I followed your article. I set the primary DNS to its own IP and the secondary DNS to the loopback ip
    2. This is a new DC and DNS server. I dont have old records yet. I also check the DNS event logs. No errors
    3. I made sure the member server is pointing only to the only DC/DNS server
    4. Here is the output from the dcdiag....  everything passed except, the Netlogons part. I'm not sure what means or how to fix it yet:
          Starting test: NetLogons
             * Warning BUILTIN\Administrators did not have the "Access this
             computer
             "*   from network" right.
             [hostname] An net use or LsaPolicy operation failed with error
             1, Incorrect function..
             ......................... hostname failed test NetLogons
    Complete output:
    > hostname
    Server:  hostname.domain.local
    Address:  X.X.X.95
    > ^C
    C:\Windows\system32>
    C:\Windows\system32>nslookup
    > set type=all
    >
    >
    >
    > _ldap._tcp.dc._msdcs.domainname
    _ldap._tcp.dc._msdcs.domain.local SRV service location:
              priority       = 0
              weight         = 100
              port           = 389
              svr hostname   = hostname.domain.local
    hostname.domain.local      internet address = X.X.X.95
    > ^C
    C:\Windows\system32>cd ..
    C:\Windows>cd SYSVOL
    C:\Windows\SYSVOL>cd sysvol
    C:\Windows\SYSVOL\sysvol>dir
     Volume in drive C has no label.
     Volume Serial Number is F624-CDB2
     Directory of C:\Windows\SYSVOL\sysvol
    10/29/2014  08:25 PM    <DIR>          .
    10/29/2014  08:25 PM    <DIR>          ..
    10/29/2014  08:25 PM    <JUNCTION>     domain.local [C:\Windows\SYSVOL\domain]
                   0 File(s)              0 bytes
                   3 Dir(s)  63,971,037,184 bytes free
    C:\Windows\SYSVOL\sysvol>dcdiag
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = hostname
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\hostname
          Starting test: Connectivity
             ......................... hostname passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\hostname
          Starting test: Advertising
             ......................... hostname passed test Advertising
          Starting test: FrsEvent
             ......................... hostname passed test FrsEvent
          Starting test: DFSREvent
             ......................... hostname passed test DFSREvent
          Starting test: SysVolCheck
             ......................... hostname passed test SysVolCheck
          Starting test: KccEvent
             ......................... hostname passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... hostname passed test
             KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... hostname passed test MachineAccount
          Starting test: NCSecDesc
             ......................... hostname passed test NCSecDesc
          Starting test: NetLogons
             * Warning BUILTIN\Administrators did not have the "Access this
             computer
             "*   from network" right.
             [hostname] An net use or LsaPolicy operation failed with error
             1, Incorrect function..
             ......................... hostname failed test NetLogons
          Starting test: ObjectsReplicated
             ......................... hostname passed test
             ObjectsReplicated
          Starting test: Replications
             ......................... hostname passed test Replications
          Starting test: RidManager
             ......................... hostname passed test RidManager
          Starting test: Services
             ......................... hostname passed test Services
          Starting test: SystemLog
             A warning event occurred.  EventID: 0x000003F6
                Time Generated: 03/04/2015   18:23:06
                Event String:
                Name resolution for the name ctldl.windowsupdate.com timed out after
     none of the configured DNS servers responded.
             ......................... hostname passed test SystemLog
          Starting test: VerifyReferences
             ......................... hostname passed test VerifyReferences
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : emcdsm
          Starting test: CheckSDRefDom
             ......................... emcdsm passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... emcdsm passed test CrossRefValidation
       Running enterprise tests on : domain.local
          Starting test: LocatorCheck
             ......................... domain.local passed test LocatorCheck
          Starting test: Intersite
             ......................... domain.local passed test Intersite
    C:\Windows\SYSVOL\sysvol>

  • Error determining whether the target server is already a domain controller: Failed to open the runspace pool

    Hi there , i already have some others DC running w2k12 R2 on the env, but when i was promoting another new DC running w2k12 R2 on the middle of the AD sync , the server encounter an error and rebooted it self ; after the server came back online , it keep
    saying that a configuration is required for AD Domain Services , like the step when you are about to promote the server , but when you try to promote it , the error "Error determining whether the target server is already a domain controller: Failed
    to open the runspace pool. The server manager winrm plug-in might be corrupted or missing."

    Hi,
    Thanks for your post.
    Please waitting for the replication is finished and rerun the domain prep command  to check the result.
    Regards.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • DFS Replication doesn't work. Windows server 2012. Failed to communicate with partner. Error 5012.

    Hi! I really confused with this error. I created replication group within two servers - AD domain controller and File server. I just want to migrate some files from AD domain controller to FS. But synchronization doesn't work. I get the error
    - DFS Replication cannot replicate with partner <server name> for replication group <domain>\<name space>\<share>. The partner did not recognize the connection or the replication group configuration. The DFS Replication service used
    partner DNS name MyDCName, IP address <the server ip>, and WINS address <server name> but failed with error ID: 9026 (The connection is invalid). Event ID: 5012
    It seems my DC doesn’t accept connection from FS. I checked network, permissions and other settings which are mentioned in this article. 
    http://social.technet.microsoft.com/Forums/en-US/953be9ef-e9e3-4885-a5c4-47fc475ba562/dfs-is-not-working-anymore?Thread%3A953be9ef-e9e3-4885-a5c4-47fc475ba562=Microsoft.Forums.Data.Models.Discussion&ThreadViewModel%3A953be9ef-e9e3-4885-a5c4-47fc475ba562=Microsoft.Forums.CachedViewModels.ThreadPageViewModel&forum=winserverfiles 
    But nothing happens. Replication still doesn’t work. Please, help me with this. May be there is a check list to solve this problem? Thank you. 

    Check this ; https://social.technet.microsoft.com/wiki/contents/articles/1205.dfsr-event-5012-dfs-replication.aspx
    Arnav Sharma | Facebook |
    Twitter Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members
    reading the thread.

  • Active Directory domain controller could not be contacted

    Hello
    Help please.
    I am trying to add a new server (2008) to domain 'bridgelimited.local' - only one DC (2003) doing everything at the moment. The plan is to add the new server, then move everything over from the old machine, then retire/upgrade the old machine and use as a backup.
    I am currently trying to dcpromo on the new machine but I get the following error:
    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller for domain bridgelimited.local:
    The error was: "DNS name does not exist."
    (error code 0x0000232B RCODE_NAME_ERROR)
    The query was for the SRV record for _ldap._tcp.dc._msdcs.bridgelimited.local
    Common causes of this error include the following:
    - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
    212.50.160.100
    196.168.16.2
    - One or more of the following zones do not include delegation to its child zone:
    bridgelimited.local
    local
    . (the root zone)
    For information about correcting this problem, click Help.
    192.168.16.2 is IP address for the DC.
    Any help would be grately appreciated.
    Kind Regards
    Richard

    Managed to get the DCDIAG
    Here goes (I know my harddisk is failing - that's why I am desperate to get everything shifted to the new server).
    Domain Controller Diagnosis
    Performing initial setup:
       * Verifying that the local machine bridgeserver, is a DC.
       * Connecting to directory service on server bridgeserver.
       * Collecting site info.
       * Identifying all servers.
       * Identifying all NC cross-refs.
       * Found 1 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\BRIDGESERVER
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             * Active Directory RPC Services Check
             ......................... BRIDGESERVER passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\BRIDGESERVER
          Starting test: Replications
             * Replications Check
             * Replication Latency Check
                DC=ForestDnsZones,DC=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 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). 
             * Replication Site Latency Check
             ......................... BRIDGESERVER passed test Replications
          Starting test: Topology
             * Configuration Topology Integrity Check
             * Analyzing the connection topology for DC=ForestDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for DC=DomainDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             ......................... BRIDGESERVER passed test Topology
          Starting test: CutoffServers
             * Configuration Topology Aliveness Check
             * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             ......................... BRIDGESERVER passed test CutoffServers
          Starting test: NCSecDesc
             * Security Permissions Check for
               DC=ForestDnsZones,DC=BridgeLimited,DC=local
                (NDNC,Version 2)
             * Security Permissions Check for
               DC=DomainDnsZones,DC=BridgeLimited,DC=local
                (NDNC,Version 2)
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local
                (Schema,Version 2)
             * Security Permissions Check for
               CN=Configuration,DC=BridgeLimited,DC=local
                (Configuration,Version 2)
             * Security Permissions Check for
               DC=BridgeLimited,DC=local
                (Domain,Version 2)
             ......................... BRIDGESERVER passed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             ......................... BRIDGESERVER passed test NetLogons
          Starting test: Advertising
             The DC BRIDGESERVER is advertising itself as a DC and having a DS.
             The DC BRIDGESERVER is advertising as an LDAP server
             The DC BRIDGESERVER is advertising as having a writeable directory
             The DC BRIDGESERVER is advertising as a Key Distribution Center
             The DC BRIDGESERVER is advertising as a time server
             The DS BRIDGESERVER is advertising as a GC.
             ......................... BRIDGESERVER passed test Advertising
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role Domain Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role PDC Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role Rid Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             ......................... BRIDGESERVER passed test KnowsOfRoleHolders
          Starting test: RidManager
             * Available RID Pool for the Domain is 2609 to 1073741823
             * bridgeserver.BridgeLimited.local is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 2109 to 2608
             * rIDPreviousAllocationPool is 2109 to 2608
             * rIDNextRID: 2121
             ......................... BRIDGESERVER passed test RidManager
          Starting test: MachineAccount
             * SPN found :LDAP/bridgeserver.BridgeLimited.local/BridgeLimited.local
             * SPN found :LDAP/bridgeserver.BridgeLimited.local
             * SPN found :LDAP/BRIDGESERVER
             * SPN found :LDAP/bridgeserver.BridgeLimited.local/BRIDGELIMITED
             * SPN found :LDAP/96d36b0b-a148-4c2f-b3d3-8c2ac83fcaf9._msdcs.BridgeLimited.local
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/96d36b0b-a148-4c2f-b3d3-8c2ac83fcaf9/BridgeLimited.local
             * SPN found :HOST/bridgeserver.BridgeLimited.local/BridgeLimited.local
             * SPN found :HOST/bridgeserver.BridgeLimited.local
             * SPN found :HOST/BRIDGESERVER
             * SPN found :HOST/bridgeserver.BridgeLimited.local/BRIDGELIMITED
             * SPN found :GC/bridgeserver.BridgeLimited.local/BridgeLimited.local
             ......................... BRIDGESERVER passed test MachineAccount
          Starting test: Services
             * Checking Service: Dnscache
             * Checking Service: NtFrs
             * Checking Service: IsmServ
                IsmServ Service is stopped on [BRIDGESERVER]
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: RpcSs
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... BRIDGESERVER failed test Services
          Starting test: OutboundSecureChannels
             * The Outbound Secure Channels test
             ** Did not run Outbound Secure Channels test
             because /testdomain: was not entered
             ......................... BRIDGESERVER passed test OutboundSecureChannels
          Starting test: ObjectsReplicated
             BRIDGESERVER is in domain DC=BridgeLimited,DC=local
             Checking for CN=BRIDGESERVER,OU=Domain Controllers,DC=BridgeLimited,DC=local in domain DC=BridgeLimited,DC=local on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local in domain CN=Configuration,DC=BridgeLimited,DC=local on 1 servers
                Object is up-to-date on all servers.
             ......................... BRIDGESERVER passed test ObjectsReplicated
          Starting test: frssysvol
             * The File Replication Service SYSVOL ready test
             File Replication Service's SYSVOL is ready
             ......................... BRIDGESERVER passed test frssysvol
          Starting test: frsevent
             * The File Replication Service Event log test
             ......................... BRIDGESERVER 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.
             ......................... BRIDGESERVER passed test kccevent
          Starting test: systemlog
             * The System Event log test
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:47:27
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:47:41
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:47:55
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:09
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:23
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:38
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:52
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:49:06
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:49:20
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:49:54
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:50:08
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:50:22
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:51:33
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:51:53
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:07
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:21
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:35
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:49
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:03
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:17
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:31
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:45
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:12:23
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:12:37
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:12:51
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:05
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:19
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:33
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:47
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:14:01
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:14:15
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:15:24
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:15:38
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:15:53
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:07
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:21
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:35
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:49
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:17:03
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:17:17
                Event String: The driver for device \Device\Scsi\hpt3xx1
    detected a port timeout due to prolonged
    inactivity. All associated busses were reset in
    an effort to clear the condition.
             ......................... BRIDGESERVER failed test systemlog
          Starting test: VerifyReplicas
             ......................... BRIDGESERVER passed test VerifyReplicas
          Starting test: VerifyReferences
             The system object reference (serverReference)
             CN=BRIDGESERVER,OU=Domain Controllers,DC=BridgeLimited,DC=local and
             backlink on
             CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             are correct.
             The system object reference (frsComputerReferenceBL)
             CN=BRIDGESERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=BridgeLimited,DC=local
             and backlink on
             CN=BRIDGESERVER,OU=Domain Controllers,DC=BridgeLimited,DC=local are
             correct.
             The system object reference (serverReferenceBL)
             CN=BRIDGESERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=BridgeLimited,DC=local
             and backlink on
             CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             are correct.
             ......................... BRIDGESERVER passed test VerifyReferences
          Starting test: VerifyEnterpriseReferences
             ......................... BRIDGESERVER passed test VerifyEnterpriseReferences
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
       Running partition tests on : BridgeLimited
          Starting test: CrossRefValidation
             ......................... BridgeLimited passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... BridgeLimited passed test CheckSDRefDom
       Running enterprise tests on : BridgeLimited.local
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope
             provided by the command line arguments provided.
             ......................... BridgeLimited.local passed test Intersite
          Starting test: FsmoCheck
             GC Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             PDC Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             Time Server Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             Preferred Time Server Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             KDC Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             ......................... BridgeLimited.local passed test FsmoCheck
    The only thing I can see (other then the HDD) is the
    IsmServ Service is stopped on [BRIDGESERVER]
    Hope you can help. Pretty please.
    Kind Regards
    Richard

  • The box indicating that this domain controller is the last controller for the domain is unchecked. However, no other Active Directory domain controllers for that domain can be contacted

    I have 2 domain controllers running 2003 server, server1 and server2. I ran dcpromo on server1 and removed AD and removed him from the domain and disconnected from network. I then added a 2012 server
    with the same name and IP address server1 with no problem. Replication from sites and services work fine on both controllers.
    The new 2012 server1 is GC. I transferred all FSMO roles to server1. Again no problem and replicating using sites and services. AD on server1 is populated correctly.
    Now what I had intended on doing was a dcpromo to remove server2 from the domain so I can then add another 2012 server. That is when I get the: "The box indicating that this domain controller is the last controller for the domain
     is unchecked. However, no other Active Directory domain controllers for that domain can be contacted.
    I have DNS installed on both servers and both look good with replicating there. Strange thing is when on the 2012 server within DNS if I right click and connect to another DNS server I can add server2 just fine but from server2 adding server1 it tells me it
    is not available.
    Help please!

    Hi,
    As there is server 2012 DC (SERVER1) DC is operational in a domain then "This domain controller is the last controller for the domain" should be remain unchecked when you demote SERVER2 DC. 
    If you are getting error "Active Directory domain controllers for that domain can be contacted" while demoting SERVER2 DC then check the DNS pointing on both as per below article, disable windows firewall on all DC, less possiblities but worth to check if both
    are different site then check the ports are open on firewall. 
    http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
    http://technet.microsoft.com/en-us/library/cc766337(v=ws.10).aspx
    http://social.technet.microsoft.com/wiki/contents/articles/584.active-directory-replication-over-firewalls.aspx
    run “ipconfig /flushdns & ipconfig /registerdns“, restart DNS server and NETLOGON service on each DC and try to demote server2 DC.
    If issue reoccurs, post dcdiag /q result.
    NOTE: If initial replication was completed between both DC (new 2012 and old DC) then you may remove the server2 DC from Active Directory forcefully (DCPROMO /FORCEREMOVAL) and perform metadata cleanup.
    Active Directory Metadata Cleanup
    http://abhijitw.wordpress.com/2012/03/03/active-directory-metadata-cleanup/
    Best regards,
    Abhijit Waikar.
    MCSA | MCSA:Messaging | MCITP:SA | MCC:2012
    Blog: http://abhijitw.wordpress.com
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

Maybe you are looking for

  • How to get  a Current Navigation model  Current Selection (node) ID

    Hi, we are using default navigation model for page navigation in our application. I am trying to get Id of Default Navigation model node, I am able to get the Title using following code which available in globe template. Code – pageTemaplate_globe.js

  • Music format. URGENT HELP NEEDED....

    can any1 help me in answering is it possible to covert an mp4 file back to an mp3... i ahve burnt music off a mates computer in mp4 format onto a cd. i ahve now loaded it onto my i tunes but i need the cd in the computer for it to play.... there take

  • System Programs Not Working (BUILD 9926)

    Ever since the update the following will not work: PC Settings Start Menu New Cortana Action Center I know it's a bug, but is there any temporary fix? I've tried restarting a few times to no avail.

  • How to reply to discussion

    I am now looking for how to reply to a discussion I started but suggestions were made and I want to clarify my question. Thanks

  • How to get iPhone 4 to take smaller file sized photos

    All my photos taken with the iPhone camera app take 2 to 3MB size photos. How do I adjust phone to smaller jpeg sizes under 1 MB? Thank you