1

I'm having some very weird issues with migrating my 2012 Domain Controller to a new 2016 server. Most articles I have read state that all I need to do a set up the 2016 server as a Domain Controller and move the FSMO roles... then when all looks good, I can remove the Domain Controller on 2012. Well this certainly was not the case for me. DCDiag on the 2016 server is showing this:

Starting test: Advertising
   Warning: DsGetDcName returned information for \\ds1.dir
   reach DS2.
   SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
   ......................... DS2 failed test Advertising

Starting test: NetLogons
   Unable to connect to the NETLOGON share! (\\DS2\netlog
   [DS2] An net use or LsaPolicy operation failed with er
   ......................... DS2 failed test NetLogons

I found the following article that seems like it would help my case: https://blogs.technet.microsoft.com/ziggy/2013/08/20/sysvol-on-newly-promoted-dc-is-not-synchronising-but-replication-looks-ok/

I am currently trying to add the Administrators group to the "Default Domain Policy", which is explained in this article: https://support.microsoft.com/en-us/help/2567421/dfsr-sysvol-fails-to-migrate-or-replicate,-sysvol-not-shared,-event-ids-8028-or-6016

When I add the group, GPMC returns this error: "the system cannot find the path specified"

I'm really not sure what to do from here. I had to remove DNS from the 2012 server because it was giving issues with my new 2016 DC. I cannot demote the 2012 DC because it is telling me it cannot contact the other DC. I'm afraid to touch anything in fear of losing my whole directory.

Thanks for any help you can provide!

Improve this question
7
  • 1
    If you've removed DNS from your only functioning DC then you're probably in a spot of trouble. What are your DNS settings? You should have your new DC pointing at your functioning DC to start with, then to itself once it's functional.
    – john
    Jun 22, 2017 at 21:36
  • Well DNS is running on the 2016 sever and seems to be functional. I have bind set up to forward any DNS requests for directory.Company.com to the 2016 server. We are a pure Mac shop so I'm not worried about anything but my active directory users and groups. Would it help if I added DNS back to the 2012 server?
    – Intrepid
    Jun 22, 2017 at 22:52
  • I should also mention that everything appears to be working fine as far as my clients go... Despite having weird issues with both domain controllers.
    – Intrepid
    Jun 23, 2017 at 0:57
  • DNS is fairly fundamental to the correct operation of a domain controller, so you should definitely add it back on, at least until after you have demoted it.
    – john
    Jun 23, 2017 at 5:53
  • Ok DNS has been reinstalled on Server 2012 and it looks like it has all my domain DNS stuff in it. Both servers are pointing to the 2016 server for their DNS. What should I do now?
    – Intrepid
    Jun 23, 2017 at 13:43

1 Answer 1

Reset to default
2

I was able to fix all my issues by manually sharing my SYSVOL folder and then copying the SYSVOL folder from my 2012 DC to my 2016 DC. I then edited the GP to include the Administrators group. Then I edited this registry key:

Key  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\parameters
Value SysvolReady = 1

Then ran "gpupdate force" in powershell and everything was happy.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .