Server 2012 DC Promotion Bug

모든 응답

• 

  

  0

  로그인하여 투표

  Hello,

  please post a screen shot from "Server Manager still says that I need to Promote the server to a Domain Controller."

  You followed steps in http://msmvps.com/blogs/mweber/archive/2012/07/27/upgrading-an-active-directory-domain-from-windows-server-2008-or-windows-server-2008-r2-to-windows-server-2012.aspx

  ---

  Best regards

  Meinolf Weber
  MVP, MCP, MCTS
  Microsoft MVP - Directory Services
  My Blog: http://msmvps.com/blogs/mweber/

  Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

  2013년 4월 19일 금요일 오후 6:15
• 

  

  0

  로그인하여 투표

  Here's the screenshot of server manager you requested.  The article you posted isn't the one I followed to do the install, but I read through it and I definitely covered those steps.  I will also run the commands it suggests momentarily to verify schema and other settings.  I can also provide a screenshot of AD Users and Computers showing at this box is a DC if you like.

  

  2013년 4월 19일 금요일 오후 6:40
• 

  

  0

  로그인하여 투표

  Just to confirm the only thing I have not done that's in your article is transferring the FSMO roles to the 2012 DC, but I'm very hesitant to do this until I have this issue resolved - unless this is the very thing causing my issue.  I cannot find any documentation from MS to reflect this though.

  2013년 4월 19일 금요일 오후 6:52
• 

  

  0

  로그인하여 투표

  Hi,

  Have you performed the post deployment configuration successfully? Did you face any error?

  FYI- See this article if you missed any step: http://www.adshotgyan.com/2012/09/promoting-additional-domain-controller.html

  Please run netdom query dc to verify the DCs in the domain.

  Also check for any error in event log, DCPROMO log and run dcdiag /q for any error.

  ---

  Best regards,
  
  Abhijit Waikar.
  MCSA | MCSA:Messaging | MCITP:SA | MCC:2012
  Blog: http://abhijitw.wordpress.com
  Disclaimer: This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

  2013년 4월 19일 금요일 오후 7:00
• 

  

  0

  로그인하여 투표

  Abhijit,

  Running a netdom query dc does verify that the DC is listed as a domain controller.

  I did find something interesting in the dcpromo log though:

  04/18/2013 20:12:00 [INFO] EVENTLOG (Error): NTDS Replication / DS RPC Client : 2513
  Attempting to set the desired authentication protocol for a connection to the following DSA failed.
  
  
  DSA: 
  
  7331c678-0bd3-42fb-a8e7-9df2bccd1220._msdcs.WECARE.LOCAL
  
  
  
  Additional Data:
  
  Error:
  
  1747 The authentication service is unknown.
  
  
  04/18/2013 20:12:00 [WARNING] Non critical replication returned 1747
  04/18/2013 20:12:00 [INFO] Cleaning up old Netlogon information
  04/18/2013 20:12:01 [INFO] Stopped the DS
  04/18/2013 20:12:01 [INFO] Can't contact the service controller manager (1115)
  04/18/2013 20:12:01 [INFO] Configuring service NTDS to 16 returned 1115
  04/18/2013 20:12:01 [INFO] Error - Failed to configure the service NTDS as requested
   (1115)
  04/18/2013 20:12:01 [ERROR] Failed to configure the domain controller services (1115)
  04/18/2013 20:12:01 [INFO] DsRolepClearCachedCredentials returns with status 0xc00000fe, and protocol status is 0x00000000
  04/18/2013 20:12:01 [INFO] DsRolepSetDCLocatorPostPromoState: got 0 creating the DSROLEP_DCLOCATOR_PREREBOOT_HINT key
  04/18/2013 20:12:01 [ERROR] Failed to destroy the session with RALADS03.wecare.local: 0x8ca
  04/18/2013 20:12:01 [INFO] The attempted domain controller operation has completed
  04/18/2013 20:12:01 [INFO] Updating service status to 4
  04/18/2013 20:12:01 [INFO] DsRolepSetOperationDone returned 0

  2013년 4월 19일 금요일 오후 7:15
• 

  

  0

  로그인하여 투표

  Hello,

  what is shown when you run the mentioned "Promote this server to a domain controller"?

  ---

  Best regards

  Meinolf Weber
  MVP, MCP, MCTS
  Microsoft MVP - Directory Services
  My Blog: http://msmvps.com/blogs/mweber/

  Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

  • 답변으로 표시됨 ESUCP ITS 2013년 4월 19일 금요일 오후 9:02

  2013년 4월 19일 금요일 오후 8:22
