johnny181
asked on
Cannot demote server because of error with fSMORoleOwner
We recently migrated from Windows 2008 SBS over to Windows 2012. We had issues demoting the SBS server so in the interests in saving time, we carried on. We used an intermediate server (Windows 2008 R2 Server) to hold the AD information until we brought up our 2012 domain server. Now, I am trying to demote our temp 2008 server and I am getting an error when I try to demote it "The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles"
In doing some research it shows to load up ADSI Edit and look for the ‘fSMORoleOwner’ under CN-Infrastructure I see that the old SBS server is listed there and so when I try to change that line, I get an error Operation failed. Error code: 0x20ae The role owner attribute could not be read.
I started up ntdsutil and transferred all 5 roles successfully to the 2012 domain server, started up ADSI Edit and tried to edit the ‘fSMORoleOwner’ and still could not change it. It looked as if it had a bunch of garbage characters in it. I was able to change it and changed it to the format as it is on one of my other client domain servers.
That still didn't fix the issue though
I checked the eventlog and it looks like the AD information is replicating properly. I was going to force the dcpromo but then thought that we may have the same problem if we migrate to another server years down the road. I figured it might be better to resolve this problem now instead of later.
Any ideas on what to do next to fix this issue?
In doing some research it shows to load up ADSI Edit and look for the ‘fSMORoleOwner’ under CN-Infrastructure I see that the old SBS server is listed there and so when I try to change that line, I get an error Operation failed. Error code: 0x20ae The role owner attribute could not be read.
I started up ntdsutil and transferred all 5 roles successfully to the 2012 domain server, started up ADSI Edit and tried to edit the ‘fSMORoleOwner’ and still could not change it. It looked as if it had a bunch of garbage characters in it. I was able to change it and changed it to the format as it is on one of my other client domain servers.
That still didn't fix the issue though
I checked the eventlog and it looks like the AD information is replicating properly. I was going to force the dcpromo but then thought that we may have the same problem if we migrate to another server years down the road. I figured it might be better to resolve this problem now instead of later.
Any ideas on what to do next to fix this issue?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
CN=NTDS Settings,CN=hostname>,CN=S