API tools faq
paste
Advertisement
Guest User

Cannot add a domain controller to an existing 2012 R2 domain

a guest
Sep 6th, 2017
544
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Batch 30.45 KB | None | 0 0
raw download clone embed print report
  1. NOTE: Names changed for security. PrimaryDC is the name of the server, and TL.Domain.com is the altered name of the domain
  2.  
  3. Directory Server Diagnosis
  4.  
  5. Performing initial setup:
  6.  
  7.    Trying to find home server...
  8.  
  9.    * Verifying that the local machine PrimaryDC, is a Directory Server.
  10.    Home Server = PrimaryDC
  11.  
  12.    * Connecting to directory service on server PrimaryDC.
  13.  
  14.    * Identified AD Forest.
  15.    Collecting AD specific global data
  16.    * Collecting site info.
  17.  
  18.    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
  19.    The previous call succeeded
  20.    Iterating through the sites
  21.    Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com
  22.    Getting ISTG and options for the site
  23.    * Identifying all servers.
  24.  
  25.    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
  26.    The previous call succeeded....
  27.    The previous call succeeded
  28.    Iterating through the list of servers
  29.    Getting information for the server CN=NTDS Settings,CN=PrimaryDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com
  30.    objectGuid obtained
  31.    InvocationID obtained
  32.    dnsHostname obtained
  33.    site info obtained
  34.    All the info for the server collected
  35.    * Identifying all NC cross-refs.
  36.  
  37.    * Found 1 DC(s). Testing 1 of them.
  38.  
  39.    Done gathering initial info.
  40.  
  41.  
  42. Doing initial required tests
  43.  
  44.    
  45.    Testing server: Default-First-Site-Name\PrimaryDC
  46.  
  47.       Starting test: Connectivity
  48.  
  49.          * Active Directory LDAP Services Check
  50.          Determining IP4 connectivity
  51.          * Active Directory RPC Services Check
  52.          ......................... PrimaryDC passed test Connectivity
  53.  
  54.  
  55.  
  56. Doing primary tests
  57.  
  58.    
  59.    Testing server: Default-First-Site-Name\PrimaryDC
  60.  
  61.       Starting test: Advertising
  62.  
  63.          The DC PrimaryDC is advertising itself as a DC and having a DS.
  64.          The DC PrimaryDC is advertising as an LDAP server
  65.          The DC PrimaryDC is advertising as having a writeable directory
  66.          The DC PrimaryDC is advertising as a Key Distribution Center
  67.          The DC PrimaryDC is advertising as a time server
  68.          The DS PrimaryDC is advertising as a GC.
  69.          ......................... PrimaryDC passed test Advertising
  70.  
  71.       Starting test: CheckSecurityError
  72.  
  73.          * Dr Auth:  Beginning security errors check!
  74.          Found KDC PrimaryDC for domain TL.domain.com in site Default-First-Site-Name
  75.          Checking machine account for DC PrimaryDC on DC PrimaryDC.
  76.          * SPN found :LDAP/PrimaryDC.TL.domain.com/TL.domain.com
  77.          * SPN found :LDAP/PrimaryDC.TL.domain.com
  78.          * SPN found :LDAP/PrimaryDC
  79.          * SPN found :LDAP/PrimaryDC.TL.domain.com/TL
  80.          * SPN found :LDAP/4f38725e-281d-4077-8806-f0e6a6f86ff9._msdcs.TL.domain.com
  81.          * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/4f38725e-281d-4077-8806-f0e6a6f86ff9/TL.domain.com
  82.          * SPN found :HOST/PrimaryDC.TL.domain.com/TL.domain.com
  83.          * SPN found :HOST/PrimaryDC.TL.domain.com
  84.          * SPN found :HOST/PrimaryDC
  85.          * SPN found :HOST/PrimaryDC.TL.domain.com/TL
  86.          * SPN found :GC/PrimaryDC.TL.domain.com/TL.domain.com
  87.          [PrimaryDC] No security related replication errors were found on this DC!
  88.  
  89.          To target the connection to a specific source DC use /ReplSource:<DC>.
  90.  
  91.          ......................... PrimaryDC passed test CheckSecurityError
  92.  
  93.       Starting test: CutoffServers
  94.  
  95.          * Configuration Topology Aliveness Check
  96.          * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=TL,DC=domain,DC=com.
  97.          * Performing upstream (of target) analysis.
  98.          * Performing downstream (of target) analysis.
  99.          * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=TL,DC=domain,DC=com.
  100.          * Performing upstream (of target) analysis.
  101.          * Performing downstream (of target) analysis.
  102.          * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=TL,DC=domain,DC=com.
  103.          * Performing upstream (of target) analysis.
  104.          * Performing downstream (of target) analysis.
  105.          * Analyzing the alive system replication topology for CN=Configuration,DC=TL,DC=domain,DC=com.
  106.          * Performing upstream (of target) analysis.
  107.          * Performing downstream (of target) analysis.
  108.          * Analyzing the alive system replication topology for DC=TL,DC=domain,DC=com.
  109.          * Performing upstream (of target) analysis.
  110.          * Performing downstream (of target) analysis.
  111.          ......................... PrimaryDC passed test CutoffServers
  112.  
  113.       Starting test: FrsEvent
  114.  
  115.          * The File Replication Service Event log test
  116.          Skip the test because the server is running DFSR.
  117.  
  118.          ......................... PrimaryDC passed test FrsEvent
  119.  
  120.       Starting test: DFSREvent
  121.  
  122.          The DFS Replication Event Log.
  123.          There are warning or error events within the last 24 hours after the
  124.  
  125.          SYSVOL has been shared.  Failing SYSVOL replication problems may cause
  126.  
  127.          Group Policy problems.
  128.          An error event occurred.  EventID: 0xC0000FAC
  129.  
  130.             Time Generated: 09/05/2017   19:04:01
  131.  
  132.             Event String:
  133.  
  134.             The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 782 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
  135.  
  136.              
  137.  
  138.             To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.
  139.  
  140.              
  141.  
  142.             Additional Information:
  143.  
  144.             Error: 9061 (The replicated folder has been offline for too long.)
  145.  
  146.             Replicated Folder Name: SYSVOL Share
  147.  
  148.             Replicated Folder ID: 6608D239-9FD6-4CC2-8231-58C9601DF369
  149.  
  150.             Replication Group Name: Domain System Volume
  151.  
  152.             Replication Group ID: E8EFEA5C-DB12-4FFE-9126-9EE491A9FC32
  153.  
  154.             Member ID: 66A4FFDA-F573-484D-97C6-0B645AC566A2
  155.  
  156.          An error event occurred.  EventID: 0xC0000FAC
  157.  
  158.             Time Generated: 09/06/2017   09:53:39
  159.  
  160.             Event String:
  161.  
  162.             The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 782 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
  163.  
  164.              
  165.  
  166.             To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.
  167.  
  168.              
  169.  
  170.             Additional Information:
  171.  
  172.             Error: 9061 (The replicated folder has been offline for too long.)
  173.  
  174.             Replicated Folder Name: SYSVOL Share
  175.  
  176.             Replicated Folder ID: 6608D239-9FD6-4CC2-8231-58C9601DF369
  177.  
  178.             Replication Group Name: Domain System Volume
  179.  
  180.             Replication Group ID: E8EFEA5C-DB12-4FFE-9126-9EE491A9FC32
  181.  
  182.             Member ID: 66A4FFDA-F573-484D-97C6-0B645AC566A2
  183.  
  184.          An error event occurred.  EventID: 0xC0000FAC
  185.  
  186.             Time Generated: 09/06/2017   09:55:54
  187.  
  188.             Event String:
  189.  
  190.             The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 782 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
  191.  
  192.              
  193.  
  194.             To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.
  195.  
  196.              
  197.  
  198.             Additional Information:
  199.  
  200.             Error: 9061 (The replicated folder has been offline for too long.)
  201.  
  202.             Replicated Folder Name: SYSVOL Share
  203.  
  204.             Replicated Folder ID: 6608D239-9FD6-4CC2-8231-58C9601DF369
  205.  
  206.             Replication Group Name: Domain System Volume
  207.  
  208.             Replication Group ID: E8EFEA5C-DB12-4FFE-9126-9EE491A9FC32
  209.  
  210.             Member ID: 66A4FFDA-F573-484D-97C6-0B645AC566A2
  211.  
  212.          An error event occurred.  EventID: 0xC0000FAC
  213.  
  214.             Time Generated: 09/06/2017   11:03:02
  215.  
  216.             Event String:
  217.  
  218.             The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 782 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
  219.  
  220.              
  221.  
  222.             To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.
  223.  
  224.              
  225.  
  226.             Additional Information:
  227.  
  228.             Error: 9061 (The replicated folder has been offline for too long.)
  229.  
  230.             Replicated Folder Name: SYSVOL Share
  231.  
  232.             Replicated Folder ID: 6608D239-9FD6-4CC2-8231-58C9601DF369
  233.  
  234.             Replication Group Name: Domain System Volume
  235.  
  236.             Replication Group ID: E8EFEA5C-DB12-4FFE-9126-9EE491A9FC32
  237.  
  238.             Member ID: 66A4FFDA-F573-484D-97C6-0B645AC566A2
  239.  
  240.          ......................... PrimaryDC failed test DFSREvent
  241.  
  242.       Starting test: SysVolCheck
  243.  
  244.          * The File Replication Service SYSVOL ready test
  245.          File Replication Service's SYSVOL is ready
  246.          ......................... PrimaryDC passed test SysVolCheck
  247.  
  248.       Starting test: FrsSysVol
  249.  
  250.          * The File Replication Service SYSVOL ready test
  251.          File Replication Service's SYSVOL is ready
  252.          ......................... PrimaryDC passed test FrsSysVol
  253.  
  254.       Starting test: KccEvent
  255.  
  256.          * The KCC Event log test
  257.          Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
  258.          ......................... PrimaryDC passed test KccEvent
  259.  
  260.       Starting test: KnowsOfRoleHolders
  261.  
  262.          Role Schema Owner = CN=NTDS Settings,CN=PrimaryDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com
  263.          Role Domain Owner = CN=NTDS Settings,CN=PrimaryDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com
  264.          Role PDC Owner = CN=NTDS Settings,CN=PrimaryDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com
  265.          Role Rid Owner = CN=NTDS Settings,CN=PrimaryDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com
  266.          Role Infrastructure Update Owner = CN=NTDS Settings,CN=PrimaryDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com
  267.          ......................... PrimaryDC passed test KnowsOfRoleHolders
  268.  
  269.       Starting test: MachineAccount
  270.  
  271.          Checking machine account for DC PrimaryDC on DC PrimaryDC.
  272.          * SPN found :LDAP/PrimaryDC.TL.domain.com/TL.domain.com
  273.          * SPN found :LDAP/PrimaryDC.TL.domain.com
  274.          * SPN found :LDAP/PrimaryDC
  275.          * SPN found :LDAP/PrimaryDC.TL.domain.com/TL
  276.          * SPN found :LDAP/4f38725e-281d-4077-8806-f0e6a6f86ff9._msdcs.TL.domain.com
  277.          * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/4f38725e-281d-4077-8806-f0e6a6f86ff9/TL.domain.com
  278.          * SPN found :HOST/PrimaryDC.TL.domain.com/TL.domain.com
  279.          * SPN found :HOST/PrimaryDC.TL.domain.com
  280.          * SPN found :HOST/PrimaryDC
  281.          * SPN found :HOST/PrimaryDC.TL.domain.com/TL
  282.          * SPN found :GC/PrimaryDC.TL.domain.com/TL.domain.com
  283.          ......................... PrimaryDC passed test MachineAccount
  284.  
  285.       Starting test: NCSecDesc
  286.  
  287.          * Security Permissions check for all NC's on DC PrimaryDC.
  288.          * Security Permissions Check for
  289.  
  290.            DC=ForestDnsZones,DC=TL,DC=domain,DC=com
  291.             (NDNC,Version 3)
  292.          * Security Permissions Check for
  293.  
  294.            DC=DomainDnsZones,DC=TL,DC=domain,DC=com
  295.             (NDNC,Version 3)
  296.          * Security Permissions Check for
  297.  
  298.            CN=Schema,CN=Configuration,DC=TL,DC=domain,DC=com
  299.             (Schema,Version 3)
  300.          * Security Permissions Check for
  301.  
  302.            CN=Configuration,DC=TL,DC=domain,DC=com
  303.             (Configuration,Version 3)
  304.          * Security Permissions Check for
  305.  
  306.            DC=TL,DC=domain,DC=com
  307.             (Domain,Version 3)
  308.          ......................... PrimaryDC passed test NCSecDesc
  309.  
  310.       Starting test: NetLogons
  311.  
  312.          * Network Logons Privileges Check
  313.          Verified share \\PrimaryDC\netlogon
  314.          Verified share \\PrimaryDC\sysvol
  315.          ......................... PrimaryDC passed test NetLogons
  316.  
  317.       Starting test: ObjectsReplicated
  318.  
  319.          PrimaryDC is in domain DC=TL,DC=domain,DC=com
  320.          Checking for CN=PrimaryDC,OU=Domain Controllers,DC=TL,DC=domain,DC=com in domain DC=TL,DC=domain,DC=com on 1 servers
  321.             Object is up-to-date on all servers.
  322.          Checking for CN=NTDS Settings,CN=PrimaryDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com in domain CN=Configuration,DC=TL,DC=domain,DC=com on 1 servers
  323.             Object is up-to-date on all servers.
  324.          ......................... PrimaryDC passed test ObjectsReplicated
  325.  
  326.       Starting test: OutboundSecureChannels
  327.  
  328.          * The Outbound Secure Channels test
  329.          ** Did not run Outbound Secure Channels test because /testdomain: was
  330.  
  331.          not entered
  332.  
  333.          ......................... PrimaryDC passed test OutboundSecureChannels
  334.  
  335.       Starting test: Replications
  336.  
  337.          * Replications Check
  338.          * Replication Latency Check
  339.             DC=ForestDnsZones,DC=TL,DC=domain,DC=com
  340.                Latency information for 9 entries in the vector were ignored.
  341.                   9 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).  
  342.             DC=DomainDnsZones,DC=TL,DC=domain,DC=com
  343.                Latency information for 9 entries in the vector were ignored.
  344.                   9 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).  
  345.             CN=Schema,CN=Configuration,DC=TL,DC=domain,DC=com
  346.                Latency information for 9 entries in the vector were ignored.
  347.                   9 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).  
  348.             CN=Configuration,DC=TL,DC=domain,DC=com
  349.                Latency information for 9 entries in the vector were ignored.
  350.                   9 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).  
  351.             DC=TL,DC=domain,DC=com
  352.                Latency information for 9 entries in the vector were ignored.
  353.                   9 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).  
  354.          ......................... PrimaryDC passed test Replications
  355.  
  356.       Starting test: RidManager
  357.  
  358.          * Available RID Pool for the Domain is 7603 to 1073741823
  359.          * PrimaryDC.TL.domain.com is the RID Master
  360.          * DsBind with RID Master was successful
  361.          * rIDAllocationPool is 7103 to 7602
  362.          * rIDPreviousAllocationPool is 7103 to 7602
  363.          * rIDNextRID: 7105
  364.          ......................... PrimaryDC passed test RidManager
  365.  
  366.       Starting test: Services
  367.  
  368.          * Checking Service: EventSystem
  369.          * Checking Service: RpcSs
  370.          * Checking Service: NTDS
  371.          * Checking Service: DnsCache
  372.          * Checking Service: DFSR
  373.          * Checking Service: IsmServ
  374.          * Checking Service: kdc
  375.          * Checking Service: SamSs
  376.          * Checking Service: LanmanServer
  377.          * Checking Service: LanmanWorkstation
  378.          * Checking Service: w32time
  379.          * Checking Service: NETLOGON
  380.          ......................... PrimaryDC passed test Services
  381.  
  382.       Starting test: SystemLog
  383.  
  384.          * The System Event log test
  385.          A warning event occurred.  EventID: 0x00000024
  386.  
  387.             Time Generated: 09/06/2017   14:10:19
  388.  
  389.             Event String:
  390.  
  391.             The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
  392.  
  393.          A warning event occurred.  EventID: 0x000003F6
  394.  
  395.             Time Generated: 09/06/2017   14:13:14
  396.  
  397.             Event String:
  398.  
  399.             Name resolution for the name fma.lesolsoncompany.com timed out after none of the configured DNS servers responded.
  400.  
  401.          An error event occurred.  EventID: 0x0000272C
  402.  
  403.             Time Generated: 09/06/2017   15:01:43
  404.  
  405.             Event String:
  406.  
  407.             DCOM was unable to communicate with the computer 192.168.0.1 using any of the configured protocols; requested by PID     2edc (C:\Windows\system32\dcdiag.exe).
  408.  
  409.          An error event occurred.  EventID: 0x0000272C
  410.  
  411.             Time Generated: 09/06/2017   15:04:35
  412.  
  413.             Event String:
  414.  
  415.             DCOM was unable to communicate with the computer 192.168.0.1 using any of the configured protocols; requested by PID     1e58 (C:\Windows\system32\dcdiag.exe).
  416.  
  417.          ......................... PrimaryDC failed test SystemLog
  418.  
  419.       Starting test: Topology
  420.  
  421.          * Configuration Topology Integrity Check
  422.          * Analyzing the connection topology for DC=ForestDnsZones,DC=TL,DC=domain,DC=com.
  423.          * Performing upstream (of target) analysis.
  424.          * Performing downstream (of target) analysis.
  425.          * Analyzing the connection topology for DC=DomainDnsZones,DC=TL,DC=domain,DC=com.
  426.          * Performing upstream (of target) analysis.
  427.          * Performing downstream (of target) analysis.
  428.          * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=TL,DC=domain,DC=com.
  429.          * Performing upstream (of target) analysis.
  430.          * Performing downstream (of target) analysis.
  431.          * Analyzing the connection topology for CN=Configuration,DC=TL,DC=domain,DC=com.
  432.          * Performing upstream (of target) analysis.
  433.          * Performing downstream (of target) analysis.
  434.          * Analyzing the connection topology for DC=TL,DC=domain,DC=com.
  435.          * Performing upstream (of target) analysis.
  436.          * Performing downstream (of target) analysis.
  437.          ......................... PrimaryDC passed test Topology
  438.  
  439.       Starting test: VerifyEnterpriseReferences
  440.  
  441.          ......................... PrimaryDC passed test VerifyEnterpriseReferences
  442.  
  443.       Starting test: VerifyReferences
  444.  
  445.          The system object reference (serverReference)
  446.  
  447.          CN=PrimaryDC,OU=Domain Controllers,DC=TL,DC=domain,DC=com and backlink
  448.  
  449.          on
  450.  
  451.          CN=PrimaryDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com
  452.  
  453.          are correct.
  454.          The system object reference (serverReferenceBL)
  455.  
  456.          CN=PrimaryDC,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=TL,DC=domain,DC=com
  457.  
  458.          and backlink on
  459.  
  460.          CN=NTDS Settings,CN=PrimaryDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=TL,DC=domain,DC=com
  461.  
  462.          are correct.
  463.          The system object reference (msDFSR-ComputerReferenceBL)
  464.  
  465.          CN=PrimaryDC,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=TL,DC=domain,DC=com
  466.  
  467.          and backlink on
  468.  
  469.          CN=PrimaryDC,OU=Domain Controllers,DC=TL,DC=domain,DC=com are correct.
  470.          ......................... PrimaryDC passed test VerifyReferences
  471.  
  472.       Starting test: VerifyReplicas
  473.  
  474.          ......................... PrimaryDC passed test VerifyReplicas
  475.  
  476.    
  477.       Starting test: DNS
  478.  
  479.          
  480.  
  481.          DNS Tests are running and not hung. Please wait a few minutes...
  482.  
  483.          See DNS test in enterprise tests section for results
  484.          ......................... PrimaryDC passed test DNS
  485.  
  486.    
  487.    Running partition tests on : ForestDnsZones
  488.  
  489.       Starting test: CheckSDRefDom
  490.  
  491.          ......................... ForestDnsZones passed test CheckSDRefDom
  492.  
  493.       Starting test: CrossRefValidation
  494.  
  495.          ......................... ForestDnsZones passed test
  496.  
  497.          CrossRefValidation
  498.  
  499.    
  500.    Running partition tests on : DomainDnsZones
  501.  
  502.       Starting test: CheckSDRefDom
  503.  
  504.          ......................... DomainDnsZones passed test CheckSDRefDom
  505.  
  506.       Starting test: CrossRefValidation
  507.  
  508.          ......................... DomainDnsZones passed test
  509.  
  510.          CrossRefValidation
  511.  
  512.    
  513.    Running partition tests on : Schema
  514.  
  515.       Starting test: CheckSDRefDom
  516.  
  517.          ......................... Schema passed test CheckSDRefDom
  518.  
  519.       Starting test: CrossRefValidation
  520.  
  521.          ......................... Schema passed test CrossRefValidation
  522.  
  523.    
  524.    Running partition tests on : Configuration
  525.  
  526.       Starting test: CheckSDRefDom
  527.  
  528.          ......................... Configuration passed test CheckSDRefDom
  529.  
  530.       Starting test: CrossRefValidation
  531.  
  532.          ......................... Configuration passed test CrossRefValidation
  533.  
  534.    
  535.    Running partition tests on : TL
  536.  
  537.       Starting test: CheckSDRefDom
  538.  
  539.          ......................... TL passed test CheckSDRefDom
  540.  
  541.       Starting test: CrossRefValidation
  542.  
  543.          ......................... TL passed test CrossRefValidation
  544.  
  545.    
  546.    Running enterprise tests on : TL.domain.com
  547.  
  548.       Starting test: DNS
  549.  
  550.          Test results for domain controllers:
  551.  
  552.            
  553.             DC: PrimaryDC.TL.domain.com
  554.  
  555.             Domain: TL.domain.com
  556.  
  557.            
  558.  
  559.                  
  560.                TEST: Authentication (Auth)
  561.                   Authentication test: Successfully completed
  562.                  
  563.                TEST: Basic (Basc)
  564.                   The OS
  565.  
  566.                   Microsoft Windows Server 2012 R2 Standard (Service Pack level: 0.0)
  567.  
  568.                   is supported.
  569.  
  570.                   NETLOGON service is running
  571.  
  572.                   kdc service is running
  573.  
  574.                   DNSCACHE service is running
  575.  
  576.                   DNS service is running
  577.  
  578.                   DC is a DNS server
  579.  
  580.                   Network adapters information:
  581.  
  582.                   Adapter
  583.  
  584.                   [00000019] Microsoft Network Adapter Multiplexor Driver:
  585.  
  586.                      MAC address is BC:5F:F4:C9:8A:39
  587.                      IP Address is static
  588.                      IP address: 192.168.3.1
  589.                      DNS servers:
  590.  
  591.                         192.168.3.1 (PrimaryDC) [Valid]
  592.                   The A host record(s) for this DC was found
  593.                   The SOA record for the Active Directory zone was found
  594.                   The Active Directory zone on this DC/DNS server was found primary
  595.                   Root zone on this DC/DNS server was not found
  596.                  
  597.                TEST: Forwarders/Root hints (Forw)
  598.                   Recursion is enabled
  599.                   Forwarders Information:
  600.                      192.168.0.1 (<name unavailable>) [Valid]
  601.                  
  602.                TEST: Delegations (Del)
  603.                   No delegations were found in this zone on this DNS server
  604.                  
  605.                TEST: Dynamic update (Dyn)
  606.                   Test record dcdiag-test-record added successfully in zone TL.domain.com
  607.                   Test record dcdiag-test-record deleted successfully in zone TL.domain.com
  608.                  
  609.                TEST: Records registration (RReg)
  610.                   Network Adapter
  611.  
  612.                   [00000019] Microsoft Network Adapter Multiplexor Driver:
  613.  
  614.                      Matching CNAME record found at DNS server 192.168.3.1:
  615.                      4f38725e-281d-4077-8806-f0e6a6f86ff9._msdcs.TL.domain.com
  616.  
  617.                      Matching A record found at DNS server 192.168.3.1:
  618.                      PrimaryDC.TL.domain.com
  619.  
  620.                      Matching  SRV record found at DNS server 192.168.3.1:
  621.                      _ldap._tcp.TL.domain.com
  622.  
  623.                      Matching  SRV record found at DNS server 192.168.3.1:
  624.                      _ldap._tcp.b6889a48-cad1-4dea-8023-30ba41fb7464.domains._msdcs.TL.domain.com
  625.  
  626.                      Matching  SRV record found at DNS server 192.168.3.1:
  627.                      _kerberos._tcp.dc._msdcs.TL.domain.com
  628.  
  629.                      Matching  SRV record found at DNS server 192.168.3.1:
  630.                      _ldap._tcp.dc._msdcs.TL.domain.com
  631.  
  632.                      Matching  SRV record found at DNS server 192.168.3.1:
  633.                      _kerberos._tcp.TL.domain.com
  634.  
  635.                      Matching  SRV record found at DNS server 192.168.3.1:
  636.                      _kerberos._udp.TL.domain.com
  637.  
  638.                      Matching  SRV record found at DNS server 192.168.3.1:
  639.                      _kpasswd._tcp.TL.domain.com
  640.  
  641.                      Matching  SRV record found at DNS server 192.168.3.1:
  642.                      _ldap._tcp.Default-First-Site-Name._sites.TL.domain.com
  643.  
  644.                      Matching  SRV record found at DNS server 192.168.3.1:
  645.                      _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.TL.domain.com
  646.  
  647.                      Matching  SRV record found at DNS server 192.168.3.1:
  648.                      _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.TL.domain.com
  649.  
  650.                      Matching  SRV record found at DNS server 192.168.3.1:
  651.                      _kerberos._tcp.Default-First-Site-Name._sites.TL.domain.com
  652.  
  653.                      Matching  SRV record found at DNS server 192.168.3.1:
  654.                      _ldap._tcp.gc._msdcs.TL.domain.com
  655.  
  656.                      Matching A record found at DNS server 192.168.3.1:
  657.                      gc._msdcs.TL.domain.com
  658.  
  659.                      Matching  SRV record found at DNS server 192.168.3.1:
  660.                      _gc._tcp.Default-First-Site-Name._sites.TL.domain.com
  661.  
  662.                      Matching  SRV record found at DNS server 192.168.3.1:
  663.                      _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.TL.domain.com
  664.  
  665.                      Matching  SRV record found at DNS server 192.168.3.1:
  666.                      _ldap._tcp.pdc._msdcs.TL.domain.com
  667.  
  668.          
  669.          Summary of test results for DNS servers used by the above domain
  670.  
  671.          controllers:
  672.  
  673.          
  674.  
  675.             DNS server: 192.168.0.1 (<name unavailable>)
  676.  
  677.                All tests passed on this DNS server
  678.  
  679.                
  680.             DNS server: 192.168.3.1 (PrimaryDC)
  681.  
  682.                All tests passed on this DNS server
  683.  
  684.                Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
  685.                
  686.          Summary of DNS test results:
  687.  
  688.          
  689.                                             Auth Basc Forw Del  Dyn  RReg Ext
  690.             _________________________________________________________________
  691.             Domain: TL.domain.com
  692.  
  693.                PrimaryDC                         PASS PASS PASS PASS PASS PASS n/a  
  694.          
  695.          ......................... TL.domain.com passed test DNS
  696.  
  697.       Starting test: LocatorCheck
  698.  
  699.          GC Name: \\PrimaryDC.TL.domain.com
  700.  
  701.          Locator Flags: 0xe000f3fd
  702.          PDC Name: \\PrimaryDC.TL.domain.com
  703.          Locator Flags: 0xe000f3fd
  704.          Time Server Name: \\PrimaryDC.TL.domain.com
  705.          Locator Flags: 0xe000f3fd
  706.          Preferred Time Server Name: \\PrimaryDC.TL.domain.com
  707.          Locator Flags: 0xe000f3fd
  708.          KDC Name: \\PrimaryDC.TL.domain.com
  709.          Locator Flags: 0xe000f3fd
  710.          ......................... TL.domain.com passed test LocatorCheck
  711.  
  712.       Starting test: FsmoCheck
  713.  
  714.          GC Name: \\PrimaryDC.TL.domain.com
  715.  
  716.          Locator Flags: 0xe000f3fd
  717.          PDC Name: \\PrimaryDC.TL.domain.com
  718.          Locator Flags: 0xe000f3fd
  719.          Time Server Name: \\PrimaryDC.TL.domain.com
  720.          Locator Flags: 0xe000f3fd
  721.          Preferred Time Server Name: \\PrimaryDC.TL.domain.com
  722.          Locator Flags: 0xe000f3fd
  723.          KDC Name: \\PrimaryDC.TL.domain.com
  724.          Locator Flags: 0xe000f3fd
  725.          ......................... TL.domain.com passed test FsmoCheck
  726.  
  727.       Starting test: Intersite
  728.  
  729.          Skipping site Default-First-Site-Name, this site is outside the scope
  730.  
  731.          provided by the command line arguments provided.
  732.          ......................... TL.domain.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!