• 

  

  0

  로그인하여 투표

  Meinolf, I clicked the "Promote this server to a domain controller" and got this:

  

  2013년 4월 19일 금요일 오후 8:27
• 

  

  0

  로그인하여 투표

  Annnnd that may have fixed it ladies and gents.  I am going to reboot to confirm - but since I clicked the above ^ and then clicked cancel, server manager is no longer showing the yellow "!" and telling me I need to promote it.  Will see if this persists through reboot and confirm.

  2013년 4월 19일 금요일 오후 8:34
• 

  

  4

  로그인하여 투표

  Fixed!

  So it seems we can chalk this up to a 'bug' of sorts after all.  Following reboot Server Manager is no longer complaining.

  To summarize this issue was resolved by:

  Clicking on the Yellow Caution indicator and clicking on the option to promote the server to a Domain Controller.
  Waiting for the error message, then clicking Cancel.  After this was done, Server Manager no longer prompts for
  the server to be promoted as a Domain Controller.

  Thanks everyone for contributing / taking a look at this.

  2013년 4월 19일 금요일 오후 9:02
• 

  

  0

  로그인하여 투표

  Glad to hear that the problem was fixed. Thanks for sharing your experience.

  TechNet Subscriber Support

  If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

  2013년 4월 22일 월요일 오전 2:09
• 

  

  0

  로그인하여 투표

  Thanks this post saved my bacon!  Its my turn to make dinner and I am running late as it is when I ran into this snag. 

  ---

  Kevin

  2014년 4월 23일 수요일 오후 10:27
• 

  

  0

  로그인하여 투표

   This is a total bug in 2012R2 after DC Promotion.  
  

  Clicking on the Yellow Caution indicator and clicking on the option to promote the server to a Domain Controller.
  

  Waiting for the error message, then clicking Cancel.  After this was done, Server Manager no longer prompts for
  the server to be promoted as a Domain Controller.

  WORKS!

  2015년 4월 2일 목요일 오후 8:57
• 

  

  0

  로그인하여 투표

  Ditto, I was glad to know it was a bug and not something I did. haha!

  2015년 11월 10일 화요일 오후 9:04
• 

  

  0

  로그인하여 투표

  Hello, What if server is rebooted during "replicating objects" step while promoting a server as domain controller? Thanks Ankush Gambhir

  2017년 12월 17일 일요일 오후 6:49
• 

  

  0

  로그인하여 투표

  So , 

  i currently have this issue with a 2016 Server as well. I hit cancel now, and the warning alert has gone away. 

  Just to get a bit of background on this. Were you doing a forced DC Demotion prior ? In my case, i was and when it came back up after the automatic reboot, the ADDS Services were still installed. I did a metadata cleanup on the DC it was replicating with. I am wondering, was i supposed to do any manual cleanup on the local server ? 
  

  Anyway, not to jump off topic, just wanted to see if your case was similar to mine.  
  

  2017년 12월 20일 수요일 오후 3:59
• 

  

  0

  로그인하여 투표

  Same here after promoting a 2012 R2 server into an existing domain. Replication was working fine and no errors in dcdiag, repadmin worked fine as well.

  Just needed to wait an hour and reboot 3 times before it showed that it was promoted succesfully.

  2018년 7월 27일 금요일 오전 7:16
• 

  

  0

  로그인하여 투표

  Hi, 

  I am having the same issue , 

  lets assume my PDC IP : setting:

  IP  192.168.55.2

  Mask: 255.255.255.0

  Default gateway: 192.168.55.5

  DNS1: 127.0.0.1

  DNS2: 192.168.55.3

  it's Windows server standard 2012

  My ADC 

  IP  192.168.55.3

  Mask: 255.255.255.0

  D gateway: 192.168.55.5

  DNS1: 127.0.0.1

  DNS2: 192.168.55.2

  Windows server standard 2016

  DFL: Windows server 2008

  FFL: Windows server 2008

  many restart attempts and steps to cancel then promote this server to a domain controller after server manager restart didnot work

  any reply or help would be highly appreciated , 

  2019년 12월 23일 월요일 오전 10:55