API tools faq
paste
Advertisement
Guest User

H2S3-ADDC2_dcdiag.txt

a guest
Feb 20th, 2015
59
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 65.53 KB | None | 0 0
raw download clone embed print report
  1. Directory Server Diagnosis
  2.  
  3.  
  4. Performing initial setup:
  5.  
  6. Trying to find home server...
  7.  
  8. Home Server = h2s3-addc2
  9.  
  10. * Identified AD Forest.
  11. Done gathering initial info.
  12.  
  13.  
  14. Doing initial required tests
  15.  
  16.  
  17. Testing server: WestChester\DC1
  18.  
  19. Starting test: Connectivity
  20.  
  21. ......................... DC1 passed test Connectivity
  22.  
  23.  
  24. Testing server: WestChester\DC2
  25.  
  26. Starting test: Connectivity
  27.  
  28. ......................... DC2 passed test Connectivity
  29.  
  30.  
  31. Testing server: AtlantaStaging\H2S2-ADDC2
  32.  
  33. Starting test: Connectivity
  34.  
  35. ......................... H2S2-ADDC2 passed test Connectivity
  36.  
  37.  
  38. Testing server: AtlantaH2P\H2P-ADDC1
  39.  
  40. Starting test: Connectivity
  41.  
  42. ......................... H2P-ADDC1 passed test Connectivity
  43.  
  44.  
  45. Testing server: AtlantaH2P\H2P-ADDC2
  46.  
  47. Starting test: Connectivity
  48.  
  49. ......................... H2P-ADDC2 passed test Connectivity
  50.  
  51.  
  52. Testing server: AtlantaH3R\H3R-ADDC1
  53.  
  54. Starting test: Connectivity
  55.  
  56. ......................... H3R-ADDC1 passed test Connectivity
  57.  
  58.  
  59. Testing server: AtlantaH3R\H3R-ADDC2
  60.  
  61. Starting test: Connectivity
  62.  
  63. ......................... H3R-ADDC2 passed test Connectivity
  64.  
  65.  
  66. Testing server: AtlantaStaging\H2S3-ADDC1
  67.  
  68. Starting test: Connectivity
  69.  
  70. ......................... H2S3-ADDC1 passed test Connectivity
  71.  
  72.  
  73. Testing server: AtlantaStaging\H2S3-ADDC2
  74.  
  75. Starting test: Connectivity
  76.  
  77. ......................... H2S3-ADDC2 passed test Connectivity
  78.  
  79.  
  80. Testing server: AtlantaStaging\H2S2-ADDC1
  81.  
  82. Starting test: Connectivity
  83.  
  84. ......................... H2S2-ADDC1 passed test Connectivity
  85.  
  86.  
  87.  
  88. Doing primary tests
  89.  
  90.  
  91. Testing server: WestChester\DC1
  92.  
  93. Starting test: Advertising
  94.  
  95. ......................... DC1 passed test Advertising
  96.  
  97. Starting test: FrsEvent
  98.  
  99. ......................... DC1 passed test FrsEvent
  100.  
  101. Starting test: DFSREvent
  102.  
  103. ......................... DC1 passed test DFSREvent
  104.  
  105. Starting test: SysVolCheck
  106.  
  107. ......................... DC1 passed test SysVolCheck
  108.  
  109. Starting test: KccEvent
  110.  
  111. ......................... DC1 passed test KccEvent
  112.  
  113. Starting test: KnowsOfRoleHolders
  114.  
  115. ......................... DC1 passed test KnowsOfRoleHolders
  116.  
  117. Starting test: MachineAccount
  118.  
  119. ......................... DC1 passed test MachineAccount
  120.  
  121. Starting test: NCSecDesc
  122.  
  123. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  124.  
  125. Replicating Directory Changes In Filtered Set
  126. access rights for the naming context:
  127.  
  128. DC=ForestDnsZones,DC=HOMENET,DC=local
  129. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  130.  
  131. Replicating Directory Changes In Filtered Set
  132. access rights for the naming context:
  133.  
  134. DC=DomainDnsZones,DC=HOMENET,DC=local
  135. ......................... DC1 failed test NCSecDesc
  136.  
  137. Starting test: NetLogons
  138.  
  139. ......................... DC1 passed test NetLogons
  140.  
  141. Starting test: ObjectsReplicated
  142.  
  143. ......................... DC1 passed test ObjectsReplicated
  144.  
  145. Starting test: Replications
  146.  
  147. ......................... DC1 passed test Replications
  148.  
  149. Starting test: RidManager
  150.  
  151. ......................... DC1 passed test RidManager
  152.  
  153. Starting test: Services
  154.  
  155. ......................... DC1 passed test Services
  156.  
  157. Starting test: SystemLog
  158.  
  159. ......................... DC1 passed test SystemLog
  160.  
  161. Starting test: VerifyReferences
  162.  
  163. ......................... DC1 passed test VerifyReferences
  164.  
  165.  
  166. Testing server: WestChester\DC2
  167.  
  168. Starting test: Advertising
  169.  
  170. ......................... DC2 passed test Advertising
  171.  
  172. Starting test: FrsEvent
  173.  
  174. ......................... DC2 passed test FrsEvent
  175.  
  176. Starting test: DFSREvent
  177.  
  178. ......................... DC2 passed test DFSREvent
  179.  
  180. Starting test: SysVolCheck
  181.  
  182. ......................... DC2 passed test SysVolCheck
  183.  
  184. Starting test: KccEvent
  185.  
  186. ......................... DC2 passed test KccEvent
  187.  
  188. Starting test: KnowsOfRoleHolders
  189.  
  190. ......................... DC2 passed test KnowsOfRoleHolders
  191.  
  192. Starting test: MachineAccount
  193.  
  194. ......................... DC2 passed test MachineAccount
  195.  
  196. Starting test: NCSecDesc
  197.  
  198. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  199.  
  200. Replicating Directory Changes In Filtered Set
  201. access rights for the naming context:
  202.  
  203. DC=ForestDnsZones,DC=HOMENET,DC=local
  204. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  205.  
  206. Replicating Directory Changes In Filtered Set
  207. access rights for the naming context:
  208.  
  209. DC=DomainDnsZones,DC=HOMENET,DC=local
  210. ......................... DC2 failed test NCSecDesc
  211.  
  212. Starting test: NetLogons
  213.  
  214. ......................... DC2 passed test NetLogons
  215.  
  216. Starting test: ObjectsReplicated
  217.  
  218. ......................... DC2 passed test ObjectsReplicated
  219.  
  220. Starting test: Replications
  221.  
  222. ......................... DC2 passed test Replications
  223.  
  224. Starting test: RidManager
  225.  
  226. ......................... DC2 passed test RidManager
  227.  
  228. Starting test: Services
  229.  
  230. ......................... DC2 passed test Services
  231.  
  232. Starting test: SystemLog
  233.  
  234. A warning event occurred. EventID: 0x0000043D
  235.  
  236. Time Generated: 02/20/2015 06:51:34
  237.  
  238. Event String:
  239.  
  240. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  241.  
  242. A warning event occurred. EventID: 0x0000043D
  243.  
  244. Time Generated: 02/20/2015 06:51:36
  245.  
  246. Event String:
  247.  
  248. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  249.  
  250. A warning event occurred. EventID: 0x0000043D
  251.  
  252. Time Generated: 02/20/2015 06:51:37
  253.  
  254. Event String:
  255.  
  256. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  257.  
  258. A warning event occurred. EventID: 0x0000043D
  259.  
  260. Time Generated: 02/20/2015 06:56:42
  261.  
  262. Event String:
  263.  
  264. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  265.  
  266. A warning event occurred. EventID: 0x0000043D
  267.  
  268. Time Generated: 02/20/2015 06:56:44
  269.  
  270. Event String:
  271.  
  272. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  273.  
  274. A warning event occurred. EventID: 0x0000043D
  275.  
  276. Time Generated: 02/20/2015 06:56:44
  277.  
  278. Event String:
  279.  
  280. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  281.  
  282. A warning event occurred. EventID: 0x0000043D
  283.  
  284. Time Generated: 02/20/2015 07:01:49
  285.  
  286. Event String:
  287.  
  288. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  289.  
  290. A warning event occurred. EventID: 0x0000043D
  291.  
  292. Time Generated: 02/20/2015 07:01:52
  293.  
  294. Event String:
  295.  
  296. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  297.  
  298. A warning event occurred. EventID: 0x0000043D
  299.  
  300. Time Generated: 02/20/2015 07:01:52
  301.  
  302. Event String:
  303.  
  304. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  305.  
  306. A warning event occurred. EventID: 0x0000043D
  307.  
  308. Time Generated: 02/20/2015 07:06:57
  309.  
  310. Event String:
  311.  
  312. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  313.  
  314. A warning event occurred. EventID: 0x0000043D
  315.  
  316. Time Generated: 02/20/2015 07:06:59
  317.  
  318. Event String:
  319.  
  320. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  321.  
  322. A warning event occurred. EventID: 0x0000043D
  323.  
  324. Time Generated: 02/20/2015 07:06:59
  325.  
  326. Event String:
  327.  
  328. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  329.  
  330. A warning event occurred. EventID: 0x0000043D
  331.  
  332. Time Generated: 02/20/2015 07:12:05
  333.  
  334. Event String:
  335.  
  336. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  337.  
  338. A warning event occurred. EventID: 0x0000043D
  339.  
  340. Time Generated: 02/20/2015 07:12:07
  341.  
  342. Event String:
  343.  
  344. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  345.  
  346. A warning event occurred. EventID: 0x0000043D
  347.  
  348. Time Generated: 02/20/2015 07:12:07
  349.  
  350. Event String:
  351.  
  352. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  353.  
  354. A warning event occurred. EventID: 0x0000043D
  355.  
  356. Time Generated: 02/20/2015 07:17:12
  357.  
  358. Event String:
  359.  
  360. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  361.  
  362. A warning event occurred. EventID: 0x0000043D
  363.  
  364. Time Generated: 02/20/2015 07:17:15
  365.  
  366. Event String:
  367.  
  368. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  369.  
  370. A warning event occurred. EventID: 0x0000043D
  371.  
  372. Time Generated: 02/20/2015 07:17:15
  373.  
  374. Event String:
  375.  
  376. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  377.  
  378. A warning event occurred. EventID: 0x0000043D
  379.  
  380. Time Generated: 02/20/2015 07:22:20
  381.  
  382. Event String:
  383.  
  384. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  385.  
  386. A warning event occurred. EventID: 0x0000043D
  387.  
  388. Time Generated: 02/20/2015 07:22:22
  389.  
  390. Event String:
  391.  
  392. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  393.  
  394. A warning event occurred. EventID: 0x0000043D
  395.  
  396. Time Generated: 02/20/2015 07:22:23
  397.  
  398. Event String:
  399.  
  400. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  401.  
  402. A warning event occurred. EventID: 0x0000043D
  403.  
  404. Time Generated: 02/20/2015 07:27:28
  405.  
  406. Event String:
  407.  
  408. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  409.  
  410. A warning event occurred. EventID: 0x0000043D
  411.  
  412. Time Generated: 02/20/2015 07:27:30
  413.  
  414. Event String:
  415.  
  416. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  417.  
  418. A warning event occurred. EventID: 0x0000043D
  419.  
  420. Time Generated: 02/20/2015 07:27:31
  421.  
  422. Event String:
  423.  
  424. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  425.  
  426. A warning event occurred. EventID: 0x0000043D
  427.  
  428. Time Generated: 02/20/2015 07:32:36
  429.  
  430. Event String:
  431.  
  432. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  433.  
  434. A warning event occurred. EventID: 0x0000043D
  435.  
  436. Time Generated: 02/20/2015 07:32:38
  437.  
  438. Event String:
  439.  
  440. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  441.  
  442. A warning event occurred. EventID: 0x0000043D
  443.  
  444. Time Generated: 02/20/2015 07:32:38
  445.  
  446. Event String:
  447.  
  448. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  449.  
  450. A warning event occurred. EventID: 0x0000043D
  451.  
  452. Time Generated: 02/20/2015 07:37:44
  453.  
  454. Event String:
  455.  
  456. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  457.  
  458. A warning event occurred. EventID: 0x0000043D
  459.  
  460. Time Generated: 02/20/2015 07:37:46
  461.  
  462. Event String:
  463.  
  464. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  465.  
  466. A warning event occurred. EventID: 0x0000043D
  467.  
  468. Time Generated: 02/20/2015 07:37:46
  469.  
  470. Event String:
  471.  
  472. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  473.  
  474. A warning event occurred. EventID: 0x0000043D
  475.  
  476. Time Generated: 02/20/2015 07:42:51
  477.  
  478. Event String:
  479.  
  480. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  481.  
  482. A warning event occurred. EventID: 0x0000043D
  483.  
  484. Time Generated: 02/20/2015 07:42:54
  485.  
  486. Event String:
  487.  
  488. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  489.  
  490. A warning event occurred. EventID: 0x0000043D
  491.  
  492. Time Generated: 02/20/2015 07:42:54
  493.  
  494. Event String:
  495.  
  496. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  497.  
  498. A warning event occurred. EventID: 0x0000043D
  499.  
  500. Time Generated: 02/20/2015 07:47:59
  501.  
  502. Event String:
  503.  
  504. Windows failed to apply the Group Policy Files settings. Group Policy Files settings might have its own log file. Please click on the "More information" link.
  505.  
  506. A warning event occurred. EventID: 0x0000043D
  507.  
  508. Time Generated: 02/20/2015 07:48:02
  509.  
  510. Event String:
  511.  
  512. Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
  513.  
  514. A warning event occurred. EventID: 0x0000043D
  515.  
  516. Time Generated: 02/20/2015 07:48:02
  517.  
  518. Event String:
  519.  
  520. Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link.
  521.  
  522. ......................... DC2 passed test SystemLog
  523.  
  524. Starting test: VerifyReferences
  525.  
  526. ......................... DC2 passed test VerifyReferences
  527.  
  528.  
  529. Testing server: AtlantaStaging\H2S2-ADDC2
  530.  
  531. Starting test: Advertising
  532.  
  533. ......................... H2S2-ADDC2 passed test Advertising
  534.  
  535. Starting test: FrsEvent
  536.  
  537. ......................... H2S2-ADDC2 passed test FrsEvent
  538.  
  539. Starting test: DFSREvent
  540.  
  541. ......................... H2S2-ADDC2 passed test DFSREvent
  542.  
  543. Starting test: SysVolCheck
  544.  
  545. ......................... H2S2-ADDC2 passed test SysVolCheck
  546.  
  547. Starting test: KccEvent
  548.  
  549. ......................... H2S2-ADDC2 passed test KccEvent
  550.  
  551. Starting test: KnowsOfRoleHolders
  552.  
  553. ......................... H2S2-ADDC2 passed test KnowsOfRoleHolders
  554.  
  555. Starting test: MachineAccount
  556.  
  557. ......................... H2S2-ADDC2 passed test MachineAccount
  558.  
  559. Starting test: NCSecDesc
  560.  
  561. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  562.  
  563. Replicating Directory Changes In Filtered Set
  564. access rights for the naming context:
  565.  
  566. DC=ForestDnsZones,DC=HOMENET,DC=local
  567. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  568.  
  569. Replicating Directory Changes In Filtered Set
  570. access rights for the naming context:
  571.  
  572. DC=DomainDnsZones,DC=HOMENET,DC=local
  573. ......................... H2S2-ADDC2 failed test NCSecDesc
  574.  
  575. Starting test: NetLogons
  576.  
  577. ......................... H2S2-ADDC2 passed test NetLogons
  578.  
  579. Starting test: ObjectsReplicated
  580.  
  581. ......................... H2S2-ADDC2 passed test ObjectsReplicated
  582.  
  583. Starting test: Replications
  584.  
  585. ......................... H2S2-ADDC2 passed test Replications
  586.  
  587. Starting test: RidManager
  588.  
  589. ......................... H2S2-ADDC2 passed test RidManager
  590.  
  591. Starting test: Services
  592.  
  593. ......................... H2S2-ADDC2 passed test Services
  594.  
  595. Starting test: SystemLog
  596.  
  597. A warning event occurred. EventID: 0x8000001D
  598.  
  599. Time Generated: 02/20/2015 07:11:27
  600.  
  601. Event String:
  602.  
  603. The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate could not be verified. Smart card logon may not function correctly if this problem is not resolved. To correct this problem, either verify the existing KDC certificate using certutil.exe or enroll for a new KDC certificate.
  604.  
  605. ......................... H2S2-ADDC2 passed test SystemLog
  606.  
  607. Starting test: VerifyReferences
  608.  
  609. ......................... H2S2-ADDC2 passed test VerifyReferences
  610.  
  611.  
  612. Testing server: AtlantaH2P\H2P-ADDC1
  613.  
  614. Starting test: Advertising
  615.  
  616. ......................... H2P-ADDC1 passed test Advertising
  617.  
  618. Starting test: FrsEvent
  619.  
  620. ......................... H2P-ADDC1 passed test FrsEvent
  621.  
  622. Starting test: DFSREvent
  623.  
  624. ......................... H2P-ADDC1 passed test DFSREvent
  625.  
  626. Starting test: SysVolCheck
  627.  
  628. ......................... H2P-ADDC1 passed test SysVolCheck
  629.  
  630. Starting test: KccEvent
  631.  
  632. ......................... H2P-ADDC1 passed test KccEvent
  633.  
  634. Starting test: KnowsOfRoleHolders
  635.  
  636. ......................... H2P-ADDC1 passed test KnowsOfRoleHolders
  637.  
  638. Starting test: MachineAccount
  639.  
  640. ......................... H2P-ADDC1 passed test MachineAccount
  641.  
  642. Starting test: NCSecDesc
  643.  
  644. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  645.  
  646. Replicating Directory Changes In Filtered Set
  647. access rights for the naming context:
  648.  
  649. DC=ForestDnsZones,DC=HOMENET,DC=local
  650. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  651.  
  652. Replicating Directory Changes In Filtered Set
  653. access rights for the naming context:
  654.  
  655. DC=DomainDnsZones,DC=HOMENET,DC=local
  656. ......................... H2P-ADDC1 failed test NCSecDesc
  657.  
  658. Starting test: NetLogons
  659.  
  660. ......................... H2P-ADDC1 passed test NetLogons
  661.  
  662. Starting test: ObjectsReplicated
  663.  
  664. ......................... H2P-ADDC1 passed test ObjectsReplicated
  665.  
  666. Starting test: Replications
  667.  
  668. ......................... H2P-ADDC1 passed test Replications
  669.  
  670. Starting test: RidManager
  671.  
  672. ......................... H2P-ADDC1 passed test RidManager
  673.  
  674. Starting test: Services
  675.  
  676. ......................... H2P-ADDC1 passed test Services
  677.  
  678. Starting test: SystemLog
  679.  
  680. ......................... H2P-ADDC1 passed test SystemLog
  681.  
  682. Starting test: VerifyReferences
  683.  
  684. ......................... H2P-ADDC1 passed test VerifyReferences
  685.  
  686.  
  687. Testing server: AtlantaH2P\H2P-ADDC2
  688.  
  689. Starting test: Advertising
  690.  
  691. ......................... H2P-ADDC2 passed test Advertising
  692.  
  693. Starting test: FrsEvent
  694.  
  695. ......................... H2P-ADDC2 passed test FrsEvent
  696.  
  697. Starting test: DFSREvent
  698.  
  699. ......................... H2P-ADDC2 passed test DFSREvent
  700.  
  701. Starting test: SysVolCheck
  702.  
  703. ......................... H2P-ADDC2 passed test SysVolCheck
  704.  
  705. Starting test: KccEvent
  706.  
  707. ......................... H2P-ADDC2 passed test KccEvent
  708.  
  709. Starting test: KnowsOfRoleHolders
  710.  
  711. ......................... H2P-ADDC2 passed test KnowsOfRoleHolders
  712.  
  713. Starting test: MachineAccount
  714.  
  715. ......................... H2P-ADDC2 passed test MachineAccount
  716.  
  717. Starting test: NCSecDesc
  718.  
  719. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  720.  
  721. Replicating Directory Changes In Filtered Set
  722. access rights for the naming context:
  723.  
  724. DC=ForestDnsZones,DC=HOMENET,DC=local
  725. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  726.  
  727. Replicating Directory Changes In Filtered Set
  728. access rights for the naming context:
  729.  
  730. DC=DomainDnsZones,DC=HOMENET,DC=local
  731. ......................... H2P-ADDC2 failed test NCSecDesc
  732.  
  733. Starting test: NetLogons
  734.  
  735. ......................... H2P-ADDC2 passed test NetLogons
  736.  
  737. Starting test: ObjectsReplicated
  738.  
  739. ......................... H2P-ADDC2 passed test ObjectsReplicated
  740.  
  741. Starting test: Replications
  742.  
  743. ......................... H2P-ADDC2 passed test Replications
  744.  
  745. Starting test: RidManager
  746.  
  747. ......................... H2P-ADDC2 passed test RidManager
  748.  
  749. Starting test: Services
  750.  
  751. ......................... H2P-ADDC2 passed test Services
  752.  
  753. Starting test: SystemLog
  754.  
  755. A warning event occurred. EventID: 0x000016AF
  756.  
  757. Time Generated: 02/20/2015 07:23:16
  758.  
  759. Event String:
  760.  
  761. During the past 4.20 hours there have been 83 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined sites and may connect to any Domain Controller including those that are in far distant locations from the clients. A client's site is determined by the mapping of its subnet to one of the existing sites. To move the above clients to one of the sites, please consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites. The names and IP addresses of the clients in question have been logged on this computer in the following log file '%SystemRoot%\debug\netlogon.log' and, potentially, in the log file '%SystemRoot%\debug\netlogon.bak' created if the former log becomes full. The log(s) may contain additional unrelated debugging information. To filter out the needed information, please search for lines which contain text 'NO_CLIENT_SITE:'. The first word after this string is the client name and the second word is the client IP address. The maximum size of the log(s) is controlled by the following registry DWORD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize'; the default is 20000000 bytes. The current maximum size is 20000000 bytes. To set a different maximum size, create the above registry value and set the desired maximum size in bytes.
  762.  
  763. ......................... H2P-ADDC2 passed test SystemLog
  764.  
  765. Starting test: VerifyReferences
  766.  
  767. ......................... H2P-ADDC2 passed test VerifyReferences
  768.  
  769.  
  770. Testing server: AtlantaH3R\H3R-ADDC1
  771.  
  772. Starting test: Advertising
  773.  
  774. ......................... H3R-ADDC1 passed test Advertising
  775.  
  776. Starting test: FrsEvent
  777.  
  778. ......................... H3R-ADDC1 passed test FrsEvent
  779.  
  780. Starting test: DFSREvent
  781.  
  782. ......................... H3R-ADDC1 passed test DFSREvent
  783.  
  784. Starting test: SysVolCheck
  785.  
  786. ......................... H3R-ADDC1 passed test SysVolCheck
  787.  
  788. Starting test: KccEvent
  789.  
  790. ......................... H3R-ADDC1 passed test KccEvent
  791.  
  792. Starting test: KnowsOfRoleHolders
  793.  
  794. ......................... H3R-ADDC1 passed test KnowsOfRoleHolders
  795.  
  796. Starting test: MachineAccount
  797.  
  798. ......................... H3R-ADDC1 passed test MachineAccount
  799.  
  800. Starting test: NCSecDesc
  801.  
  802. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  803.  
  804. Replicating Directory Changes In Filtered Set
  805. access rights for the naming context:
  806.  
  807. DC=ForestDnsZones,DC=HOMENET,DC=local
  808. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  809.  
  810. Replicating Directory Changes In Filtered Set
  811. access rights for the naming context:
  812.  
  813. DC=DomainDnsZones,DC=HOMENET,DC=local
  814. ......................... H3R-ADDC1 failed test NCSecDesc
  815.  
  816. Starting test: NetLogons
  817.  
  818. ......................... H3R-ADDC1 passed test NetLogons
  819.  
  820. Starting test: ObjectsReplicated
  821.  
  822. ......................... H3R-ADDC1 passed test ObjectsReplicated
  823.  
  824. Starting test: Replications
  825.  
  826. ......................... H3R-ADDC1 passed test Replications
  827.  
  828. Starting test: RidManager
  829.  
  830. ......................... H3R-ADDC1 passed test RidManager
  831.  
  832. Starting test: Services
  833.  
  834. ......................... H3R-ADDC1 passed test Services
  835.  
  836. Starting test: SystemLog
  837.  
  838. A warning event occurred. EventID: 0x00009016
  839.  
  840. Time Generated: 02/20/2015 06:55:04
  841.  
  842. Event String:
  843.  
  844. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  845.  
  846. A warning event occurred. EventID: 0x00009016
  847.  
  848. Time Generated: 02/20/2015 07:30:33
  849.  
  850. Event String:
  851.  
  852. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  853.  
  854. A warning event occurred. EventID: 0x00009016
  855.  
  856. Time Generated: 02/20/2015 07:30:40
  857.  
  858. Event String:
  859.  
  860. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  861.  
  862. A warning event occurred. EventID: 0x00009016
  863.  
  864. Time Generated: 02/20/2015 07:30:40
  865.  
  866. Event String:
  867.  
  868. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  869.  
  870. A warning event occurred. EventID: 0x00009016
  871.  
  872. Time Generated: 02/20/2015 07:36:47
  873.  
  874. Event String:
  875.  
  876. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  877.  
  878. A warning event occurred. EventID: 0x00009016
  879.  
  880. Time Generated: 02/20/2015 07:37:28
  881.  
  882. Event String:
  883.  
  884. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  885.  
  886. A warning event occurred. EventID: 0x00009016
  887.  
  888. Time Generated: 02/20/2015 07:40:20
  889.  
  890. Event String:
  891.  
  892. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  893.  
  894. A warning event occurred. EventID: 0x00009016
  895.  
  896. Time Generated: 02/20/2015 07:44:17
  897.  
  898. Event String:
  899.  
  900. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  901.  
  902. ......................... H3R-ADDC1 passed test SystemLog
  903.  
  904. Starting test: VerifyReferences
  905.  
  906. ......................... H3R-ADDC1 passed test VerifyReferences
  907.  
  908.  
  909. Testing server: AtlantaH3R\H3R-ADDC2
  910.  
  911. Starting test: Advertising
  912.  
  913. ......................... H3R-ADDC2 passed test Advertising
  914.  
  915. Starting test: FrsEvent
  916.  
  917. ......................... H3R-ADDC2 passed test FrsEvent
  918.  
  919. Starting test: DFSREvent
  920.  
  921. ......................... H3R-ADDC2 passed test DFSREvent
  922.  
  923. Starting test: SysVolCheck
  924.  
  925. ......................... H3R-ADDC2 passed test SysVolCheck
  926.  
  927. Starting test: KccEvent
  928.  
  929. ......................... H3R-ADDC2 passed test KccEvent
  930.  
  931. Starting test: KnowsOfRoleHolders
  932.  
  933. ......................... H3R-ADDC2 passed test KnowsOfRoleHolders
  934.  
  935. Starting test: MachineAccount
  936.  
  937. ......................... H3R-ADDC2 passed test MachineAccount
  938.  
  939. Starting test: NCSecDesc
  940.  
  941. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  942.  
  943. Replicating Directory Changes In Filtered Set
  944. access rights for the naming context:
  945.  
  946. DC=ForestDnsZones,DC=HOMENET,DC=local
  947. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  948.  
  949. Replicating Directory Changes In Filtered Set
  950. access rights for the naming context:
  951.  
  952. DC=DomainDnsZones,DC=HOMENET,DC=local
  953. ......................... H3R-ADDC2 failed test NCSecDesc
  954.  
  955. Starting test: NetLogons
  956.  
  957. ......................... H3R-ADDC2 passed test NetLogons
  958.  
  959. Starting test: ObjectsReplicated
  960.  
  961. ......................... H3R-ADDC2 passed test ObjectsReplicated
  962.  
  963. Starting test: Replications
  964.  
  965. ......................... H3R-ADDC2 passed test Replications
  966.  
  967. Starting test: RidManager
  968.  
  969. ......................... H3R-ADDC2 passed test RidManager
  970.  
  971. Starting test: Services
  972.  
  973. ......................... H3R-ADDC2 passed test Services
  974.  
  975. Starting test: SystemLog
  976.  
  977. A warning event occurred. EventID: 0x00009016
  978.  
  979. Time Generated: 02/20/2015 07:14:37
  980.  
  981. Event String:
  982.  
  983. No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
  984.  
  985. ......................... H3R-ADDC2 passed test SystemLog
  986.  
  987. Starting test: VerifyReferences
  988.  
  989. ......................... H3R-ADDC2 passed test VerifyReferences
  990.  
  991.  
  992. Testing server: AtlantaStaging\H2S3-ADDC1
  993.  
  994. Starting test: Advertising
  995.  
  996. ......................... H2S3-ADDC1 passed test Advertising
  997.  
  998. Starting test: FrsEvent
  999.  
  1000. ......................... H2S3-ADDC1 passed test FrsEvent
  1001.  
  1002. Starting test: DFSREvent
  1003.  
  1004. ......................... H2S3-ADDC1 passed test DFSREvent
  1005.  
  1006. Starting test: SysVolCheck
  1007.  
  1008. ......................... H2S3-ADDC1 passed test SysVolCheck
  1009.  
  1010. Starting test: KccEvent
  1011.  
  1012. ......................... H2S3-ADDC1 passed test KccEvent
  1013.  
  1014. Starting test: KnowsOfRoleHolders
  1015.  
  1016. ......................... H2S3-ADDC1 passed test KnowsOfRoleHolders
  1017.  
  1018. Starting test: MachineAccount
  1019.  
  1020. ......................... H2S3-ADDC1 passed test MachineAccount
  1021.  
  1022. Starting test: NCSecDesc
  1023.  
  1024. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  1025.  
  1026. Replicating Directory Changes In Filtered Set
  1027. access rights for the naming context:
  1028.  
  1029. DC=ForestDnsZones,DC=HOMENET,DC=local
  1030. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  1031.  
  1032. Replicating Directory Changes In Filtered Set
  1033. access rights for the naming context:
  1034.  
  1035. DC=DomainDnsZones,DC=HOMENET,DC=local
  1036. ......................... H2S3-ADDC1 failed test NCSecDesc
  1037.  
  1038. Starting test: NetLogons
  1039.  
  1040. ......................... H2S3-ADDC1 passed test NetLogons
  1041.  
  1042. Starting test: ObjectsReplicated
  1043.  
  1044. ......................... H2S3-ADDC1 passed test ObjectsReplicated
  1045.  
  1046. Starting test: Replications
  1047.  
  1048. ......................... H2S3-ADDC1 passed test Replications
  1049.  
  1050. Starting test: RidManager
  1051.  
  1052. ......................... H2S3-ADDC1 passed test RidManager
  1053.  
  1054. Starting test: Services
  1055.  
  1056. ......................... H2S3-ADDC1 passed test Services
  1057.  
  1058. Starting test: SystemLog
  1059.  
  1060. ......................... H2S3-ADDC1 passed test SystemLog
  1061.  
  1062. Starting test: VerifyReferences
  1063.  
  1064. ......................... H2S3-ADDC1 passed test VerifyReferences
  1065.  
  1066.  
  1067. Testing server: AtlantaStaging\H2S3-ADDC2
  1068.  
  1069. Starting test: Advertising
  1070.  
  1071. ......................... H2S3-ADDC2 passed test Advertising
  1072.  
  1073. Starting test: FrsEvent
  1074.  
  1075. ......................... H2S3-ADDC2 passed test FrsEvent
  1076.  
  1077. Starting test: DFSREvent
  1078.  
  1079. ......................... H2S3-ADDC2 passed test DFSREvent
  1080.  
  1081. Starting test: SysVolCheck
  1082.  
  1083. ......................... H2S3-ADDC2 passed test SysVolCheck
  1084.  
  1085. Starting test: KccEvent
  1086.  
  1087. ......................... H2S3-ADDC2 passed test KccEvent
  1088.  
  1089. Starting test: KnowsOfRoleHolders
  1090.  
  1091. ......................... H2S3-ADDC2 passed test KnowsOfRoleHolders
  1092.  
  1093. Starting test: MachineAccount
  1094.  
  1095. ......................... H2S3-ADDC2 passed test MachineAccount
  1096.  
  1097. Starting test: NCSecDesc
  1098.  
  1099. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  1100.  
  1101. Replicating Directory Changes In Filtered Set
  1102. access rights for the naming context:
  1103.  
  1104. DC=ForestDnsZones,DC=HOMENET,DC=local
  1105. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  1106.  
  1107. Replicating Directory Changes In Filtered Set
  1108. access rights for the naming context:
  1109.  
  1110. DC=DomainDnsZones,DC=HOMENET,DC=local
  1111. ......................... H2S3-ADDC2 failed test NCSecDesc
  1112.  
  1113. Starting test: NetLogons
  1114.  
  1115. ......................... H2S3-ADDC2 passed test NetLogons
  1116.  
  1117. Starting test: ObjectsReplicated
  1118.  
  1119. ......................... H2S3-ADDC2 passed test ObjectsReplicated
  1120.  
  1121. Starting test: Replications
  1122.  
  1123. ......................... H2S3-ADDC2 passed test Replications
  1124.  
  1125. Starting test: RidManager
  1126.  
  1127. ......................... H2S3-ADDC2 passed test RidManager
  1128.  
  1129. Starting test: Services
  1130.  
  1131. ......................... H2S3-ADDC2 passed test Services
  1132.  
  1133. Starting test: SystemLog
  1134.  
  1135. ......................... H2S3-ADDC2 passed test SystemLog
  1136.  
  1137. Starting test: VerifyReferences
  1138.  
  1139. ......................... H2S3-ADDC2 passed test VerifyReferences
  1140.  
  1141.  
  1142. Testing server: AtlantaStaging\H2S2-ADDC1
  1143.  
  1144. Starting test: Advertising
  1145.  
  1146. ......................... H2S2-ADDC1 passed test Advertising
  1147.  
  1148. Starting test: FrsEvent
  1149.  
  1150. There are warning or error events within the last 24 hours after the
  1151.  
  1152. SYSVOL has been shared. Failing SYSVOL replication problems may cause
  1153.  
  1154. Group Policy problems.
  1155. ......................... H2S2-ADDC1 passed test FrsEvent
  1156.  
  1157. Starting test: DFSREvent
  1158.  
  1159. ......................... H2S2-ADDC1 passed test DFSREvent
  1160.  
  1161. Starting test: SysVolCheck
  1162.  
  1163. ......................... H2S2-ADDC1 passed test SysVolCheck
  1164.  
  1165. Starting test: KccEvent
  1166.  
  1167. ......................... H2S2-ADDC1 passed test KccEvent
  1168.  
  1169. Starting test: KnowsOfRoleHolders
  1170.  
  1171. ......................... H2S2-ADDC1 passed test KnowsOfRoleHolders
  1172.  
  1173. Starting test: MachineAccount
  1174.  
  1175. ......................... H2S2-ADDC1 passed test MachineAccount
  1176.  
  1177. Starting test: NCSecDesc
  1178.  
  1179. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  1180.  
  1181. Replicating Directory Changes In Filtered Set
  1182. access rights for the naming context:
  1183.  
  1184. DC=ForestDnsZones,DC=HOMENET,DC=local
  1185. Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
  1186.  
  1187. Replicating Directory Changes In Filtered Set
  1188. access rights for the naming context:
  1189.  
  1190. DC=DomainDnsZones,DC=HOMENET,DC=local
  1191. ......................... H2S2-ADDC1 failed test NCSecDesc
  1192.  
  1193. Starting test: NetLogons
  1194.  
  1195. ......................... H2S2-ADDC1 passed test NetLogons
  1196.  
  1197. Starting test: ObjectsReplicated
  1198.  
  1199. ......................... H2S2-ADDC1 passed test ObjectsReplicated
  1200.  
  1201. Starting test: Replications
  1202.  
  1203. ......................... H2S2-ADDC1 passed test Replications
  1204.  
  1205. Starting test: RidManager
  1206.  
  1207. ......................... H2S2-ADDC1 passed test RidManager
  1208.  
  1209. Starting test: Services
  1210.  
  1211. ......................... H2S2-ADDC1 passed test Services
  1212.  
  1213. Starting test: SystemLog
  1214.  
  1215. An error event occurred. EventID: 0x00000017
  1216.  
  1217. Time Generated: 02/20/2015 06:54:48
  1218.  
  1219. Event String:
  1220.  
  1221. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1222.  
  1223. A warning event occurred. EventID: 0x0000001B
  1224.  
  1225. Time Generated: 02/20/2015 06:54:48
  1226.  
  1227. Event String:
  1228.  
  1229. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1230.  
  1231. An error event occurred. EventID: 0x00000017
  1232.  
  1233. Time Generated: 02/20/2015 06:54:48
  1234.  
  1235. Event String:
  1236.  
  1237. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1238.  
  1239. A warning event occurred. EventID: 0x0000001B
  1240.  
  1241. Time Generated: 02/20/2015 06:54:48
  1242.  
  1243. Event String:
  1244.  
  1245. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1246.  
  1247. An error event occurred. EventID: 0x00000017
  1248.  
  1249. Time Generated: 02/20/2015 06:54:48
  1250.  
  1251. Event String:
  1252.  
  1253. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1254.  
  1255. An error event occurred. EventID: 0x00000017
  1256.  
  1257. Time Generated: 02/20/2015 06:54:48
  1258.  
  1259. Event String:
  1260.  
  1261. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1262.  
  1263. A warning event occurred. EventID: 0x0000001B
  1264.  
  1265. Time Generated: 02/20/2015 06:54:48
  1266.  
  1267. Event String:
  1268.  
  1269. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1270.  
  1271. An error event occurred. EventID: 0x00000017
  1272.  
  1273. Time Generated: 02/20/2015 06:59:52
  1274.  
  1275. Event String:
  1276.  
  1277. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1278.  
  1279. A warning event occurred. EventID: 0x0000001B
  1280.  
  1281. Time Generated: 02/20/2015 06:59:52
  1282.  
  1283. Event String:
  1284.  
  1285. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1286.  
  1287. An error event occurred. EventID: 0x00000017
  1288.  
  1289. Time Generated: 02/20/2015 06:59:52
  1290.  
  1291. Event String:
  1292.  
  1293. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1294.  
  1295. A warning event occurred. EventID: 0x0000001B
  1296.  
  1297. Time Generated: 02/20/2015 06:59:52
  1298.  
  1299. Event String:
  1300.  
  1301. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1302.  
  1303. An error event occurred. EventID: 0x00000017
  1304.  
  1305. Time Generated: 02/20/2015 06:59:52
  1306.  
  1307. Event String:
  1308.  
  1309. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1310.  
  1311. An error event occurred. EventID: 0x00000017
  1312.  
  1313. Time Generated: 02/20/2015 06:59:52
  1314.  
  1315. Event String:
  1316.  
  1317. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1318.  
  1319. A warning event occurred. EventID: 0x0000001B
  1320.  
  1321. Time Generated: 02/20/2015 06:59:52
  1322.  
  1323. Event String:
  1324.  
  1325. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1326.  
  1327. An error event occurred. EventID: 0x00000017
  1328.  
  1329. Time Generated: 02/20/2015 07:04:57
  1330.  
  1331. Event String:
  1332.  
  1333. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1334.  
  1335. A warning event occurred. EventID: 0x0000001B
  1336.  
  1337. Time Generated: 02/20/2015 07:04:57
  1338.  
  1339. Event String:
  1340.  
  1341. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1342.  
  1343. An error event occurred. EventID: 0x00000017
  1344.  
  1345. Time Generated: 02/20/2015 07:04:57
  1346.  
  1347. Event String:
  1348.  
  1349. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1350.  
  1351. A warning event occurred. EventID: 0x0000001B
  1352.  
  1353. Time Generated: 02/20/2015 07:04:57
  1354.  
  1355. Event String:
  1356.  
  1357. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1358.  
  1359. An error event occurred. EventID: 0x00000017
  1360.  
  1361. Time Generated: 02/20/2015 07:04:57
  1362.  
  1363. Event String:
  1364.  
  1365. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1366.  
  1367. An error event occurred. EventID: 0x00000017
  1368.  
  1369. Time Generated: 02/20/2015 07:04:57
  1370.  
  1371. Event String:
  1372.  
  1373. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1374.  
  1375. A warning event occurred. EventID: 0x0000001B
  1376.  
  1377. Time Generated: 02/20/2015 07:04:57
  1378.  
  1379. Event String:
  1380.  
  1381. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1382.  
  1383. An error event occurred. EventID: 0x00000017
  1384.  
  1385. Time Generated: 02/20/2015 07:10:01
  1386.  
  1387. Event String:
  1388.  
  1389. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1390.  
  1391. A warning event occurred. EventID: 0x0000001B
  1392.  
  1393. Time Generated: 02/20/2015 07:10:01
  1394.  
  1395. Event String:
  1396.  
  1397. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1398.  
  1399. An error event occurred. EventID: 0x00000017
  1400.  
  1401. Time Generated: 02/20/2015 07:10:01
  1402.  
  1403. Event String:
  1404.  
  1405. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1406.  
  1407. A warning event occurred. EventID: 0x0000001B
  1408.  
  1409. Time Generated: 02/20/2015 07:10:01
  1410.  
  1411. Event String:
  1412.  
  1413. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1414.  
  1415. An error event occurred. EventID: 0x00000017
  1416.  
  1417. Time Generated: 02/20/2015 07:10:01
  1418.  
  1419. Event String:
  1420.  
  1421. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1422.  
  1423. An error event occurred. EventID: 0x00000017
  1424.  
  1425. Time Generated: 02/20/2015 07:10:01
  1426.  
  1427. Event String:
  1428.  
  1429. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1430.  
  1431. A warning event occurred. EventID: 0x0000001B
  1432.  
  1433. Time Generated: 02/20/2015 07:10:01
  1434.  
  1435. Event String:
  1436.  
  1437. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1438.  
  1439. An error event occurred. EventID: 0x00000017
  1440.  
  1441. Time Generated: 02/20/2015 07:15:05
  1442.  
  1443. Event String:
  1444.  
  1445. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1446.  
  1447. A warning event occurred. EventID: 0x0000001B
  1448.  
  1449. Time Generated: 02/20/2015 07:15:05
  1450.  
  1451. Event String:
  1452.  
  1453. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1454.  
  1455. An error event occurred. EventID: 0x00000017
  1456.  
  1457. Time Generated: 02/20/2015 07:15:05
  1458.  
  1459. Event String:
  1460.  
  1461. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1462.  
  1463. A warning event occurred. EventID: 0x0000001B
  1464.  
  1465. Time Generated: 02/20/2015 07:15:05
  1466.  
  1467. Event String:
  1468.  
  1469. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1470.  
  1471. An error event occurred. EventID: 0x00000017
  1472.  
  1473. Time Generated: 02/20/2015 07:15:05
  1474.  
  1475. Event String:
  1476.  
  1477. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1478.  
  1479. An error event occurred. EventID: 0x00000017
  1480.  
  1481. Time Generated: 02/20/2015 07:15:05
  1482.  
  1483. Event String:
  1484.  
  1485. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1486.  
  1487. A warning event occurred. EventID: 0x0000001B
  1488.  
  1489. Time Generated: 02/20/2015 07:15:05
  1490.  
  1491. Event String:
  1492.  
  1493. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1494.  
  1495. An error event occurred. EventID: 0x00000017
  1496.  
  1497. Time Generated: 02/20/2015 07:20:09
  1498.  
  1499. Event String:
  1500.  
  1501. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1502.  
  1503. A warning event occurred. EventID: 0x0000001B
  1504.  
  1505. Time Generated: 02/20/2015 07:20:09
  1506.  
  1507. Event String:
  1508.  
  1509. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1510.  
  1511. An error event occurred. EventID: 0x00000017
  1512.  
  1513. Time Generated: 02/20/2015 07:20:10
  1514.  
  1515. Event String:
  1516.  
  1517. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1518.  
  1519. A warning event occurred. EventID: 0x0000001B
  1520.  
  1521. Time Generated: 02/20/2015 07:20:10
  1522.  
  1523. Event String:
  1524.  
  1525. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1526.  
  1527. An error event occurred. EventID: 0x00000017
  1528.  
  1529. Time Generated: 02/20/2015 07:20:10
  1530.  
  1531. Event String:
  1532.  
  1533. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1534.  
  1535. An error event occurred. EventID: 0x00000017
  1536.  
  1537. Time Generated: 02/20/2015 07:20:10
  1538.  
  1539. Event String:
  1540.  
  1541. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1542.  
  1543. A warning event occurred. EventID: 0x0000001B
  1544.  
  1545. Time Generated: 02/20/2015 07:20:10
  1546.  
  1547. Event String:
  1548.  
  1549. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1550.  
  1551. An error event occurred. EventID: 0x00000017
  1552.  
  1553. Time Generated: 02/20/2015 07:25:14
  1554.  
  1555. Event String:
  1556.  
  1557. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1558.  
  1559. A warning event occurred. EventID: 0x0000001B
  1560.  
  1561. Time Generated: 02/20/2015 07:25:14
  1562.  
  1563. Event String:
  1564.  
  1565. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1566.  
  1567. An error event occurred. EventID: 0x00000017
  1568.  
  1569. Time Generated: 02/20/2015 07:25:14
  1570.  
  1571. Event String:
  1572.  
  1573. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1574.  
  1575. A warning event occurred. EventID: 0x0000001B
  1576.  
  1577. Time Generated: 02/20/2015 07:25:14
  1578.  
  1579. Event String:
  1580.  
  1581. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1582.  
  1583. An error event occurred. EventID: 0x00000017
  1584.  
  1585. Time Generated: 02/20/2015 07:25:14
  1586.  
  1587. Event String:
  1588.  
  1589. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1590.  
  1591. An error event occurred. EventID: 0x00000017
  1592.  
  1593. Time Generated: 02/20/2015 07:25:14
  1594.  
  1595. Event String:
  1596.  
  1597. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1598.  
  1599. A warning event occurred. EventID: 0x0000001B
  1600.  
  1601. Time Generated: 02/20/2015 07:25:14
  1602.  
  1603. Event String:
  1604.  
  1605. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1606.  
  1607. An error event occurred. EventID: 0x00000017
  1608.  
  1609. Time Generated: 02/20/2015 07:30:18
  1610.  
  1611. Event String:
  1612.  
  1613. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1614.  
  1615. A warning event occurred. EventID: 0x0000001B
  1616.  
  1617. Time Generated: 02/20/2015 07:30:18
  1618.  
  1619. Event String:
  1620.  
  1621. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1622.  
  1623. An error event occurred. EventID: 0x00000017
  1624.  
  1625. Time Generated: 02/20/2015 07:30:18
  1626.  
  1627. Event String:
  1628.  
  1629. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1630.  
  1631. A warning event occurred. EventID: 0x0000001B
  1632.  
  1633. Time Generated: 02/20/2015 07:30:18
  1634.  
  1635. Event String:
  1636.  
  1637. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1638.  
  1639. An error event occurred. EventID: 0x00000017
  1640.  
  1641. Time Generated: 02/20/2015 07:30:18
  1642.  
  1643. Event String:
  1644.  
  1645. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1646.  
  1647. An error event occurred. EventID: 0x00000017
  1648.  
  1649. Time Generated: 02/20/2015 07:30:18
  1650.  
  1651. Event String:
  1652.  
  1653. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1654.  
  1655. A warning event occurred. EventID: 0x0000001B
  1656.  
  1657. Time Generated: 02/20/2015 07:30:18
  1658.  
  1659. Event String:
  1660.  
  1661. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1662.  
  1663. An error event occurred. EventID: 0x00000017
  1664.  
  1665. Time Generated: 02/20/2015 07:35:23
  1666.  
  1667. Event String:
  1668.  
  1669. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1670.  
  1671. A warning event occurred. EventID: 0x0000001B
  1672.  
  1673. Time Generated: 02/20/2015 07:35:23
  1674.  
  1675. Event String:
  1676.  
  1677. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1678.  
  1679. An error event occurred. EventID: 0x00000017
  1680.  
  1681. Time Generated: 02/20/2015 07:35:23
  1682.  
  1683. Event String:
  1684.  
  1685. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1686.  
  1687. A warning event occurred. EventID: 0x0000001B
  1688.  
  1689. Time Generated: 02/20/2015 07:35:23
  1690.  
  1691. Event String:
  1692.  
  1693. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1694.  
  1695. An error event occurred. EventID: 0x00000017
  1696.  
  1697. Time Generated: 02/20/2015 07:35:23
  1698.  
  1699. Event String:
  1700.  
  1701. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1702.  
  1703. An error event occurred. EventID: 0x00000017
  1704.  
  1705. Time Generated: 02/20/2015 07:35:23
  1706.  
  1707. Event String:
  1708.  
  1709. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1710.  
  1711. A warning event occurred. EventID: 0x0000001B
  1712.  
  1713. Time Generated: 02/20/2015 07:35:23
  1714.  
  1715. Event String:
  1716.  
  1717. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1718.  
  1719. An error event occurred. EventID: 0x00000017
  1720.  
  1721. Time Generated: 02/20/2015 07:40:27
  1722.  
  1723. Event String:
  1724.  
  1725. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1726.  
  1727. A warning event occurred. EventID: 0x0000001B
  1728.  
  1729. Time Generated: 02/20/2015 07:40:27
  1730.  
  1731. Event String:
  1732.  
  1733. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1734.  
  1735. An error event occurred. EventID: 0x00000017
  1736.  
  1737. Time Generated: 02/20/2015 07:40:27
  1738.  
  1739. Event String:
  1740.  
  1741. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1742.  
  1743. A warning event occurred. EventID: 0x0000001B
  1744.  
  1745. Time Generated: 02/20/2015 07:40:27
  1746.  
  1747. Event String:
  1748.  
  1749. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1750.  
  1751. An error event occurred. EventID: 0x00000017
  1752.  
  1753. Time Generated: 02/20/2015 07:40:27
  1754.  
  1755. Event String:
  1756.  
  1757. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1758.  
  1759. An error event occurred. EventID: 0x00000017
  1760.  
  1761. Time Generated: 02/20/2015 07:40:27
  1762.  
  1763. Event String:
  1764.  
  1765. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1766.  
  1767. A warning event occurred. EventID: 0x0000001B
  1768.  
  1769. Time Generated: 02/20/2015 07:40:27
  1770.  
  1771. Event String:
  1772.  
  1773. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1774.  
  1775. An error event occurred. EventID: 0x00000017
  1776.  
  1777. Time Generated: 02/20/2015 07:45:31
  1778.  
  1779. Event String:
  1780.  
  1781. The event logging service encountered an error (res=3) while initializing logging resources for channel Application.
  1782.  
  1783. A warning event occurred. EventID: 0x0000001B
  1784.  
  1785. Time Generated: 02/20/2015 07:45:31
  1786.  
  1787. Event String:
  1788.  
  1789. The event logging service encountered an error (res=3) while opening log file for channel Application. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Application.evtx.
  1790.  
  1791. An error event occurred. EventID: 0x00000017
  1792.  
  1793. Time Generated: 02/20/2015 07:45:31
  1794.  
  1795. Event String:
  1796.  
  1797. The event logging service encountered an error (res=3) while initializing logging resources for channel Security.
  1798.  
  1799. A warning event occurred. EventID: 0x0000001B
  1800.  
  1801. Time Generated: 02/20/2015 07:45:31
  1802.  
  1803. Event String:
  1804.  
  1805. The event logging service encountered an error (res=3) while opening log file for channel Security. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\Security.evtx.
  1806.  
  1807. An error event occurred. EventID: 0x00000017
  1808.  
  1809. Time Generated: 02/20/2015 07:45:31
  1810.  
  1811. Event String:
  1812.  
  1813. The event logging service encountered an error (res=3) while initializing logging resources for channel Setup.
  1814.  
  1815. An error event occurred. EventID: 0x00000017
  1816.  
  1817. Time Generated: 02/20/2015 07:45:31
  1818.  
  1819. Event String:
  1820.  
  1821. The event logging service encountered an error (res=3) while initializing logging resources for channel System.
  1822.  
  1823. A warning event occurred. EventID: 0x0000001B
  1824.  
  1825. Time Generated: 02/20/2015 07:45:31
  1826.  
  1827. Event String:
  1828.  
  1829. The event logging service encountered an error (res=3) while opening log file for channel System. Trying again using default log file path %SystemRoot%\System32\Winevt\Logs\System.evtx.
  1830.  
  1831. ......................... H2S2-ADDC1 failed test SystemLog
  1832.  
  1833. Starting test: VerifyReferences
  1834.  
  1835. ......................... H2S2-ADDC1 passed test VerifyReferences
  1836.  
  1837.  
  1838.  
  1839.  
  1840.  
  1841.  
  1842.  
  1843.  
  1844.  
  1845.  
  1846.  
  1847.  
  1848. Running partition tests on : ForestDnsZones
  1849.  
  1850. Starting test: CheckSDRefDom
  1851.  
  1852. ......................... ForestDnsZones passed test CheckSDRefDom
  1853.  
  1854. Starting test: CrossRefValidation
  1855.  
  1856. ......................... ForestDnsZones passed test
  1857.  
  1858. CrossRefValidation
  1859.  
  1860.  
  1861. Running partition tests on : DomainDnsZones
  1862.  
  1863. Starting test: CheckSDRefDom
  1864.  
  1865. ......................... DomainDnsZones passed test CheckSDRefDom
  1866.  
  1867. Starting test: CrossRefValidation
  1868.  
  1869. ......................... DomainDnsZones passed test
  1870.  
  1871. CrossRefValidation
  1872.  
  1873.  
  1874. Running partition tests on : Schema
  1875.  
  1876. Starting test: CheckSDRefDom
  1877.  
  1878. ......................... Schema passed test CheckSDRefDom
  1879.  
  1880. Starting test: CrossRefValidation
  1881.  
  1882. ......................... Schema passed test CrossRefValidation
  1883.  
  1884.  
  1885. Running partition tests on : Configuration
  1886.  
  1887. Starting test: CheckSDRefDom
  1888.  
  1889. ......................... Configuration passed test CheckSDRefDom
  1890.  
  1891. Starting test: CrossRefValidation
  1892.  
  1893. ......................... Configuration passed test CrossRefValidation
  1894.  
  1895.  
  1896. Running partition tests on : HOMENET
  1897.  
  1898. Starting test: CheckSDRefDom
  1899.  
  1900. ......................... HOMENET passed test CheckSDRefDom
  1901.  
  1902. Starting test: CrossRefValidation
  1903.  
  1904. ......................... HOMENET passed test CrossRefValidation
  1905.  
  1906.  
  1907. Running enterprise tests on : HOMENET.local
  1908.  
  1909. Starting test: LocatorCheck
  1910.  
  1911. ......................... HOMENET.local passed test LocatorCheck
  1912.  
  1913. Starting test: Intersite
  1914.  
  1915. Doing intersite inbound replication test on site AtlantaH2P:
  1916. Doing intersite inbound replication test on site WestChester:
  1917. Doing intersite inbound replication test on site AtlantaStaging:
  1918. Doing intersite inbound replication test on site AtlantaH3R:
  1919. ......................... HOMENET.local 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!