Group Policy new server

[scotyboy56]

I have added a new server (2012R2) to the domain and taken all the roles from the old server (2008R2). So the new server is in charge of everything as far as I can tell. However it doesn't have the netlogon share. Also when I try to open Group Policy on the new server it says "The System cannot find the Path Specified"

 

Any ideas?

 

Thanks

[tmcd35]

Have you completely removed the old server from the network? It sounds like it hasn't replicated properly. If the old server is still on the domain, still joined to the network, then you need to look for replication errors in your event logs, or just give it time to replicate.

 

If the old server is gone, then you want help from someone more knowledgeable than me. My guess would be to restore System Settings from a recent backup? (but don't quote me on that). Depending on the state of the old server, have you run DCPROMO on it to demote it?, I'd be tempted to revert everything back to the old server, make sure everything is 100% perfect there, and then rebuild the new server from scratch.

[scotyboy56]

Have you completely removed the old server from the network? It sounds like it hasn't replicated properly. If the old server is still on the domain, still joined to the network, then you need to look for replication errors in your event logs, or just give it time to replicate.

Nope the old server is still part of the domain, just has none of the fsmo roles etc. Shall have a look at the replication stuff, what should it be replicating though?

 

Thanks

[pantscat]

How recently did you promote the 2012 machine? Replication can take a little while depending upon the size of your sysvol share.

 

Use dcdiag from a command prompt on both DCs to look for any potential issues - it'll flag up any problems.

[Domino]

It could be you're using FRS for sysvol replication, and that's been depreciated in 2012 R2 https://technet.microsoft.com/en-us/library/hh831487.aspx

 

If so I feel a move to DFSR in the near future... The Case for Migrating SYSVOL to DFSR - Ask the Directory Services Team - Site Home - TechNet Blogs

[scotyboy56]

How recently did you promote the 2012 machine? Replication can take a little while depending upon the size of your sysvol share.

 

Use dcdiag from a command prompt on both DCs to look for any potential issues - it'll flag up any problems.

 

over a week ago, thanks shall try that

[pantscat]

This could be useful for you: https://www.microsoft.com/en-us/download/details.aspx?id=30005

 

- - - Updated - - -

 

over a week ago, thanks shall try that

 

Wouldn't take that long!

[ITGURU]

I recall this may have happened to us on server 2003 where we had to change a registry setting which re-created the sysvol share.

Check event logs and run the replication monitor command for any errors and last sync time.

 

Check the FSMO roles are all transferred to a valid server

- Check if the demoted server is removed in AD Sites and services.

- Make sure GPO management console is applied

- Assume the AD wizard was successful when promoted?

- Check DNS Settings are correct.

[Chuckster]

Did you raise the domain functional level (assuming you no longer have any 2008 R2 DC servers)?

[3s-gtech]

Check that the jet database is working properly. This will show in your event logs, and if it's at fault the syntax of the fix is included in the log. This issue doesn't affect 2012 and 2012 R2 DCs but does affect 2008 R2 so could still be the cause.

[mikkydoos]

Have a look at this thread... might help.

 

http://www.edugeek.net/forums/windows-server-2012/154461-group-policy-only-applying-if-2003-dcs-still-switched-4.html#post1325960