Error determining whether the target server is already a domain controller: The target server is already a Domain Controller.

I was trying to add a new Windows 2012R2 Domain controller to an existing Domain. I was using the GUI tools, may be I should do this with PowerShell the next time. After adding the AD and DNS role I went through the DCPROMO wizard dcpromoand kicked off the promotion. After a manual reboot I checked and all of DNS and AD seems to be working fine including replication. However, I’m still being prompted in the Server Manager to promote the server. When I do the following messages is displayed – “Error determining whether the target server is already a domain controller: The target server is already a Domain Controller.” After some research it looks like I’m not the only one, check out these posts. First thing always, run DCDIAG. The output only confirms that everything seems to be working. The solution seems to be to just disable/acknowledge the notification by clicking the “x” beside the task. Even after a reboot the notification doesn’t come up anymore.

dcpromoclick

 

 

 

 

 

  1. Directory Server Diagnosis
  2.  
  3.  
  4. Performing initial setup:
  5.  
  6. Trying to find home server...
  7.  
  8. Home Server = SRV-ADC-01
  9.  
  10. * Identified AD Forest.
  11. Done gathering initial info.
  12.  
  13.  
  14. Doing initial required tests
  15.  
  16.  
  17. Testing server: IEGW\SRV-ADC-01
  18.  
  19. Starting test: Connectivity
  20.  
  21. ......................... SRV-ADC-01 passed test Connectivity
  22.  
  23.  
  24.  
  25. Doing primary tests
  26.  
  27.  
  28. Testing server: IEGW\SRV-ADC-01
  29.  
  30. Starting test: Advertising
  31.  
  32. ......................... SRV-ADC-01 passed test Advertising
  33.  
  34. Starting test: FrsEvent
  35.  
  36. There are warning or error events within the last 24 hours after the
  37.  
  38. SYSVOL has been shared. Failing SYSVOL replication problems may cause
  39.  
  40. Group Policy problems.
  41. ......................... SRV-ADC-01 passed test FrsEvent
  42.  
  43. Starting test: DFSREvent
  44.  
  45. ......................... SRV-ADC-01 passed test DFSREvent
  46.  
  47. Starting test: SysVolCheck
  48.  
  49. ......................... SRV-ADC-01 passed test SysVolCheck
  50.  
  51. Starting test: KccEvent
  52.  
  53. ......................... SRV-ADC-01 passed test KccEvent
  54.  
  55. Starting test: KnowsOfRoleHolders
  56.  
  57. ......................... SRV-ADC-01 passed test KnowsOfRoleHolders
  58.  
  59. Starting test: MachineAccount
  60.  
  61. ......................... SRV-ADC-01 passed test MachineAccount
  62.  
  63. Starting test: NCSecDesc
  64.  
  65. ......................... SRV-ADC-01 passed test NCSecDesc
  66.  
  67. Starting test: NetLogons
  68.  
  69. ......................... SRV-ADC-01 passed test NetLogons
  70.  
  71. Starting test: ObjectsReplicated
  72.  
  73. ......................... SRV-ADC-01 passed test ObjectsReplicated
  74.  
  75. Starting test: Replications
  76.  
  77. ......................... SRV-ADC-01 passed test Replications
  78.  
  79. Starting test: RidManager
  80.  
  81. ......................... SRV-ADC-01 passed test RidManager
  82.  
  83. Starting test: Services
  84.  
  85. ......................... SRV-ADC-01 passed test Services
  86.  
  87. Starting test: SystemLog
  88.  
  89. ......................... SRV-ADC-01 passed test SystemLog
  90.  
  91. Starting test: VerifyReferences
  92.  
  93. ......................... SRV-ADC-01 passed test VerifyReferences
  94.  
  95.  
  96.  
  97. Running partition tests on : ForestDnsZones
  98.  
  99. Starting test: CheckSDRefDom
  100.  
  101. ......................... ForestDnsZones passed test CheckSDRefDom
  102.  
  103. Starting test: CrossRefValidation
  104.  
  105. ......................... ForestDnsZones passed test
  106.  
  107. CrossRefValidation
  108.  
  109.  
  110. Running partition tests on : DomainDnsZones
  111.  
  112. Starting test: CheckSDRefDom
  113.  
  114. ......................... DomainDnsZones passed test CheckSDRefDom
  115.  
  116. Starting test: CrossRefValidation
  117.  
  118. ......................... DomainDnsZones passed test
  119.  
  120. CrossRefValidation
  121.  
  122.  
  123. Running partition tests on : Schema
  124.  
  125. Starting test: CheckSDRefDom
  126.  
  127. ......................... Schema passed test CheckSDRefDom
  128.  
  129. Starting test: CrossRefValidation
  130.  
  131. ......................... Schema passed test CrossRefValidation
  132.  
  133.  
  134. Running partition tests on : Configuration
  135.  
  136. Starting test: CheckSDRefDom
  137.  
  138. ......................... Configuration passed test CheckSDRefDom
  139.  
  140. Starting test: CrossRefValidation
  141.  
  142. ......................... Configuration passed test CrossRefValidation
  143.  
  144.  
  145. Running partition tests on : DOMAIN
  146.  
  147. Starting test: CheckSDRefDom
  148.  
  149. ......................... DOMAIN passed test CheckSDRefDom
  150.  
  151. Starting test: CrossRefValidation
  152.  
  153. ......................... DOMAIN passed test CrossRefValidation
  154.  
  155.  
  156. Running enterprise tests on : DOMAIN.INC
  157.  
  158. Starting test: LocatorCheck
  159.  
  160. ......................... DOMAIN.INC passed test LocatorCheck
  161.  
  162. Starting test: Intersite
  163.  
  164. ......................... DOMAIN.INC passed test Intersite

 

Pages: 1 | 2 | Multi-Page

2 comments

  1. I had the same error message after promoting a Server in Microsoft Azure (separate AD Site) to a Domain Controller. I first also had some troubles with DNS (because of entries of the old AD Controller) and Sysvol was not successfully replicated to this server (got this trough DCDiag). After solving that, a few manual “Replicate now” on AD Sites and Services and 3 Reboots of the Server, this message disappeared from Server Manager by itself. I didn’t deactivate the message like RZM wrote. So I figure, you could solve that, but maybe in RMZ’s Case he should also just have rebooted the server one or two more times.

    Reply
    • If I remember correctly I did reboot the server at least once and checked the eventlogs and replication to see if anything was out of place. It appears the same steps to troubleshoot/check apply and this messages can be misleading.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *