No SysVol or Netlogon

[T_Lister]

Greetings forum,

 

I have been attempted to promote a DC onto an existing domain, however it won't generate the SysVol or Netlogon. This is a huge problem as I am wanting to transfer the FSMO and shut down the old server.

 

Setup:

Existing DC is 2012 - Physical Server

Operation Level is 2012

First DC I attempted to promote was 2019 (I have bridged this gap before at another school) (VM)

I've tried a second 2019 server (VM)

I've also built and tried a 2016 server (VM), none of these will generate the Sysvol etc.

 

All the research I've done talks about non authorative and authorative restores, which I am not too familar with. Is this the only way or am I missing something? The fault I presume must be on the 2012 DC. All the VMs I've tried are on the new physical box.

 

Thanks in advance.

[DJ-1701]

Could this be the issue?

 

https://www.sikich.com/insight/frs-to-dfsr-migration-on-domain-controllers/

[Boredguy]

It's not related to the same domain you had issues with back in 2018 was it (http://www.edugeek.net/forums/windows-server-2012/193421-rid-replication-failure.html#post1652886) ?

[T_Lister]

Differnet school.

[T_Lister]

Could this be the issue?

 

https://www.sikich.com/insight/frs-to-dfsr-migration-on-domain-controllers/

 

/Getflobalstate says Eliminated. I believe this meanse I'm on DFSR?

[DJ-1701]

/Getflobalstate says Eliminated. I believe this meanse I'm on DFSR?

 

That's correct, so that's not the issue.

[djm968]

Anything in the event logs? Most DC promo issues I've seen have been DNS related. Any issues reported when you run dcdiag tests?

[T_Lister]

Will look into the meaning of this now, hadn't really looked until now. I was doing this work before Christmas. This error seems to have been cropping up for some time, since before we were supporting the school:

 

The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

[djm968]

Could be that another DC has been previously removed without being properly demoted and AD replication is failing.

[T_Lister]

That's what I'm beginning to think from what I'm reading. Looking at doing the authorative sync:

 

https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

 

If I shouldn't give this a go do stop me. Job for tomorrow though. I've just demoted the new DC to ensure that the physical is now the only one running.

[T_Lister]

That seems to have done the trick. Previous IT Support didn't pass all the roles across properly. Christmas break seemed to be what I needed. Thanks all.