Sunday, November 25, 2012 9:30 PM
I had a Windows Server 8 Beta domain controller running just fine, and came in to upgrade to Windows Server 2012 Standard. Of course, this has to be a fresh install from beta. Server install works fine, but when I install AD and make the Domain Controller, I cannot access any AD controls. I get errors "The specified name either does not exist or could not be contacted". AD Service Center shows the domain (local) as offline, and cannot be brought online.
I read something about Sysvol and Netlogon not being shared properly, and about DNS not being correctly set up, but I'm not sure which direction to go. Neither of these was an issue when I installed the beta, so I'm not sure why I'm having problems with this. Of course, this is urgent.
Thanks for any pointers. I'll be glad to post any requested information.
Monday, November 26, 2012 4:44 AMModerator
Yes, you're correct, the issue occurs probably because Sysvol direcotry is not shared out or DNS is not configured correctly. You can use net share command to check if SYSVOL share is showing, and use dcdiag /test:dns to check DNS settings. Use dcdiag /v /c to check the health of your domain.
Please follow this to configure DNS settings in your domain:
Best practices for DNS client settings on Domain Controller and Domain members.
Below link might also be helpful:
Introducing the first Windows Server 2012 Domain Controller (Part 1 of 2)
- Marked As Answer by Cicely FengMicrosoft Contingent Staff, Moderator Tuesday, December 04, 2012 7:16 AM