API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Apr 23rd, 2019
951
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 99.26 KB | None | 0 0
raw download clone embed print report
  1. Command Line: "dcdiag.exe
  2. /V /C /D /E /s:WPCALDC02"
  3.  
  4. Directory Server Diagnosis
  5.  
  6.  
  7. Performing initial setup:
  8.  
  9. * Connecting to directory service on server WPCALDC02.
  10.  
  11. WPCALDC02.currentTime = 20190423205838.0Z
  12.  
  13. WPCALDC02.highestCommittedUSN = 8950670
  14.  
  15. WPCALDC02.isSynchronized = 1
  16.  
  17. WPCALDC02.isGlobalCatalogReady = 1
  18.  
  19. * Identified AD Forest.
  20. Collecting AD specific global data
  21. * Collecting site info.
  22.  
  23. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=test,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
  24. The previous call succeeded
  25. Iterating through the sites
  26. Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  27. Getting ISTG and options for the site
  28. * Identifying all servers.
  29.  
  30. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=test,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
  31. The previous call succeeded....
  32. The previous call succeeded
  33. Iterating through the list of servers
  34. Getting information for the server CN=NTDS Settings,CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  35. objectGuid obtained
  36. InvocationID obtained
  37. dnsHostname obtained
  38. site info obtained
  39. All the info for the server collected
  40. Getting information for the server CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  41. objectGuid obtained
  42. InvocationID obtained
  43. dnsHostname obtained
  44. site info obtained
  45. All the info for the server collected
  46. WPCALDC02.currentTime = 20190423205838.0Z
  47.  
  48. WPCALDC02.highestCommittedUSN = 8950670
  49.  
  50. WPCALDC02.isSynchronized = 1
  51.  
  52. WPCALDC02.isGlobalCatalogReady = 1
  53.  
  54. * Identifying all NC cross-refs.
  55.  
  56. WPDC01.currentTime = 20190423205839.0Z
  57.  
  58. WPDC01.highestCommittedUSN = 12166685
  59.  
  60. WPDC01.isSynchronized = 1
  61.  
  62. WPDC01.isGlobalCatalogReady = 1
  63.  
  64. * Found 2 DC(s). Testing 2 of them.
  65.  
  66. Done gathering initial info.
  67.  
  68.  
  69.  
  70. ===============================================Printing out pDsInfo
  71.  
  72. GLOBAL:
  73. ulNumServers=2
  74. pszRootDomain=test.com
  75. pszNC=
  76. pszRootDomainFQDN=DC=test,DC=com
  77. pszConfigNc=CN=Configuration,DC=test,DC=com
  78. pszPartitionsDn=CN=Partitions,CN=Configuration,DC=test,DC=com
  79. fAdam=0
  80. iSiteOptions=0
  81. dwTombstoneLifeTimeDays=180
  82.  
  83. dwForestBehaviorVersion=4
  84.  
  85. HomeServer=1, WPCALDC02
  86.  
  87. SERVER: pServer[0].pszName=WPDC01
  88. pServer[0].pszGuidDNSName (binding str)=2cbeed59-4eca-4f48-af71-640b5c843801._msdcs.test.com
  89. pServer[0].pszDNSName=srdc01.test.com
  90. pServer[0].pszLdapPort=(null)
  91. pServer[0].pszSslPort=(null)
  92. pServer[0].pszDn=CN=NTDS Settings,CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  93. pServer[0].pszComputerAccountDn=CN=WPDC01,OU=Domain Controllers,DC=test,DC=com
  94. pServer[0].uuidObjectGuid=2cbeed59-4eca-4f48-af71-640b5c843801
  95. pServer[0].uuidInvocationId=551ff08b-6dd9-47f3-8bf2-93280c978344
  96. pServer[0].iSite=0 (Default-First-Site-Name)
  97. pServer[0].iOptions=1
  98. pServer[0].ftLocalAcquireTime=5358d730 01d4fa17
  99.  
  100. pServer[0].ftRemoteConnectTime=53572980 01d4fa17
  101.  
  102. pServer[0].ppszMaster/FullReplicaNCs:
  103. ppszMaster/FullReplicaNCs[0]=DC=ForestDnsZones,DC=test,DC=com
  104. ppszMaster/FullReplicaNCs[1]=DC=DomainDnsZones,DC=test,DC=com
  105. ppszMaster/FullReplicaNCs[2]=CN=Schema,CN=Configuration,DC=test,DC=com
  106. ppszMaster/FullReplicaNCs[3]=CN=Configuration,DC=test,DC=com
  107. ppszMaster/FullReplicaNCs[4]=DC=test,DC=com
  108.  
  109. SERVER: pServer[1].pszName=WPCALDC02
  110. pServer[1].pszGuidDNSName (binding str)=bb16129b-d7b7-4a76-9382-fbedf83d100c._msdcs.test.com
  111. pServer[1].pszDNSName=WPCALDC02.test.com
  112. pServer[1].pszLdapPort=(null)
  113. pServer[1].pszSslPort=(null)
  114. pServer[1].pszDn=CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  115. pServer[1].pszComputerAccountDn=CN=WPCALDC02,OU=Domain Controllers,DC=test,DC=com
  116. pServer[1].uuidObjectGuid=bb16129b-d7b7-4a76-9382-fbedf83d100c
  117. pServer[1].uuidInvocationId=d4d262cf-a40c-4700-a98f-bf5e1d296064
  118. pServer[1].iSite=0 (Default-First-Site-Name)
  119. pServer[1].iOptions=1
  120. pServer[1].ftLocalAcquireTime=53568d40 01d4fa17
  121.  
  122. pServer[1].ftRemoteConnectTime=52be9300 01d4fa17
  123.  
  124. pServer[1].ppszMaster/FullReplicaNCs:
  125. ppszMaster/FullReplicaNCs[0]=DC=ForestDnsZones,DC=test,DC=com
  126. ppszMaster/FullReplicaNCs[1]=DC=DomainDnsZones,DC=test,DC=com
  127. ppszMaster/FullReplicaNCs[2]=CN=Schema,CN=Configuration,DC=test,DC=com
  128. ppszMaster/FullReplicaNCs[3]=CN=Configuration,DC=test,DC=com
  129. ppszMaster/FullReplicaNCs[4]=DC=test,DC=com
  130.  
  131. SITES: pSites[0].pszName=Default-First-Site-Name
  132. pSites[0].pszSiteSettings=CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  133. pSites[0].pszISTG=CN=NTDS Settings,CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  134. pSites[0].iSiteOption=0
  135.  
  136. pSites[0].cServers=2
  137.  
  138. NC: pNCs[0].pszName=ForestDnsZones
  139. pNCs[0].pszDn=DC=ForestDnsZones,DC=test,DC=com
  140.  
  141. pNCs[0].aCrInfo[0].dwFlags=0x00000201
  142. pNCs[0].aCrInfo[0].pszDn=CN=d8941ed0-5bf0-45a4-a787-08e2e0d22251,CN=Partitions,CN=Configuration,DC=test,DC=com
  143. pNCs[0].aCrInfo[0].pszDnsRoot=ForestDnsZones.test.com
  144. pNCs[0].aCrInfo[0].iSourceServer=1
  145. pNCs[0].aCrInfo[0].pszSourceServer=(null)
  146. pNCs[0].aCrInfo[0].ulSystemFlags=0x00000005
  147. pNCs[0].aCrInfo[0].bEnabled=TRUE
  148. pNCs[0].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[0].aCrInfo[0].pszSDReferenceDomain=(null)
  149. pNCs[0].aCrInfo[0].pszNetBiosName=(null)
  150. pNCs[0].aCrInfo[0].cReplicas=-1
  151. pNCs[0].aCrInfo[0].aszReplicas=
  152.  
  153.  
  154. NC: pNCs[1].pszName=DomainDnsZones
  155. pNCs[1].pszDn=DC=DomainDnsZones,DC=test,DC=com
  156.  
  157. pNCs[1].aCrInfo[0].dwFlags=0x00000201
  158. pNCs[1].aCrInfo[0].pszDn=CN=afb835d1-b56f-401a-95b2-1b8d96a75128,CN=Partitions,CN=Configuration,DC=test,DC=com
  159. pNCs[1].aCrInfo[0].pszDnsRoot=DomainDnsZones.test.com
  160. pNCs[1].aCrInfo[0].iSourceServer=1
  161. pNCs[1].aCrInfo[0].pszSourceServer=(null)
  162. pNCs[1].aCrInfo[0].ulSystemFlags=0x00000005
  163. pNCs[1].aCrInfo[0].bEnabled=TRUE
  164. pNCs[1].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[1].aCrInfo[0].pszSDReferenceDomain=(null)
  165. pNCs[1].aCrInfo[0].pszNetBiosName=(null)
  166. pNCs[1].aCrInfo[0].cReplicas=-1
  167. pNCs[1].aCrInfo[0].aszReplicas=
  168.  
  169.  
  170. NC: pNCs[2].pszName=Schema
  171. pNCs[2].pszDn=CN=Schema,CN=Configuration,DC=test,DC=com
  172.  
  173. pNCs[2].aCrInfo[0].dwFlags=0x00000201
  174. pNCs[2].aCrInfo[0].pszDn=CN=Enterprise Schema,CN=Partitions,CN=Configuration,DC=test,DC=com
  175. pNCs[2].aCrInfo[0].pszDnsRoot=test.com
  176. pNCs[2].aCrInfo[0].iSourceServer=1
  177. pNCs[2].aCrInfo[0].pszSourceServer=(null)
  178. pNCs[2].aCrInfo[0].ulSystemFlags=0x00000001
  179. pNCs[2].aCrInfo[0].bEnabled=TRUE
  180. pNCs[2].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[2].aCrInfo[0].pszSDReferenceDomain=(null)
  181. pNCs[2].aCrInfo[0].pszNetBiosName=(null)
  182. pNCs[2].aCrInfo[0].cReplicas=-1
  183. pNCs[2].aCrInfo[0].aszReplicas=
  184.  
  185.  
  186. NC: pNCs[3].pszName=Configuration
  187. pNCs[3].pszDn=CN=Configuration,DC=test,DC=com
  188.  
  189. pNCs[3].aCrInfo[0].dwFlags=0x00000201
  190. pNCs[3].aCrInfo[0].pszDn=CN=Enterprise Configuration,CN=Partitions,CN=Configuration,DC=test,DC=com
  191. pNCs[3].aCrInfo[0].pszDnsRoot=test.com
  192. pNCs[3].aCrInfo[0].iSourceServer=1
  193. pNCs[3].aCrInfo[0].pszSourceServer=(null)
  194. pNCs[3].aCrInfo[0].ulSystemFlags=0x00000001
  195. pNCs[3].aCrInfo[0].bEnabled=TRUE
  196. pNCs[3].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[3].aCrInfo[0].pszSDReferenceDomain=(null)
  197. pNCs[3].aCrInfo[0].pszNetBiosName=(null)
  198. pNCs[3].aCrInfo[0].cReplicas=-1
  199. pNCs[3].aCrInfo[0].aszReplicas=
  200.  
  201.  
  202. NC: pNCs[4].pszName=test
  203. pNCs[4].pszDn=DC=test,DC=com
  204.  
  205. pNCs[4].aCrInfo[0].dwFlags=0x00000201
  206. pNCs[4].aCrInfo[0].pszDn=CN=WPNINC,CN=Partitions,CN=Configuration,DC=test,DC=com
  207. pNCs[4].aCrInfo[0].pszDnsRoot=test.com
  208. pNCs[4].aCrInfo[0].iSourceServer=1
  209. pNCs[4].aCrInfo[0].pszSourceServer=(null)
  210. pNCs[4].aCrInfo[0].ulSystemFlags=0x00000003
  211. pNCs[4].aCrInfo[0].bEnabled=TRUE
  212. pNCs[4].aCrInfo[0].ftWhenCreated=00000000 00000000 pNCs[4].aCrInfo[0].pszSDReferenceDomain=(null)
  213. pNCs[4].aCrInfo[0].pszNetBiosName=(null)
  214. pNCs[4].aCrInfo[0].cReplicas=-1
  215. pNCs[4].aCrInfo[0].aszReplicas=
  216.  
  217.  
  218. 5 NC TARGETS: ForestDnsZones, DomainDnsZones, Schema, Configuration, test,
  219. 2 TARGETS: WPDC01, WPCALDC02,
  220.  
  221. =============================================Done Printing pDsInfo
  222.  
  223. Doing initial required tests
  224.  
  225.  
  226. Testing server: Default-First-Site-Name\WPDC01
  227.  
  228. Starting test: Connectivity
  229.  
  230. * Active Directory LDAP Services Check
  231. Determining IP4 connectivity
  232. Failure Analysis: WPDC01 ... OK.
  233. * Active Directory RPC Services Check
  234. ......................... WPDC01 passed test Connectivity
  235.  
  236.  
  237. Testing server: Default-First-Site-Name\WPCALDC02
  238.  
  239. Starting test: Connectivity
  240.  
  241. * Active Directory LDAP Services Check
  242. Determining IP4 connectivity
  243. Failure Analysis: WPCALDC02 ... OK.
  244. * Active Directory RPC Services Check
  245. ......................... WPCALDC02 passed test Connectivity
  246.  
  247.  
  248.  
  249. Doing primary tests
  250.  
  251.  
  252. Testing server: Default-First-Site-Name\WPDC01
  253.  
  254. Starting test: Advertising
  255.  
  256. The DC WPDC01 is advertising itself as a DC and having a DS.
  257. The DC WPDC01 is advertising as an LDAP server
  258. The DC WPDC01 is advertising as having a writeable directory
  259. The DC WPDC01 is advertising as a Key Distribution Center
  260. Warning: WPDC01 is not advertising as a time server.
  261.  
  262. The DS WPDC01 is advertising as a GC.
  263. ......................... WPDC01 failed test Advertising
  264.  
  265. Starting test: CheckSecurityError
  266.  
  267. * Dr Auth: Beginning security errors check!
  268. Found KDC WPCALDC02 for domain test.com in site Default-First-Site-Name
  269. Checking machine account for DC WPDC01 on DC WPCALDC02.
  270. * SPN found :LDAP/srdc01.test.com/test.com
  271. * SPN found :LDAP/srdc01.test.com
  272. * SPN found :LDAP/WPDC01
  273. * SPN found :LDAP/srdc01.test.com/WPNINC
  274. * SPN found :LDAP/2cbeed59-4eca-4f48-af71-640b5c843801._msdcs.test.com
  275. * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/2cbeed59-4eca-4f48-af71-640b5c843801/test.com
  276. * SPN found :HOST/srdc01.test.com/test.com
  277. * SPN found :HOST/srdc01.test.com
  278. * SPN found :HOST/WPDC01
  279. * SPN found :HOST/srdc01.test.com/WPNINC
  280. * SPN found :GC/srdc01.test.com/test.com
  281. Checking for CN=WPDC01,OU=Domain Controllers,DC=test,DC=com in domain DC=test,DC=com on 2 servers
  282. Object is up-to-date on all servers.
  283. [WPDC01] No security related replication errors were found on this DC!
  284.  
  285. To target the connection to a specific source DC use
  286.  
  287. /ReplSource:<DC>.
  288.  
  289. ......................... WPDC01 passed test CheckSecurityError
  290.  
  291. Starting test: CutoffServers
  292.  
  293. * Configuration Topology Aliveness Check
  294. * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=test,DC=com.
  295. * Performing upstream (of target) analysis.
  296. * Performing downstream (of target) analysis.
  297. * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=test,DC=com.
  298. * Performing upstream (of target) analysis.
  299. * Performing downstream (of target) analysis.
  300. * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=test,DC=com.
  301. * Performing upstream (of target) analysis.
  302. * Performing downstream (of target) analysis.
  303. * Analyzing the alive system replication topology for CN=Configuration,DC=test,DC=com.
  304. * Performing upstream (of target) analysis.
  305. * Performing downstream (of target) analysis.
  306. * Analyzing the alive system replication topology for DC=test,DC=com.
  307. * Performing upstream (of target) analysis.
  308. * Performing downstream (of target) analysis.
  309. ......................... WPDC01 passed test CutoffServers
  310.  
  311. Starting test: FrsEvent
  312.  
  313. * The File Replication Service Event log test
  314. Skip the test because the server is running DFSR.
  315.  
  316. ......................... WPDC01 passed test FrsEvent
  317.  
  318. Starting test: DFSREvent
  319.  
  320. The DFS Replication Event Log.
  321. There are warning or error events within the last 24 hours after the
  322.  
  323. SYSVOL has been shared. Failing SYSVOL replication problems may cause
  324.  
  325. Group Policy problems.
  326. A warning event occurred. EventID: 0x80001396
  327.  
  328. Time Generated: 04/22/2019 19:00:25
  329.  
  330. Event String:
  331.  
  332. The DFS Replication service is stopping communication with partner WPCALDC02 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
  333.  
  334.  
  335.  
  336. Additional Information:
  337.  
  338. Error: 9033 (The request was cancelled by a shutdown)
  339.  
  340. Connection ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  341.  
  342. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  343.  
  344. A warning event occurred. EventID: 0x80001206
  345.  
  346. Time Generated: 04/22/2019 21:24:08
  347.  
  348. Event String:
  349.  
  350. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner . If the server was in the process of being promoted to a domain controller, the domain controller will not advertize and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the synchronization partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  351.  
  352.  
  353.  
  354. Additional Information:
  355.  
  356. Replicated Folder Name: SYSVOL Share
  357.  
  358. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  359.  
  360. Replication Group Name: Domain System Volume
  361.  
  362. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  363.  
  364. Member ID: 1226CE16-5FC7-4193-96F1-CFD2028313BA
  365.  
  366. Read-Only: 0
  367.  
  368. An error event occurred. EventID: 0xC000138A
  369.  
  370. Time Generated: 04/22/2019 21:24:15
  371.  
  372. Event String:
  373.  
  374. The DFS Replication service encountered an error communicating with partner WPCALDC02 for replication group Domain System Volume.
  375.  
  376.  
  377.  
  378. Partner DNS address: WPCALDC02.test.com
  379.  
  380.  
  381.  
  382. Optional data if available:
  383.  
  384. Partner WINS Address: WPCALDC02
  385.  
  386. Partner IP Address: 10.200.60.12
  387.  
  388.  
  389.  
  390. The service will retry the connection periodically.
  391.  
  392.  
  393.  
  394. Additional Information:
  395.  
  396. Error: 1753 (There are no more endpoints available from the endpoint mapper.)
  397.  
  398. Connection ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  399.  
  400. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  401.  
  402. An error event occurred. EventID: 0xC0001204
  403.  
  404. Time Generated: 04/22/2019 21:24:15
  405.  
  406. Event String:
  407.  
  408. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner WPCALDC02.test.com. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  409.  
  410.  
  411.  
  412. Additional Information:
  413.  
  414. Replicated Folder Name: SYSVOL Share
  415.  
  416. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  417.  
  418. Replication Group Name: Domain System Volume
  419.  
  420. Replication Group ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  421.  
  422. Member ID: 1226CE16-5FC7-4193-96F1-CFD2028313BA
  423.  
  424. Read-Only: 0
  425.  
  426. A warning event occurred. EventID: 0x80001206
  427.  
  428. Time Generated: 04/23/2019 10:18:21
  429.  
  430. Event String:
  431.  
  432. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner . If the server was in the process of being promoted to a domain controller, the domain controller will not advertize and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the synchronization partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  433.  
  434.  
  435.  
  436. Additional Information:
  437.  
  438. Replicated Folder Name: SYSVOL Share
  439.  
  440. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  441.  
  442. Replication Group Name: Domain System Volume
  443.  
  444. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  445.  
  446. Member ID: 1226CE16-5FC7-4193-96F1-CFD2028313BA
  447.  
  448. Read-Only: 0
  449.  
  450. A warning event occurred. EventID: 0x80001396
  451.  
  452. Time Generated: 04/23/2019 12:51:19
  453.  
  454. Event String:
  455.  
  456. The DFS Replication service is stopping communication with partner WPCALDC02 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
  457.  
  458.  
  459.  
  460. Additional Information:
  461.  
  462. Error: 9033 (The request was cancelled by a shutdown)
  463.  
  464. Connection ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  465.  
  466. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  467.  
  468. An error event occurred. EventID: 0xC000138A
  469.  
  470. Time Generated: 04/23/2019 12:52:11
  471.  
  472. Event String:
  473.  
  474. The DFS Replication service encountered an error communicating with partner WPCALDC02 for replication group Domain System Volume.
  475.  
  476.  
  477.  
  478. Partner DNS address: WPCALDC02.test.com
  479.  
  480.  
  481.  
  482. Optional data if available:
  483.  
  484. Partner WINS Address: WPCALDC02
  485.  
  486. Partner IP Address: 10.200.60.12
  487.  
  488.  
  489.  
  490. The service will retry the connection periodically.
  491.  
  492.  
  493.  
  494. Additional Information:
  495.  
  496. Error: 1726 (The remote procedure call failed.)
  497.  
  498. Connection ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  499.  
  500. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  501.  
  502. An error event occurred. EventID: 0xC0001204
  503.  
  504. Time Generated: 04/23/2019 12:52:11
  505.  
  506. Event String:
  507.  
  508. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner WPCALDC02.test.com. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  509.  
  510.  
  511.  
  512. Additional Information:
  513.  
  514. Replicated Folder Name: SYSVOL Share
  515.  
  516. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  517.  
  518. Replication Group Name: Domain System Volume
  519.  
  520. Replication Group ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  521.  
  522. Member ID: 1226CE16-5FC7-4193-96F1-CFD2028313BA
  523.  
  524. Read-Only: 0
  525.  
  526. An error event occurred. EventID: 0xC0001390
  527.  
  528. Time Generated: 04/23/2019 12:58:59
  529.  
  530. Event String:
  531.  
  532. The DFS Replication service failed to communicate with partner WPCALDC02 for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.
  533.  
  534.  
  535.  
  536. Partner DNS Address: WPCALDC02.test.com
  537.  
  538.  
  539.  
  540. Optional data if available:
  541.  
  542. Partner WINS Address: WPCALDC02
  543.  
  544. Partner IP Address: 10.200.60.12
  545.  
  546.  
  547.  
  548. The service will retry the connection periodically.
  549.  
  550.  
  551.  
  552. Additional Information:
  553.  
  554. Error: 1722 (The RPC server is unavailable.)
  555.  
  556. Connection ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  557.  
  558. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  559.  
  560. An error event occurred. EventID: 0xC0001204
  561.  
  562. Time Generated: 04/23/2019 12:58:59
  563.  
  564. Event String:
  565.  
  566. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner WPCALDC02.test.com. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  567.  
  568.  
  569.  
  570. Additional Information:
  571.  
  572. Replicated Folder Name: SYSVOL Share
  573.  
  574. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  575.  
  576. Replication Group Name: Domain System Volume
  577.  
  578. Replication Group ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  579.  
  580. Member ID: 1226CE16-5FC7-4193-96F1-CFD2028313BA
  581.  
  582. Read-Only: 0
  583.  
  584. A warning event occurred. EventID: 0x80001206
  585.  
  586. Time Generated: 04/23/2019 13:47:09
  587.  
  588. Event String:
  589.  
  590. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner . If the server was in the process of being promoted to a domain controller, the domain controller will not advertize and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the synchronization partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  591.  
  592.  
  593.  
  594. Additional Information:
  595.  
  596. Replicated Folder Name: SYSVOL Share
  597.  
  598. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  599.  
  600. Replication Group Name: Domain System Volume
  601.  
  602. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  603.  
  604. Member ID: 1226CE16-5FC7-4193-96F1-CFD2028313BA
  605.  
  606. Read-Only: 0
  607.  
  608. An error event occurred. EventID: 0xC000138A
  609.  
  610. Time Generated: 04/23/2019 13:47:16
  611.  
  612. Event String:
  613.  
  614. The DFS Replication service encountered an error communicating with partner WPCALDC02 for replication group Domain System Volume.
  615.  
  616.  
  617.  
  618. Partner DNS address: WPCALDC02.test.com
  619.  
  620.  
  621.  
  622. Optional data if available:
  623.  
  624. Partner WINS Address: WPCALDC02
  625.  
  626. Partner IP Address: 10.200.60.12
  627.  
  628.  
  629.  
  630. The service will retry the connection periodically.
  631.  
  632.  
  633.  
  634. Additional Information:
  635.  
  636. Error: 1753 (There are no more endpoints available from the endpoint mapper.)
  637.  
  638. Connection ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  639.  
  640. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  641.  
  642. An error event occurred. EventID: 0xC0001204
  643.  
  644. Time Generated: 04/23/2019 13:47:16
  645.  
  646. Event String:
  647.  
  648. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner WPCALDC02.test.com. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  649.  
  650.  
  651.  
  652. Additional Information:
  653.  
  654. Replicated Folder Name: SYSVOL Share
  655.  
  656. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  657.  
  658. Replication Group Name: Domain System Volume
  659.  
  660. Replication Group ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  661.  
  662. Member ID: 1226CE16-5FC7-4193-96F1-CFD2028313BA
  663.  
  664. Read-Only: 0
  665.  
  666. A warning event occurred. EventID: 0x80001396
  667.  
  668. Time Generated: 04/23/2019 14:01:32
  669.  
  670. Event String:
  671.  
  672. The DFS Replication service is stopping communication with partner WPCALDC02 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
  673.  
  674.  
  675.  
  676. Additional Information:
  677.  
  678. Error: 9033 (The request was cancelled by a shutdown)
  679.  
  680. Connection ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  681.  
  682. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  683.  
  684. An error event occurred. EventID: 0xC000138A
  685.  
  686. Time Generated: 04/23/2019 14:02:05
  687.  
  688. Event String:
  689.  
  690. The DFS Replication service encountered an error communicating with partner WPCALDC02 for replication group Domain System Volume.
  691.  
  692.  
  693.  
  694. Partner DNS address: WPCALDC02.test.com
  695.  
  696.  
  697.  
  698. Optional data if available:
  699.  
  700. Partner WINS Address: WPCALDC02
  701.  
  702. Partner IP Address: 10.200.60.12
  703.  
  704.  
  705.  
  706. The service will retry the connection periodically.
  707.  
  708.  
  709.  
  710. Additional Information:
  711.  
  712. Error: 1726 (The remote procedure call failed.)
  713.  
  714. Connection ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  715.  
  716. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  717.  
  718. An error event occurred. EventID: 0xC0001204
  719.  
  720. Time Generated: 04/23/2019 14:02:05
  721.  
  722. Event String:
  723.  
  724. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner WPCALDC02.test.com. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  725.  
  726.  
  727.  
  728. Additional Information:
  729.  
  730. Replicated Folder Name: SYSVOL Share
  731.  
  732. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  733.  
  734. Replication Group Name: Domain System Volume
  735.  
  736. Replication Group ID: 31F9EA04-C3DF-4EEA-959D-6DC6A10EAB01
  737.  
  738. Member ID: 1226CE16-5FC7-4193-96F1-CFD2028313BA
  739.  
  740. Read-Only: 0
  741.  
  742. ......................... WPDC01 failed test DFSREvent
  743.  
  744. Starting test: SysVolCheck
  745.  
  746. * The File Replication Service SYSVOL ready test
  747. File Replication Service's SYSVOL is ready
  748. ......................... WPDC01 passed test SysVolCheck
  749.  
  750. Starting test: FrsSysVol
  751.  
  752. * The File Replication Service SYSVOL ready test
  753. File Replication Service's SYSVOL is ready
  754. ......................... WPDC01 passed test FrsSysVol
  755.  
  756. Starting test: KccEvent
  757.  
  758. * The KCC Event log test
  759. Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
  760. ......................... WPDC01 passed test KccEvent
  761.  
  762. Starting test: KnowsOfRoleHolders
  763.  
  764. Role Schema Owner = CN=NTDS Settings,CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  765. Role Domain Owner = CN=NTDS Settings,CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  766. Role PDC Owner = CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  767. Role Rid Owner = CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  768. Role Infrastructure Update Owner = CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  769. ......................... WPDC01 passed test KnowsOfRoleHolders
  770.  
  771. Starting test: MachineAccount
  772.  
  773. Checking machine account for DC WPDC01 on DC WPDC01.
  774. * SPN found :LDAP/srdc01.test.com/test.com
  775. * SPN found :LDAP/srdc01.test.com
  776. * SPN found :LDAP/WPDC01
  777. * SPN found :LDAP/srdc01.test.com/WPNINC
  778. * SPN found :LDAP/2cbeed59-4eca-4f48-af71-640b5c843801._msdcs.test.com
  779. * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/2cbeed59-4eca-4f48-af71-640b5c843801/test.com
  780. * SPN found :HOST/srdc01.test.com/test.com
  781. * SPN found :HOST/srdc01.test.com
  782. * SPN found :HOST/WPDC01
  783. * SPN found :HOST/srdc01.test.com/WPNINC
  784. * SPN found :GC/srdc01.test.com/test.com
  785. ......................... WPDC01 passed test MachineAccount
  786.  
  787. Starting test: NCSecDesc
  788.  
  789. * Security Permissions check for all NC's on DC WPDC01.
  790. * Security Permissions Check for
  791.  
  792. DC=ForestDnsZones,DC=test,DC=com
  793. (NDNC,Version 3)
  794. * Security Permissions Check for
  795.  
  796. DC=DomainDnsZones,DC=test,DC=com
  797. (NDNC,Version 3)
  798. * Security Permissions Check for
  799.  
  800. CN=Schema,CN=Configuration,DC=test,DC=com
  801. (Schema,Version 3)
  802. * Security Permissions Check for
  803.  
  804. CN=Configuration,DC=test,DC=com
  805. (Configuration,Version 3)
  806. * Security Permissions Check for
  807.  
  808. DC=test,DC=com
  809. (Domain,Version 3)
  810. ......................... WPDC01 passed test NCSecDesc
  811.  
  812. Starting test: NetLogons
  813.  
  814. * Network Logons Privileges Check
  815. Verified share \\WPDC01\netlogon
  816. Verified share \\WPDC01\sysvol
  817. ......................... WPDC01 passed test NetLogons
  818.  
  819. Starting test: ObjectsReplicated
  820.  
  821. WPDC01 is in domain DC=test,DC=com
  822. Checking for CN=WPDC01,OU=Domain Controllers,DC=test,DC=com in domain DC=test,DC=com on 2 servers
  823. Object is up-to-date on all servers.
  824. Checking for CN=NTDS Settings,CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com in domain CN=Configuration,DC=test,DC=com on 2 servers
  825. Object is up-to-date on all servers.
  826. ......................... WPDC01 passed test ObjectsReplicated
  827.  
  828. Starting test: OutboundSecureChannels
  829.  
  830. * The Outbound Secure Channels test
  831. ** Did not run Outbound Secure Channels test because /testdomain: was
  832.  
  833. not entered
  834.  
  835. ......................... WPDC01 passed test OutboundSecureChannels
  836.  
  837. Starting test: Replications
  838.  
  839. * Replications Check
  840. DC=ForestDnsZones,DC=test,DC=com has 16 cursors.
  841. DC=DomainDnsZones,DC=test,DC=com has 16 cursors.
  842. CN=Schema,CN=Configuration,DC=test,DC=com has 16 cursors.
  843. CN=Configuration,DC=test,DC=com has 17 cursors.
  844. DC=test,DC=com has 17 cursors.
  845. * Replication Latency Check
  846. DC=ForestDnsZones,DC=test,DC=com
  847. Latency information for 14 entries in the vector were ignored.
  848. 14 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).
  849. DC=DomainDnsZones,DC=test,DC=com
  850. Latency information for 14 entries in the vector were ignored.
  851. 14 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).
  852. CN=Schema,CN=Configuration,DC=test,DC=com
  853. Latency information for 14 entries in the vector were ignored.
  854. 14 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).
  855. CN=Configuration,DC=test,DC=com
  856. Latency information for 15 entries in the vector were ignored.
  857. 15 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
  858. DC=test,DC=com
  859. Latency information for 15 entries in the vector were ignored.
  860. 15 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
  861. ......................... WPDC01 passed test Replications
  862.  
  863. Starting test: RidManager
  864.  
  865. ridManagerReference = CN=RID Manager$,CN=System,DC=test,DC=com
  866. * Available RID Pool for the Domain is 20600 to 1073741823
  867. fSMORoleOwner = CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  868. * WPCALDC02.test.com is the RID Master
  869. * DsBind with RID Master was successful
  870. rIDSetReferences = CN=RID Set,CN=WPDC01,OU=Domain Controllers,DC=test,DC=com
  871. * rIDAllocationPool is 19600 to 20099
  872. * rIDPreviousAllocationPool is 19600 to 20099
  873. * rIDNextRID: 19600
  874. ......................... WPDC01 passed test RidManager
  875.  
  876. Starting test: Services
  877.  
  878. * Checking Service: EventSystem
  879. * Checking Service: RpcSs
  880. * Checking Service: NTDS
  881. * Checking Service: DnsCache
  882. * Checking Service: DFSR
  883. * Checking Service: IsmServ
  884. * Checking Service: kdc
  885. * Checking Service: SamSs
  886. * Checking Service: LanmanServer
  887. * Checking Service: LanmanWorkstation
  888. * Checking Service: w32time
  889. * Checking Service: NETLOGON
  890. ......................... WPDC01 passed test Services
  891.  
  892. Starting test: SystemLog
  893.  
  894. * The System Event log test
  895. A warning event occurred. EventID: 0x0000053C
  896.  
  897. Time Generated: 04/23/2019 14:44:50
  898.  
  899. Event String:
  900.  
  901. The DNS registration for DHCPv4 Client IP address 192.168.4.53 , FQDN w-0516.test.com and DHCID AAEBCBPiJRidbOcg8dG7lP+ION5y11Z4KvfzOdjVc6mSPmQ= has been denied as there is probably an existing client with same FQDN already registered with DNS.
  902.  
  903. A warning event occurred. EventID: 0x0000053C
  904.  
  905. Time Generated: 04/23/2019 14:54:21
  906.  
  907. Event String:
  908.  
  909. The DNS registration for DHCPv4 Client IP address 192.168.4.60 , FQDN w-0526.test.com and DHCID AAEB0q/9BQODLb/JfGaj/8t0kCNswHST/e6SNTdnZEK3XE4= has been denied as there is probably an existing client with same FQDN already registered with DNS.
  910.  
  911. A warning event occurred. EventID: 0x0000053C
  912.  
  913. Time Generated: 04/23/2019 14:56:52
  914.  
  915. Event String:
  916.  
  917. The DNS registration for DHCPv4 Client IP address 192.168.4.57 , FQDN W-0266.test.com and DHCID AAEBEgq9N+BcWbgTctZYvZv1+sjqGRwRYFHl81rNHbI7BLw= has been denied as there is probably an existing client with same FQDN already registered with DNS.
  918.  
  919. Found no errors in "System" Event log in the last 60 minutes.
  920. ......................... WPDC01 passed test SystemLog
  921.  
  922. Starting test: Topology
  923.  
  924. * Configuration Topology Integrity Check
  925. * Analyzing the connection topology for DC=ForestDnsZones,DC=test,DC=com.
  926. * Performing upstream (of target) analysis.
  927. * Performing downstream (of target) analysis.
  928. * Analyzing the connection topology for DC=DomainDnsZones,DC=test,DC=com.
  929. * Performing upstream (of target) analysis.
  930. * Performing downstream (of target) analysis.
  931. * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=test,DC=com.
  932. * Performing upstream (of target) analysis.
  933. * Performing downstream (of target) analysis.
  934. * Analyzing the connection topology for CN=Configuration,DC=test,DC=com.
  935. * Performing upstream (of target) analysis.
  936. * Performing downstream (of target) analysis.
  937. * Analyzing the connection topology for DC=test,DC=com.
  938. * Performing upstream (of target) analysis.
  939. * Performing downstream (of target) analysis.
  940. ......................... WPDC01 passed test Topology
  941.  
  942. Starting test: VerifyEnterpriseReferences
  943.  
  944. ......................... WPDC01 passed test
  945.  
  946. VerifyEnterpriseReferences
  947.  
  948. Starting test: VerifyReferences
  949.  
  950. The system object reference (serverReference)
  951.  
  952. CN=WPDC01,OU=Domain Controllers,DC=test,DC=com and backlink on
  953.  
  954. CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  955.  
  956. are correct.
  957. The system object reference (serverReferenceBL)
  958.  
  959. CN=WPDC01,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=test,DC=com
  960.  
  961. and backlink on
  962.  
  963. CN=NTDS Settings,CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  964.  
  965. are correct.
  966. The system object reference (msDFSR-ComputerReferenceBL)
  967.  
  968. CN=WPDC01,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=test,DC=com
  969.  
  970. and backlink on CN=WPDC01,OU=Domain Controllers,DC=test,DC=com are
  971.  
  972. correct.
  973. ......................... WPDC01 passed test VerifyReferences
  974.  
  975. Starting test: VerifyReplicas
  976.  
  977. ......................... WPDC01 passed test VerifyReplicas
  978.  
  979.  
  980. Testing server: Default-First-Site-Name\WPCALDC02
  981.  
  982. Starting test: Advertising
  983.  
  984. The DC WPCALDC02 is advertising itself as a DC and having a DS.
  985. The DC WPCALDC02 is advertising as an LDAP server
  986. The DC WPCALDC02 is advertising as having a writeable directory
  987. The DC WPCALDC02 is advertising as a Key Distribution Center
  988. The DC WPCALDC02 is advertising as a time server
  989. The DS WPCALDC02 is advertising as a GC.
  990. ......................... WPCALDC02 passed test Advertising
  991.  
  992. Starting test: CheckSecurityError
  993.  
  994. * Dr Auth: Beginning security errors check!
  995. Found KDC WPCALDC02 for domain test.com in site Default-First-Site-Name
  996. Checking machine account for DC WPCALDC02 on DC WPCALDC02.
  997. * SPN found :LDAP/WPCALDC02.test.com/test.com
  998. * SPN found :LDAP/WPCALDC02.test.com
  999. * SPN found :LDAP/WPCALDC02
  1000. * SPN found :LDAP/WPCALDC02.test.com/WPNINC
  1001. * SPN found :LDAP/bb16129b-d7b7-4a76-9382-fbedf83d100c._msdcs.test.com
  1002. * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/bb16129b-d7b7-4a76-9382-fbedf83d100c/test.com
  1003. * SPN found :HOST/WPCALDC02.test.com/test.com
  1004. * SPN found :HOST/WPCALDC02.test.com
  1005. * SPN found :HOST/WPCALDC02
  1006. * SPN found :HOST/WPCALDC02.test.com/WPNINC
  1007. * SPN found :GC/WPCALDC02.test.com/test.com
  1008. [WPCALDC02] No security related replication errors were found on this
  1009.  
  1010. DC! To target the connection to a specific source DC use
  1011.  
  1012. /ReplSource:<DC>.
  1013.  
  1014. ......................... WPCALDC02 passed test CheckSecurityError
  1015.  
  1016. Starting test: CutoffServers
  1017.  
  1018. * Configuration Topology Aliveness Check
  1019. * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=test,DC=com.
  1020. * Performing upstream (of target) analysis.
  1021. * Performing downstream (of target) analysis.
  1022. * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=test,DC=com.
  1023. * Performing upstream (of target) analysis.
  1024. * Performing downstream (of target) analysis.
  1025. * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=test,DC=com.
  1026. * Performing upstream (of target) analysis.
  1027. * Performing downstream (of target) analysis.
  1028. * Analyzing the alive system replication topology for CN=Configuration,DC=test,DC=com.
  1029. * Performing upstream (of target) analysis.
  1030. * Performing downstream (of target) analysis.
  1031. * Analyzing the alive system replication topology for DC=test,DC=com.
  1032. * Performing upstream (of target) analysis.
  1033. * Performing downstream (of target) analysis.
  1034. ......................... WPCALDC02 passed test CutoffServers
  1035.  
  1036. Starting test: FrsEvent
  1037.  
  1038. * The File Replication Service Event log test
  1039. Skip the test because the server is running DFSR.
  1040.  
  1041. ......................... WPCALDC02 passed test FrsEvent
  1042.  
  1043. Starting test: DFSREvent
  1044.  
  1045. The DFS Replication Event Log.
  1046. There are warning or error events within the last 24 hours after the
  1047.  
  1048. SYSVOL has been shared. Failing SYSVOL replication problems may cause
  1049.  
  1050. Group Policy problems.
  1051. A warning event occurred. EventID: 0x80001396
  1052.  
  1053. Time Generated: 04/22/2019 21:00:21
  1054.  
  1055. Event String:
  1056.  
  1057. The DFS Replication service is stopping communication with partner WPDC01 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
  1058.  
  1059.  
  1060.  
  1061. Additional Information:
  1062.  
  1063. Error: 9033 (The request was cancelled by a shutdown)
  1064.  
  1065. Connection ID: 2B275E6F-1EDE-4F5A-929A-492BA6ECD70B
  1066.  
  1067. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  1068.  
  1069. A warning event occurred. EventID: 0x80001396
  1070.  
  1071. Time Generated: 04/22/2019 21:54:24
  1072.  
  1073. Event String:
  1074.  
  1075. The DFS Replication service is stopping communication with partner WPDC01 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
  1076.  
  1077.  
  1078.  
  1079. Additional Information:
  1080.  
  1081. Error: 9033 (The request was cancelled by a shutdown)
  1082.  
  1083. Connection ID: 2B275E6F-1EDE-4F5A-929A-492BA6ECD70B
  1084.  
  1085. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  1086.  
  1087. A warning event occurred. EventID: 0x80001206
  1088.  
  1089. Time Generated: 04/22/2019 21:54:39
  1090.  
  1091. Event String:
  1092.  
  1093. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner . If the server was in the process of being promoted to a domain controller, the domain controller will not advertize and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the synchronization partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  1094.  
  1095.  
  1096.  
  1097. Additional Information:
  1098.  
  1099. Replicated Folder Name: SYSVOL Share
  1100.  
  1101. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  1102.  
  1103. Replication Group Name: Domain System Volume
  1104.  
  1105. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  1106.  
  1107. Member ID: 1A6AB88D-9D62-4369-8322-4681021E5B09
  1108.  
  1109. Read-Only: 0
  1110.  
  1111. A warning event occurred. EventID: 0x80001396
  1112.  
  1113. Time Generated: 04/22/2019 21:55:58
  1114.  
  1115. Event String:
  1116.  
  1117. The DFS Replication service is stopping communication with partner WPDC01 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
  1118.  
  1119.  
  1120.  
  1121. Additional Information:
  1122.  
  1123. Error: 9033 (The request was cancelled by a shutdown)
  1124.  
  1125. Connection ID: 2B275E6F-1EDE-4F5A-929A-492BA6ECD70B
  1126.  
  1127. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  1128.  
  1129. An error event occurred. EventID: 0xC000138A
  1130.  
  1131. Time Generated: 04/22/2019 21:56:31
  1132.  
  1133. Event String:
  1134.  
  1135. The DFS Replication service encountered an error communicating with partner WPDC01 for replication group Domain System Volume.
  1136.  
  1137.  
  1138.  
  1139. Partner DNS address: srdc01.test.com
  1140.  
  1141.  
  1142.  
  1143. Optional data if available:
  1144.  
  1145. Partner WINS Address: srdc01
  1146.  
  1147. Partner IP Address: 10.200.60.11
  1148.  
  1149.  
  1150.  
  1151. The service will retry the connection periodically.
  1152.  
  1153.  
  1154.  
  1155. Additional Information:
  1156.  
  1157. Error: 1753 (There are no more endpoints available from the endpoint mapper.)
  1158.  
  1159. Connection ID: 2B275E6F-1EDE-4F5A-929A-492BA6ECD70B
  1160.  
  1161. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  1162.  
  1163. An error event occurred. EventID: 0xC0001204
  1164.  
  1165. Time Generated: 04/22/2019 21:56:31
  1166.  
  1167. Event String:
  1168.  
  1169. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner srdc01.test.com. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  1170.  
  1171.  
  1172.  
  1173. Additional Information:
  1174.  
  1175. Replicated Folder Name: SYSVOL Share
  1176.  
  1177. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  1178.  
  1179. Replication Group Name: Domain System Volume
  1180.  
  1181. Replication Group ID: 2B275E6F-1EDE-4F5A-929A-492BA6ECD70B
  1182.  
  1183. Member ID: 1A6AB88D-9D62-4369-8322-4681021E5B09
  1184.  
  1185. Read-Only: 0
  1186.  
  1187. A warning event occurred. EventID: 0x80001206
  1188.  
  1189. Time Generated: 04/23/2019 11:00:48
  1190.  
  1191. Event String:
  1192.  
  1193. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner . If the server was in the process of being promoted to a domain controller, the domain controller will not advertize and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the synchronization partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  1194.  
  1195.  
  1196.  
  1197. Additional Information:
  1198.  
  1199. Replicated Folder Name: SYSVOL Share
  1200.  
  1201. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  1202.  
  1203. Replication Group Name: Domain System Volume
  1204.  
  1205. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  1206.  
  1207. Member ID: 1A6AB88D-9D62-4369-8322-4681021E5B09
  1208.  
  1209. Read-Only: 0
  1210.  
  1211. A warning event occurred. EventID: 0x80001396
  1212.  
  1213. Time Generated: 04/23/2019 11:04:09
  1214.  
  1215. Event String:
  1216.  
  1217. The DFS Replication service is stopping communication with partner WPDC01 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
  1218.  
  1219.  
  1220.  
  1221. Additional Information:
  1222.  
  1223. Error: 9033 (The request was cancelled by a shutdown)
  1224.  
  1225. Connection ID: 2B275E6F-1EDE-4F5A-929A-492BA6ECD70B
  1226.  
  1227. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  1228.  
  1229. An error event occurred. EventID: 0xC000138A
  1230.  
  1231. Time Generated: 04/23/2019 11:04:45
  1232.  
  1233. Event String:
  1234.  
  1235. The DFS Replication service encountered an error communicating with partner WPDC01 for replication group Domain System Volume.
  1236.  
  1237.  
  1238.  
  1239. Partner DNS address: srdc01.test.com
  1240.  
  1241.  
  1242.  
  1243. Optional data if available:
  1244.  
  1245. Partner WINS Address: srdc01
  1246.  
  1247. Partner IP Address: 10.200.60.11
  1248.  
  1249.  
  1250.  
  1251. The service will retry the connection periodically.
  1252.  
  1253.  
  1254.  
  1255. Additional Information:
  1256.  
  1257. Error: 1753 (There are no more endpoints available from the endpoint mapper.)
  1258.  
  1259. Connection ID: 2B275E6F-1EDE-4F5A-929A-492BA6ECD70B
  1260.  
  1261. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  1262.  
  1263. An error event occurred. EventID: 0xC0001204
  1264.  
  1265. Time Generated: 04/23/2019 11:04:45
  1266.  
  1267. Event String:
  1268.  
  1269. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner srdc01.test.com. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  1270.  
  1271.  
  1272.  
  1273. Additional Information:
  1274.  
  1275. Replicated Folder Name: SYSVOL Share
  1276.  
  1277. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  1278.  
  1279. Replication Group Name: Domain System Volume
  1280.  
  1281. Replication Group ID: 2B275E6F-1EDE-4F5A-929A-492BA6ECD70B
  1282.  
  1283. Member ID: 1A6AB88D-9D62-4369-8322-4681021E5B09
  1284.  
  1285. Read-Only: 0
  1286.  
  1287. An error event occurred. EventID: 0xC00004B2
  1288.  
  1289. Time Generated: 04/23/2019 12:54:33
  1290.  
  1291. Event String:
  1292.  
  1293. 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.
  1294.  
  1295.  
  1296.  
  1297. Additional Information:
  1298.  
  1299. Error: 160 (One or more arguments are not correct.)
  1300.  
  1301. A warning event occurred. EventID: 0x80001206
  1302.  
  1303. Time Generated: 04/23/2019 13:48:07
  1304.  
  1305. Event String:
  1306.  
  1307. The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner . If the server was in the process of being promoted to a domain controller, the domain controller will not advertize and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the synchronization partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
  1308.  
  1309.  
  1310.  
  1311. Additional Information:
  1312.  
  1313. Replicated Folder Name: SYSVOL Share
  1314.  
  1315. Replicated Folder ID: 88E20407-9DD2-4133-8D69-4C098E37247B
  1316.  
  1317. Replication Group Name: Domain System Volume
  1318.  
  1319. Replication Group ID: B43BC5D6-93F0-45E9-9E30-0D559A1E1628
  1320.  
  1321. Member ID: 1A6AB88D-9D62-4369-8322-4681021E5B09
  1322.  
  1323. Read-Only: 0
  1324.  
  1325. ......................... WPCALDC02 failed test DFSREvent
  1326.  
  1327. Starting test: SysVolCheck
  1328.  
  1329. * The File Replication Service SYSVOL ready test
  1330. File Replication Service's SYSVOL is ready
  1331. ......................... WPCALDC02 passed test SysVolCheck
  1332.  
  1333. Starting test: FrsSysVol
  1334.  
  1335. * The File Replication Service SYSVOL ready test
  1336. File Replication Service's SYSVOL is ready
  1337. ......................... WPCALDC02 passed test FrsSysVol
  1338.  
  1339. Starting test: KccEvent
  1340.  
  1341. * The KCC Event log test
  1342. Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
  1343. ......................... WPCALDC02 passed test KccEvent
  1344.  
  1345. Starting test: KnowsOfRoleHolders
  1346.  
  1347. Role Schema Owner = CN=NTDS Settings,CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  1348. Role Domain Owner = CN=NTDS Settings,CN=WPDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  1349. Role PDC Owner = CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  1350. Role Rid Owner = CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  1351. Role Infrastructure Update Owner = CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  1352. ......................... WPCALDC02 passed test KnowsOfRoleHolders
  1353.  
  1354. Starting test: MachineAccount
  1355.  
  1356. Checking machine account for DC WPCALDC02 on DC WPCALDC02.
  1357. * SPN found :LDAP/WPCALDC02.test.com/test.com
  1358. * SPN found :LDAP/WPCALDC02.test.com
  1359. * SPN found :LDAP/WPCALDC02
  1360. * SPN found :LDAP/WPCALDC02.test.com/WPNINC
  1361. * SPN found :LDAP/bb16129b-d7b7-4a76-9382-fbedf83d100c._msdcs.test.com
  1362. * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/bb16129b-d7b7-4a76-9382-fbedf83d100c/test.com
  1363. * SPN found :HOST/WPCALDC02.test.com/test.com
  1364. * SPN found :HOST/WPCALDC02.test.com
  1365. * SPN found :HOST/WPCALDC02
  1366. * SPN found :HOST/WPCALDC02.test.com/WPNINC
  1367. * SPN found :GC/WPCALDC02.test.com/test.com
  1368. ......................... WPCALDC02 passed test MachineAccount
  1369.  
  1370. Starting test: NCSecDesc
  1371.  
  1372. * Security Permissions check for all NC's on DC WPCALDC02.
  1373. * Security Permissions Check for
  1374.  
  1375. DC=ForestDnsZones,DC=test,DC=com
  1376. (NDNC,Version 3)
  1377. * Security Permissions Check for
  1378.  
  1379. DC=DomainDnsZones,DC=test,DC=com
  1380. (NDNC,Version 3)
  1381. * Security Permissions Check for
  1382.  
  1383. CN=Schema,CN=Configuration,DC=test,DC=com
  1384. (Schema,Version 3)
  1385. * Security Permissions Check for
  1386.  
  1387. CN=Configuration,DC=test,DC=com
  1388. (Configuration,Version 3)
  1389. * Security Permissions Check for
  1390.  
  1391. DC=test,DC=com
  1392. (Domain,Version 3)
  1393. ......................... WPCALDC02 passed test NCSecDesc
  1394.  
  1395. Starting test: NetLogons
  1396.  
  1397. * Network Logons Privileges Check
  1398. Verified share \\WPCALDC02\netlogon
  1399. Verified share \\WPCALDC02\sysvol
  1400. ......................... WPCALDC02 passed test NetLogons
  1401.  
  1402. Starting test: ObjectsReplicated
  1403.  
  1404. WPCALDC02 is in domain DC=test,DC=com
  1405. Checking for CN=WPCALDC02,OU=Domain Controllers,DC=test,DC=com in domain DC=test,DC=com on 2 servers
  1406. Object is up-to-date on all servers.
  1407. Checking for CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com in domain CN=Configuration,DC=test,DC=com on 2 servers
  1408. Object is up-to-date on all servers.
  1409. ......................... WPCALDC02 passed test ObjectsReplicated
  1410.  
  1411. Starting test: OutboundSecureChannels
  1412.  
  1413. * The Outbound Secure Channels test
  1414. ** Did not run Outbound Secure Channels test because /testdomain: was
  1415.  
  1416. not entered
  1417.  
  1418. ......................... WPCALDC02 passed test OutboundSecureChannels
  1419.  
  1420. Starting test: Replications
  1421.  
  1422. * Replications Check
  1423. DC=ForestDnsZones,DC=test,DC=com has 16 cursors.
  1424. DC=DomainDnsZones,DC=test,DC=com has 16 cursors.
  1425. CN=Schema,CN=Configuration,DC=test,DC=com has 16 cursors.
  1426. CN=Configuration,DC=test,DC=com has 17 cursors.
  1427. DC=test,DC=com has 17 cursors.
  1428. * Replication Latency Check
  1429. DC=ForestDnsZones,DC=test,DC=com
  1430. Latency information for 14 entries in the vector were ignored.
  1431. 14 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).
  1432. DC=DomainDnsZones,DC=test,DC=com
  1433. Latency information for 14 entries in the vector were ignored.
  1434. 14 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).
  1435. CN=Schema,CN=Configuration,DC=test,DC=com
  1436. Latency information for 14 entries in the vector were ignored.
  1437. 14 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).
  1438. CN=Configuration,DC=test,DC=com
  1439. Latency information for 15 entries in the vector were ignored.
  1440. 15 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
  1441. DC=test,DC=com
  1442. Latency information for 15 entries in the vector were ignored.
  1443. 15 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
  1444. ......................... WPCALDC02 passed test Replications
  1445.  
  1446. Starting test: RidManager
  1447.  
  1448. ridManagerReference = CN=RID Manager$,CN=System,DC=test,DC=com
  1449. * Available RID Pool for the Domain is 20600 to 1073741823
  1450. fSMORoleOwner = CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  1451. * WPCALDC02.test.com is the RID Master
  1452. * DsBind with RID Master was successful
  1453. rIDSetReferences = CN=RID Set,CN=WPCALDC02,OU=Domain Controllers,DC=test,DC=com
  1454. * rIDAllocationPool is 20100 to 20599
  1455. * rIDPreviousAllocationPool is 20100 to 20599
  1456. * rIDNextRID: 20100
  1457. ......................... WPCALDC02 passed test RidManager
  1458.  
  1459. Starting test: Services
  1460.  
  1461. * Checking Service: EventSystem
  1462. * Checking Service: RpcSs
  1463. * Checking Service: NTDS
  1464. * Checking Service: DnsCache
  1465. * Checking Service: DFSR
  1466. * Checking Service: IsmServ
  1467. * Checking Service: kdc
  1468. * Checking Service: SamSs
  1469. * Checking Service: LanmanServer
  1470. * Checking Service: LanmanWorkstation
  1471. * Checking Service: w32time
  1472. * Checking Service: NETLOGON
  1473. ......................... WPCALDC02 passed test Services
  1474.  
  1475. Starting test: SystemLog
  1476.  
  1477. * The System Event log test
  1478. A warning event occurred. EventID: 0x000727A5
  1479.  
  1480. Time Generated: 04/23/2019 14:01:31
  1481.  
  1482. Event String:
  1483.  
  1484. The WinRM service is not listening for WS-Management requests.
  1485.  
  1486.  
  1487.  
  1488. User Action
  1489.  
  1490. If you did not intentionally stop the service, use the following command to see the WinRM configuration:
  1491.  
  1492.  
  1493.  
  1494. winrm enumerate winrm/config/listener
  1495.  
  1496. A warning event occurred. EventID: 0x800009CF
  1497.  
  1498. Time Generated: 04/23/2019 14:02:32
  1499.  
  1500. Event String:
  1501.  
  1502. The server service was unable to recreate the share UserHome because the directory D:\UserHomeDirectory no longer exists. Please run "net share UserHome /delete" to delete the share, or recreate the directory D:\UserHomeDirectory.
  1503.  
  1504. A warning event occurred. EventID: 0x800009CF
  1505.  
  1506. Time Generated: 04/23/2019 14:02:32
  1507.  
  1508. Event String:
  1509.  
  1510. The server service was unable to recreate the share btlbackup because the directory C:\srv\btlbackup no longer exists. Please run "net share btlbackup /delete" to delete the share, or recreate the directory C:\srv\btlbackup.
  1511.  
  1512. A warning event occurred. EventID: 0x00001796
  1513.  
  1514. Time Generated: 04/23/2019 14:02:38
  1515.  
  1516. Event String:
  1517.  
  1518. Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.
  1519.  
  1520.  
  1521.  
  1522. NTLM is a weaker authentication mechanism. Please check:
  1523.  
  1524.  
  1525.  
  1526. Which applications are using NTLM authentication?
  1527.  
  1528. Are there configuration issues preventing the use of stronger authentication such as Kerberos authentication?
  1529.  
  1530. If NTLM must be supported, is Extended Protection configured?
  1531.  
  1532.  
  1533.  
  1534. Details on how to complete these checks can be found at http://go.microsoft.com/fwlink/?LinkId=225699.
  1535.  
  1536. A warning event occurred. EventID: 0x00002724
  1537.  
  1538. Time Generated: 04/23/2019 14:02:54
  1539.  
  1540. Event String:
  1541.  
  1542. This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses.
  1543.  
  1544. A warning event occurred. EventID: 0x00001696
  1545.  
  1546. Time Generated: 04/23/2019 14:03:01
  1547.  
  1548. Event String:
  1549.  
  1550. Dynamic registration or deregistration of one or more DNS records failed with the following error:
  1551.  
  1552. No DNS servers configured for local system.
  1553.  
  1554. A warning event occurred. EventID: 0x0000A000
  1555.  
  1556. Time Generated: 04/23/2019 14:03:02
  1557.  
  1558. Event String:
  1559.  
  1560. The Security System detected an authentication error for the server ldap/srdc01.test.com. The failure code from authentication protocol Kerberos was "An attempt was made to logon, but the netlogon service was not started.
  1561.  
  1562. (0xc0000192)".
  1563.  
  1564. An error event occurred. EventID: 0x000727AB
  1565.  
  1566. Time Generated: 04/23/2019 14:03:23
  1567.  
  1568. Event String:
  1569.  
  1570. The WSMan service failed to read configuration of the following plugin:
  1571.  
  1572. Microsoft.ServerManager.
  1573.  
  1574.  
  1575.  
  1576. The error received was -2144108144: %%-2144108144
  1577.  
  1578. The WS-Management service cannot process the request. Configuration for plugin: "Microsoft.ServerManager" is corrupted. This plugin needs to be reconfigured or deleted. Use the following command to delete a plugin configuration
  1579.  
  1580.  
  1581.  
  1582. winrm delete http://schemas.microsoft.com/wbem/wsman/1/config/plugin?Name=xyz
  1583.  
  1584.  
  1585.  
  1586. Or use the following command to restore default plugin configuration. Note that all external plugins will be unregistered during this restore operation.
  1587.  
  1588.  
  1589.  
  1590. winrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config/plugin @{}.
  1591.  
  1592.  
  1593.  
  1594. User Action
  1595.  
  1596. Make sure this plugin configuration is valid.
  1597.  
  1598. A warning event occurred. EventID: 0x000727AA
  1599.  
  1600. Time Generated: 04/23/2019 14:03:23
  1601.  
  1602. Event String:
  1603.  
  1604. The WinRM service failed to create the following SPNs: WSMAN/WPCALDC02.test.com; WSMAN/WPCALDC02.
  1605.  
  1606.  
  1607.  
  1608. Additional Data
  1609.  
  1610. The error received was 8344: %%8344.
  1611.  
  1612.  
  1613.  
  1614. User Action
  1615.  
  1616. The SPNs can be created by an administrator using setspn.exe utility.
  1617.  
  1618. An error event occurred. EventID: 0xC00110F1
  1619.  
  1620. Time Generated: 04/23/2019 14:03:23
  1621.  
  1622. Event String:
  1623.  
  1624. The WINS Server could not initialize security to allow the read-only operations.
  1625.  
  1626. A warning event occurred. EventID: 0x800038C6
  1627.  
  1628. Time Generated: 04/23/2019 14:03:27
  1629.  
  1630. Event String:
  1631.  
  1632. DFS Root UserHome failed during initialization. The root will not be available.
  1633.  
  1634. A warning event occurred. EventID: 0x800038D9
  1635.  
  1636. Time Generated: 04/23/2019 14:03:27
  1637.  
  1638. Event String:
  1639.  
  1640. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1641.  
  1642. An error event occurred. EventID: 0x0000106A
  1643.  
  1644. Time Generated: 04/23/2019 14:03:28
  1645.  
  1646. Event String:
  1647.  
  1648. Unable to update the IP address on Isatap interface isatap.{05DB7FB2-9AA3-49BA-9415-7F0E71ADBEBC}. Update Type: 1. Error Code: 0x490.
  1649.  
  1650. A warning event occurred. EventID: 0x000000DB
  1651.  
  1652. Time Generated: 04/23/2019 14:03:38
  1653.  
  1654. Event String:
  1655.  
  1656. The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{2b232958-51db-11e9-8114-806e6f6e6963}#000000E916700000.
  1657.  
  1658. A warning event occurred. EventID: 0x800038D9
  1659.  
  1660. Time Generated: 04/23/2019 14:03:42
  1661.  
  1662. Event String:
  1663.  
  1664. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1665.  
  1666. An error event occurred. EventID: 0x0000090A
  1667.  
  1668. Time Generated: 04/23/2019 14:03:42
  1669.  
  1670. Event String:
  1671.  
  1672. Severity: Critical, Category: Storage, MessageID: STOR0209, Message: Unable to monitor or manage SAS components because the initialization sequence of the devices did not complete.
  1673.  
  1674. A warning event occurred. EventID: 0x800038D9
  1675.  
  1676. Time Generated: 04/23/2019 14:04:13
  1677.  
  1678. Event String:
  1679.  
  1680. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1681.  
  1682. A warning event occurred. EventID: 0x800038D9
  1683.  
  1684. Time Generated: 04/23/2019 14:05:13
  1685.  
  1686. Event String:
  1687.  
  1688. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1689.  
  1690. A warning event occurred. EventID: 0x800038D9
  1691.  
  1692. Time Generated: 04/23/2019 14:07:13
  1693.  
  1694. Event String:
  1695.  
  1696. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1697.  
  1698. A warning event occurred. EventID: 0x800038D9
  1699.  
  1700. Time Generated: 04/23/2019 14:11:13
  1701.  
  1702. Event String:
  1703.  
  1704. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1705.  
  1706. A warning event occurred. EventID: 0x0000053C
  1707.  
  1708. Time Generated: 04/23/2019 14:44:50
  1709.  
  1710. Event String:
  1711.  
  1712. The DNS registration for DHCPv4 Client IP address 192.168.4.53 , FQDN w-0516.test.com and DHCID AAEBCBPiJRidbOcg8dG7lP+ION5y11Z4KvfzOdjVc6mSPmQ= has been denied as there is probably an existing client with same FQDN already registered with DNS.
  1713.  
  1714. A warning event occurred. EventID: 0x0000053C
  1715.  
  1716. Time Generated: 04/23/2019 14:54:21
  1717.  
  1718. Event String:
  1719.  
  1720. The DNS registration for DHCPv4 Client IP address 192.168.4.60 , FQDN w-0526.test.com and DHCID AAEB0q/9BQODLb/JfGaj/8t0kCNswHST/e6SNTdnZEK3XE4= has been denied as there is probably an existing client with same FQDN already registered with DNS.
  1721.  
  1722. A warning event occurred. EventID: 0x0000053C
  1723.  
  1724. Time Generated: 04/23/2019 14:56:52
  1725.  
  1726. Event String:
  1727.  
  1728. The DNS registration for DHCPv4 Client IP address 192.168.4.57 , FQDN W-0266.test.com and DHCID AAEBEgq9N+BcWbgTctZYvZv1+sjqGRwRYFHl81rNHbI7BLw= has been denied as there is probably an existing client with same FQDN already registered with DNS.
  1729.  
  1730. A warning event occurred. EventID: 0x800038D9
  1731.  
  1732. Time Generated: 04/23/2019 14:57:14
  1733.  
  1734. Event String:
  1735.  
  1736. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1737.  
  1738. A warning event occurred. EventID: 0x800038D9
  1739.  
  1740. Time Generated: 04/23/2019 14:57:14
  1741.  
  1742. Event String:
  1743.  
  1744. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1745.  
  1746. A warning event occurred. EventID: 0x800038D9
  1747.  
  1748. Time Generated: 04/23/2019 14:57:14
  1749.  
  1750. Event String:
  1751.  
  1752. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1753.  
  1754. A warning event occurred. EventID: 0x800038D9
  1755.  
  1756. Time Generated: 04/23/2019 14:57:15
  1757.  
  1758. Event String:
  1759.  
  1760. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1761.  
  1762. A warning event occurred. EventID: 0x800038D9
  1763.  
  1764. Time Generated: 04/23/2019 14:57:15
  1765.  
  1766. Event String:
  1767.  
  1768. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1769.  
  1770. A warning event occurred. EventID: 0x800038D9
  1771.  
  1772. Time Generated: 04/23/2019 14:57:15
  1773.  
  1774. Event String:
  1775.  
  1776. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1777.  
  1778. A warning event occurred. EventID: 0x800038D9
  1779.  
  1780. Time Generated: 04/23/2019 14:57:15
  1781.  
  1782. Event String:
  1783.  
  1784. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1785.  
  1786. A warning event occurred. EventID: 0x800038D9
  1787.  
  1788. Time Generated: 04/23/2019 14:57:15
  1789.  
  1790. Event String:
  1791.  
  1792. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1793.  
  1794. A warning event occurred. EventID: 0x800038D9
  1795.  
  1796. Time Generated: 04/23/2019 14:57:15
  1797.  
  1798. Event String:
  1799.  
  1800. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1801.  
  1802. A warning event occurred. EventID: 0x800038D9
  1803.  
  1804. Time Generated: 04/23/2019 14:57:16
  1805.  
  1806. Event String:
  1807.  
  1808. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1809.  
  1810. A warning event occurred. EventID: 0x800038D9
  1811.  
  1812. Time Generated: 04/23/2019 14:57:16
  1813.  
  1814. Event String:
  1815.  
  1816. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1817.  
  1818. A warning event occurred. EventID: 0x800038D9
  1819.  
  1820. Time Generated: 04/23/2019 14:57:16
  1821.  
  1822. Event String:
  1823.  
  1824. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1825.  
  1826. A warning event occurred. EventID: 0x800038D9
  1827.  
  1828. Time Generated: 04/23/2019 14:57:16
  1829.  
  1830. Event String:
  1831.  
  1832. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1833.  
  1834. A warning event occurred. EventID: 0x800038D9
  1835.  
  1836. Time Generated: 04/23/2019 14:57:16
  1837.  
  1838. Event String:
  1839.  
  1840. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1841.  
  1842. A warning event occurred. EventID: 0x800038D9
  1843.  
  1844. Time Generated: 04/23/2019 14:57:16
  1845.  
  1846. Event String:
  1847.  
  1848. The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: UserHome
  1849.  
  1850. ......................... WPCALDC02 failed test SystemLog
  1851.  
  1852. Starting test: Topology
  1853.  
  1854. * Configuration Topology Integrity Check
  1855. * Analyzing the connection topology for DC=ForestDnsZones,DC=test,DC=com.
  1856. * Performing upstream (of target) analysis.
  1857. * Performing downstream (of target) analysis.
  1858. * Analyzing the connection topology for DC=DomainDnsZones,DC=test,DC=com.
  1859. * Performing upstream (of target) analysis.
  1860. * Performing downstream (of target) analysis.
  1861. * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=test,DC=com.
  1862. * Performing upstream (of target) analysis.
  1863. * Performing downstream (of target) analysis.
  1864. * Analyzing the connection topology for CN=Configuration,DC=test,DC=com.
  1865. * Performing upstream (of target) analysis.
  1866. * Performing downstream (of target) analysis.
  1867. * Analyzing the connection topology for DC=test,DC=com.
  1868. * Performing upstream (of target) analysis.
  1869. * Performing downstream (of target) analysis.
  1870. ......................... WPCALDC02 passed test Topology
  1871.  
  1872. Starting test: VerifyEnterpriseReferences
  1873.  
  1874. ......................... WPCALDC02 passed test
  1875.  
  1876. VerifyEnterpriseReferences
  1877.  
  1878. Starting test: VerifyReferences
  1879.  
  1880. The system object reference (serverReference)
  1881.  
  1882. CN=WPCALDC02,OU=Domain Controllers,DC=test,DC=com and backlink on
  1883.  
  1884. CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  1885.  
  1886. are correct.
  1887. The system object reference (serverReferenceBL)
  1888.  
  1889. CN=WPCALDC02,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=test,DC=com
  1890.  
  1891. and backlink on
  1892.  
  1893. CN=NTDS Settings,CN=WPCALDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=test,DC=com
  1894.  
  1895. are correct.
  1896. The system object reference (msDFSR-ComputerReferenceBL)
  1897.  
  1898. CN=WPCALDC02,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=test,DC=com
  1899.  
  1900. and backlink on CN=WPCALDC02,OU=Domain Controllers,DC=test,DC=com
  1901.  
  1902. are correct.
  1903. ......................... WPCALDC02 passed test VerifyReferences
  1904.  
  1905. Starting test: VerifyReplicas
  1906.  
  1907. ......................... WPCALDC02 passed test VerifyReplicas
  1908.  
  1909.  
  1910. Starting test: DNS
  1911.  
  1912.  
  1913. Starting test: DNS
  1914.  
  1915.  
  1916.  
  1917. DNS Tests are running and not hung. Please wait a few
  1918.  
  1919. minutes...
  1920.  
  1921. See DNS test in enterprise tests section for results
  1922. ......................... WPCALDC02 passed test DNS
  1923.  
  1924. See DNS test in enterprise tests section for results
  1925. ......................... WPDC01 passed test DNS
  1926.  
  1927.  
  1928. Running partition tests on : ForestDnsZones
  1929.  
  1930. Starting test: CheckSDRefDom
  1931.  
  1932. ......................... ForestDnsZones passed test CheckSDRefDom
  1933.  
  1934. Starting test: CrossRefValidation
  1935.  
  1936. ......................... ForestDnsZones passed test
  1937.  
  1938. CrossRefValidation
  1939.  
  1940.  
  1941. Running partition tests on : DomainDnsZones
  1942.  
  1943. Starting test: CheckSDRefDom
  1944.  
  1945. ......................... DomainDnsZones passed test CheckSDRefDom
  1946.  
  1947. Starting test: CrossRefValidation
  1948.  
  1949. ......................... DomainDnsZones passed test
  1950.  
  1951. CrossRefValidation
  1952.  
  1953.  
  1954. Running partition tests on : Schema
  1955.  
  1956. Starting test: CheckSDRefDom
  1957.  
  1958. ......................... Schema passed test CheckSDRefDom
  1959.  
  1960. Starting test: CrossRefValidation
  1961.  
  1962. ......................... Schema passed test CrossRefValidation
  1963.  
  1964.  
  1965. Running partition tests on : Configuration
  1966.  
  1967. Starting test: CheckSDRefDom
  1968.  
  1969. ......................... Configuration passed test CheckSDRefDom
  1970.  
  1971. Starting test: CrossRefValidation
  1972.  
  1973. ......................... Configuration passed test CrossRefValidation
  1974.  
  1975.  
  1976. Running partition tests on : test
  1977.  
  1978. Starting test: CheckSDRefDom
  1979.  
  1980. ......................... test passed test CheckSDRefDom
  1981.  
  1982. Starting test: CrossRefValidation
  1983.  
  1984. ......................... test passed test CrossRefValidation
  1985.  
  1986.  
  1987. Running enterprise tests on : test.com
  1988.  
  1989. Starting test: DNS
  1990.  
  1991. Test results for domain controllers:
  1992.  
  1993.  
  1994. DC: srdc01.test.com
  1995.  
  1996. Domain: test.com
  1997.  
  1998.  
  1999.  
  2000.  
  2001. TEST: Authentication (Auth)
  2002. Authentication test: Successfully completed
  2003.  
  2004. TEST: Basic (Basc)
  2005. The OS
  2006.  
  2007. Microsoft Windows Server 2012 R2 Standard (Service Pack level: 0.0)
  2008.  
  2009. is supported.
  2010.  
  2011. NETLOGON service is running
  2012.  
  2013. kdc service is running
  2014.  
  2015. DNSCACHE service is running
  2016.  
  2017. DNS service is running
  2018.  
  2019. DC is a DNS server
  2020.  
  2021. Network adapters information:
  2022.  
  2023. Adapter
  2024.  
  2025. [00000009] Intel(R) 82574L Gigabit Network Connection:
  2026.  
  2027. MAC address is 00:0C:29:C5:B2:BF
  2028. IP Address is static
  2029. IP address: 10.200.60.11
  2030. DNS servers:
  2031.  
  2032. 10.200.60.12 (srcaldc02.test.com.) [Valid]
  2033. 127.0.0.1 (WPDC01) [Valid]
  2034. The A host record(s) for this DC was found
  2035. The SOA record for the Active Directory zone was found
  2036. The Active Directory zone on this DC/DNS server was found primary
  2037. Root zone on this DC/DNS server was not found
  2038.  
  2039. TEST: Forwarders/Root hints (Forw)
  2040. Recursion is enabled
  2041. Forwarders Information:
  2042. 208.67.222.222 (<name unavailable>) [Valid]
  2043. 8.8.4.4 (<name unavailable>) [Valid]
  2044. 8.8.8.8 (<name unavailable>) [Valid]
  2045.  
  2046. TEST: Delegations (Del)
  2047. Delegation information for the zone: test.com.
  2048. Delegated domain name: _msdcs.test.com.
  2049. DNS server: srcaldc02.test.com. IP:10.200.60.12 [Valid]
  2050.  
  2051. TEST: Dynamic update (Dyn)
  2052. Test record dcdiag-test-record added successfully in zone test.com
  2053. Warning: Failed to delete the test record dcdiag-test-record in zone test.com
  2054. [Error details: 9505 (Type: Win32 - Description: Unsecured DNS packet.)]
  2055.  
  2056. TEST: Records registration (RReg)
  2057. Network Adapter
  2058.  
  2059. [00000009] Intel(R) 82574L Gigabit Network Connection:
  2060.  
  2061. Matching CNAME record found at DNS server 10.200.60.12:
  2062. 2cbeed59-4eca-4f48-af71-640b5c843801._msdcs.test.com
  2063.  
  2064. Matching A record found at DNS server 10.200.60.12:
  2065. srdc01.test.com
  2066.  
  2067. Matching SRV record found at DNS server 10.200.60.12:
  2068. _ldap._tcp.test.com
  2069.  
  2070. Matching SRV record found at DNS server 10.200.60.12:
  2071. _ldap._tcp.b6c20ebf-1ea3-4e06-85e0-f15bb0ecf94a.domains._msdcs.test.com
  2072.  
  2073. Matching SRV record found at DNS server 10.200.60.12:
  2074. _kerberos._tcp.dc._msdcs.test.com
  2075.  
  2076. Matching SRV record found at DNS server 10.200.60.12:
  2077. _ldap._tcp.dc._msdcs.test.com
  2078.  
  2079. Matching SRV record found at DNS server 10.200.60.12:
  2080. _kerberos._tcp.test.com
  2081.  
  2082. Matching SRV record found at DNS server 10.200.60.12:
  2083. _kerberos._udp.test.com
  2084.  
  2085. Matching SRV record found at DNS server 10.200.60.12:
  2086. _kpasswd._tcp.test.com
  2087.  
  2088. Matching SRV record found at DNS server 10.200.60.12:
  2089. _ldap._tcp.Default-First-Site-Name._sites.test.com
  2090.  
  2091. Matching SRV record found at DNS server 10.200.60.12:
  2092. _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.test.com
  2093.  
  2094. Matching SRV record found at DNS server 10.200.60.12:
  2095. _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.test.com
  2096.  
  2097. Matching SRV record found at DNS server 10.200.60.12:
  2098. _kerberos._tcp.Default-First-Site-Name._sites.test.com
  2099.  
  2100. Matching SRV record found at DNS server 10.200.60.12:
  2101. _ldap._tcp.gc._msdcs.test.com
  2102.  
  2103. Matching A record found at DNS server 10.200.60.12:
  2104. gc._msdcs.test.com
  2105.  
  2106. Matching SRV record found at DNS server 10.200.60.12:
  2107. _gc._tcp.Default-First-Site-Name._sites.test.com
  2108.  
  2109. Matching SRV record found at DNS server 10.200.60.12:
  2110. _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.test.com
  2111.  
  2112. Matching CNAME record found at DNS server 10.200.60.11:
  2113. 2cbeed59-4eca-4f48-af71-640b5c843801._msdcs.test.com
  2114.  
  2115. Matching A record found at DNS server 10.200.60.11:
  2116. srdc01.test.com
  2117.  
  2118. Matching SRV record found at DNS server 10.200.60.11:
  2119. _ldap._tcp.test.com
  2120.  
  2121. Matching SRV record found at DNS server 10.200.60.11:
  2122. _ldap._tcp.b6c20ebf-1ea3-4e06-85e0-f15bb0ecf94a.domains._msdcs.test.com
  2123.  
  2124. Matching SRV record found at DNS server 10.200.60.11:
  2125. _kerberos._tcp.dc._msdcs.test.com
  2126.  
  2127. Matching SRV record found at DNS server 10.200.60.11:
  2128. _ldap._tcp.dc._msdcs.test.com
  2129.  
  2130. Matching SRV record found at DNS server 10.200.60.11:
  2131. _kerberos._tcp.test.com
  2132.  
  2133. Matching SRV record found at DNS server 10.200.60.11:
  2134. _kerberos._udp.test.com
  2135.  
  2136. Matching SRV record found at DNS server 10.200.60.11:
  2137. _kpasswd._tcp.test.com
  2138.  
  2139. Matching SRV record found at DNS server 10.200.60.11:
  2140. _ldap._tcp.Default-First-Site-Name._sites.test.com
  2141.  
  2142. Matching SRV record found at DNS server 10.200.60.11:
  2143. _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.test.com
  2144.  
  2145. Matching SRV record found at DNS server 10.200.60.11:
  2146. _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.test.com
  2147.  
  2148. Matching SRV record found at DNS server 10.200.60.11:
  2149. _kerberos._tcp.Default-First-Site-Name._sites.test.com
  2150.  
  2151. Matching SRV record found at DNS server 10.200.60.11:
  2152. _ldap._tcp.gc._msdcs.test.com
  2153.  
  2154. Matching A record found at DNS server 10.200.60.11:
  2155. gc._msdcs.test.com
  2156.  
  2157. Matching SRV record found at DNS server 10.200.60.11:
  2158. _gc._tcp.Default-First-Site-Name._sites.test.com
  2159.  
  2160. Matching SRV record found at DNS server 10.200.60.11:
  2161. _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.test.com
  2162.  
  2163. Total query time:0 min. 0 sec.. Total RPC connection
  2164.  
  2165. time:0 min. 0 sec.
  2166.  
  2167. Total WMI connection time:0 min. 42 sec. Total Netuse connection
  2168.  
  2169. time:0 min. 0 sec.
  2170.  
  2171.  
  2172.  
  2173. DC: WPCALDC02.test.com
  2174.  
  2175. Domain: test.com
  2176.  
  2177.  
  2178.  
  2179.  
  2180. TEST: Authentication (Auth)
  2181. Authentication test: Successfully completed
  2182.  
  2183. TEST: Basic (Basc)
  2184. The OS
  2185.  
  2186. Microsoft Windows Server 2012 R2 Standard (Service Pack level: 0.0)
  2187.  
  2188. is supported.
  2189.  
  2190. NETLOGON service is running
  2191.  
  2192. kdc service is running
  2193.  
  2194. DNSCACHE service is running
  2195.  
  2196. DNS service is running
  2197.  
  2198. DC is a DNS server
  2199.  
  2200. Network adapters information:
  2201.  
  2202. Adapter [00000012] vmxnet3 Ethernet Adapter:
  2203.  
  2204. MAC address is 00:0C:29:59:0D:F8
  2205. IP Address is static
  2206. IP address: 10.200.60.12
  2207. DNS servers:
  2208.  
  2209. 10.200.60.11 (WPDC01) [Valid]
  2210. 127.0.0.1 (srcaldc02.test.com.) [Valid]
  2211. The A host record(s) for this DC was found
  2212. The SOA record for the Active Directory zone was found
  2213. The Active Directory zone on this DC/DNS server was found primary
  2214. Root zone on this DC/DNS server was not found
  2215.  
  2216. TEST: Forwarders/Root hints (Forw)
  2217. Recursion is enabled
  2218. Forwarders Information:
  2219. 208.67.222.222 (<name unavailable>) [Valid]
  2220. 8.8.4.4 (<name unavailable>) [Valid]
  2221. 8.8.8.8 (<name unavailable>) [Valid]
  2222.  
  2223. TEST: Delegations (Del)
  2224. Delegation information for the zone: test.com.
  2225. Delegated domain name: _msdcs.test.com.
  2226. DNS server: srcaldc02.test.com. IP:10.200.60.12 [Valid]
  2227.  
  2228. TEST: Dynamic update (Dyn)
  2229. Test record dcdiag-test-record added successfully in zone test.com
  2230. Warning: Failed to delete the test record dcdiag-test-record in zone test.com
  2231. [Error details: 9505 (Type: Win32 - Description: Unsecured DNS packet.)]
  2232.  
  2233. TEST: Records registration (RReg)
  2234. Network Adapter [00000012] vmxnet3 Ethernet Adapter:
  2235.  
  2236. Matching CNAME record found at DNS server 10.200.60.11:
  2237. bb16129b-d7b7-4a76-9382-fbedf83d100c._msdcs.test.com
  2238.  
  2239. Matching A record found at DNS server 10.200.60.11:
  2240. WPCALDC02.test.com
  2241.  
  2242. Matching SRV record found at DNS server 10.200.60.11:
  2243. _ldap._tcp.test.com
  2244.  
  2245. Matching SRV record found at DNS server 10.200.60.11:
  2246. _ldap._tcp.b6c20ebf-1ea3-4e06-85e0-f15bb0ecf94a.domains._msdcs.test.com
  2247.  
  2248. Matching SRV record found at DNS server 10.200.60.11:
  2249. _kerberos._tcp.dc._msdcs.test.com
  2250.  
  2251. Matching SRV record found at DNS server 10.200.60.11:
  2252. _ldap._tcp.dc._msdcs.test.com
  2253.  
  2254. Matching SRV record found at DNS server 10.200.60.11:
  2255. _kerberos._tcp.test.com
  2256.  
  2257. Matching SRV record found at DNS server 10.200.60.11:
  2258. _kerberos._udp.test.com
  2259.  
  2260. Matching SRV record found at DNS server 10.200.60.11:
  2261. _kpasswd._tcp.test.com
  2262.  
  2263. Matching SRV record found at DNS server 10.200.60.11:
  2264. _ldap._tcp.Default-First-Site-Name._sites.test.com
  2265.  
  2266. Matching SRV record found at DNS server 10.200.60.11:
  2267. _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.test.com
  2268.  
  2269. Matching SRV record found at DNS server 10.200.60.11:
  2270. _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.test.com
  2271.  
  2272. Matching SRV record found at DNS server 10.200.60.11:
  2273. _kerberos._tcp.Default-First-Site-Name._sites.test.com
  2274.  
  2275. Matching SRV record found at DNS server 10.200.60.11:
  2276. _ldap._tcp.gc._msdcs.test.com
  2277.  
  2278. Matching A record found at DNS server 10.200.60.11:
  2279. gc._msdcs.test.com
  2280.  
  2281. Matching SRV record found at DNS server 10.200.60.11:
  2282. _gc._tcp.Default-First-Site-Name._sites.test.com
  2283.  
  2284. Matching SRV record found at DNS server 10.200.60.11:
  2285. _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.test.com
  2286.  
  2287. Matching SRV record found at DNS server 10.200.60.11:
  2288. _ldap._tcp.pdc._msdcs.test.com
  2289.  
  2290. Matching CNAME record found at DNS server 10.200.60.12:
  2291. bb16129b-d7b7-4a76-9382-fbedf83d100c._msdcs.test.com
  2292.  
  2293. Matching A record found at DNS server 10.200.60.12:
  2294. WPCALDC02.test.com
  2295.  
  2296. Matching SRV record found at DNS server 10.200.60.12:
  2297. _ldap._tcp.test.com
  2298.  
  2299. Matching SRV record found at DNS server 10.200.60.12:
  2300. _ldap._tcp.b6c20ebf-1ea3-4e06-85e0-f15bb0ecf94a.domains._msdcs.test.com
  2301.  
  2302. Matching SRV record found at DNS server 10.200.60.12:
  2303. _kerberos._tcp.dc._msdcs.test.com
  2304.  
  2305. Matching SRV record found at DNS server 10.200.60.12:
  2306. _ldap._tcp.dc._msdcs.test.com
  2307.  
  2308. Matching SRV record found at DNS server 10.200.60.12:
  2309. _kerberos._tcp.test.com
  2310.  
  2311. Matching SRV record found at DNS server 10.200.60.12:
  2312. _kerberos._udp.test.com
  2313.  
  2314. Matching SRV record found at DNS server 10.200.60.12:
  2315. _kpasswd._tcp.test.com
  2316.  
  2317. Matching SRV record found at DNS server 10.200.60.12:
  2318. _ldap._tcp.Default-First-Site-Name._sites.test.com
  2319.  
  2320. Matching SRV record found at DNS server 10.200.60.12:
  2321. _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.test.com
  2322.  
  2323. Matching SRV record found at DNS server 10.200.60.12:
  2324. _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.test.com
  2325.  
  2326. Matching SRV record found at DNS server 10.200.60.12:
  2327. _kerberos._tcp.Default-First-Site-Name._sites.test.com
  2328.  
  2329. Matching SRV record found at DNS server 10.200.60.12:
  2330. _ldap._tcp.gc._msdcs.test.com
  2331.  
  2332. Matching A record found at DNS server 10.200.60.12:
  2333. gc._msdcs.test.com
  2334.  
  2335. Matching SRV record found at DNS server 10.200.60.12:
  2336. _gc._tcp.Default-First-Site-Name._sites.test.com
  2337.  
  2338. Matching SRV record found at DNS server 10.200.60.12:
  2339. _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.test.com
  2340.  
  2341. Matching SRV record found at DNS server 10.200.60.12:
  2342. _ldap._tcp.pdc._msdcs.test.com
  2343.  
  2344. Total query time:0 min. 0 sec.. Total RPC connection
  2345.  
  2346. time:0 min. 0 sec.
  2347.  
  2348. Total WMI connection time:0 min. 21 sec. Total Netuse connection
  2349.  
  2350. time:0 min. 0 sec.
  2351.  
  2352.  
  2353. Summary of test results for DNS servers used by the above domain
  2354.  
  2355. controllers:
  2356.  
  2357.  
  2358.  
  2359. DNS server: 10.200.60.11 (WPDC01)
  2360.  
  2361. All tests passed on this DNS server
  2362.  
  2363. Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
  2364. Total query time:0 min. 0 sec., Total WMI connection
  2365.  
  2366. time:0 min. 0 sec.
  2367.  
  2368.  
  2369. DNS server: 10.200.60.12 (srcaldc02.test.com.)
  2370.  
  2371. All tests passed on this DNS server
  2372.  
  2373. Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
  2374. DNS delegation for the domain _msdcs.test.com. is operational on IP 10.200.60.12
  2375.  
  2376. Total query time:0 min. 0 sec., Total WMI connection
  2377.  
  2378. time:0 min. 0 sec.
  2379.  
  2380.  
  2381. DNS server: 208.67.222.222 (<name unavailable>)
  2382.  
  2383. All tests passed on this DNS server
  2384.  
  2385. Total query time:0 min. 0 sec., Total WMI connection
  2386.  
  2387. time:0 min. 21 sec.
  2388.  
  2389.  
  2390. DNS server: 8.8.4.4 (<name unavailable>)
  2391.  
  2392. All tests passed on this DNS server
  2393.  
  2394. Total query time:0 min. 0 sec., Total WMI connection
  2395.  
  2396. time:0 min. 21 sec.
  2397.  
  2398.  
  2399. DNS server: 8.8.8.8 (<name unavailable>)
  2400.  
  2401. All tests passed on this DNS server
  2402.  
  2403. Total query time:0 min. 0 sec., Total WMI connection
  2404.  
  2405. time:0 min. 21 sec.
  2406.  
  2407.  
  2408. Summary of DNS test results:
  2409.  
  2410.  
  2411. Auth Basc Forw Del Dyn RReg Ext
  2412. _________________________________________________________________
  2413. Domain: test.com
  2414.  
  2415. srdc01 PASS PASS PASS PASS WARN PASS n/a
  2416. WPCALDC02 PASS PASS PASS PASS WARN PASS n/a
  2417.  
  2418. Total Time taken to test all the DCs:1 min. 3 sec.
  2419.  
  2420. ......................... test.com passed test DNS
  2421.  
  2422. Starting test: LocatorCheck
  2423.  
  2424. GC Name: \\WPCALDC02.test.com
  2425.  
  2426. Locator Flags: 0xe000f3fd
  2427. PDC Name: \\WPCALDC02.test.com
  2428. Locator Flags: 0xe000f3fd
  2429. Time Server Name: \\WPCALDC02.test.com
  2430. Locator Flags: 0xe000f3fd
  2431. Preferred Time Server Name: \\WPCALDC02.test.com
  2432. Locator Flags: 0xe000f3fd
  2433. KDC Name: \\WPCALDC02.test.com
  2434. Locator Flags: 0xe000f3fd
  2435. ......................... test.com passed test LocatorCheck
  2436.  
  2437. Starting test: FsmoCheck
  2438.  
  2439. GC Name: \\WPCALDC02.test.com
  2440.  
  2441. Locator Flags: 0xe000f3fd
  2442. PDC Name: \\WPCALDC02.test.com
  2443. Locator Flags: 0xe000f3fd
  2444. Time Server Name: \\WPCALDC02.test.com
  2445. Locator Flags: 0xe000f3fd
  2446. Preferred Time Server Name: \\WPCALDC02.test.com
  2447. Locator Flags: 0xe000f3fd
  2448. KDC Name: \\WPCALDC02.test.com
  2449. Locator Flags: 0xe000f3fd
  2450. ......................... test.com passed test FsmoCheck
  2451.  
  2452. Starting test: Intersite
  2453.  
  2454. Skipping site Default-First-Site-Name, this site is outside the scope
  2455.  
  2456. provided by the command line arguments provided.
  2457. ......................... .com passed test Intersite
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!