asked on
Group Policy Object. You might not have the appropriate rights?
I've recently transferred all the roles from an old SBS to 2012 R2 server and netdom query fsmo confirms they have all been transferred to the new server fine.
However when I try an edit old GPO's I get the Failed to open the Group Policy Object you might not have the appropriate rights - network name cannot be found.
If I open GPO on the old Server it still opens and I can edit them however I can see they are still tied to the old server name not the new.
Usually when I've transferred the roles before GPO shows the new Server name in the GPO Editor and I don't have this problem.
Also should I worry about Raising the domain functional level? it's currently set for Windows Server 2003 ( not sure if this really matters?)
Any recommendations how I can get all the GPO's transferred properly to the new Server?
Many Thanks in Advance
However when I try an edit old GPO's I get the Failed to open the Group Policy Object you might not have the appropriate rights - network name cannot be found.
If I open GPO on the old Server it still opens and I can edit them however I can see they are still tied to the old server name not the new.
Usually when I've transferred the roles before GPO shows the new Server name in the GPO Editor and I don't have this problem.
Also should I worry about Raising the domain functional level? it's currently set for Windows Server 2003 ( not sure if this really matters?)
Any recommendations how I can get all the GPO's transferred properly to the new Server?
Many Thanks in Advance
SBSWindows Server 2012* rolesActive Directory
Last Comment
Cliff Galiher
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I can see SYSVOL isn't even shared off of the new Server could it be something to do with this?
That's an unhealthy DC then. Sysvol and netlogon get shated as part of the DC boot and health check.
Now most admin tools can connect to remote servers for remote administration. And many default to using DNS to find DCs. Which means you probably have a DNS problem, not a group policy problem.