DI
asked on
SBS 2011 Migration: Cannot demote old SBS 2008 server
Experts,
I am on the process of migrationg from SBS 2008 to SBS 2011. I've been following Microsoft's instructions in the document "Migrate to Windows SBS 2011 Standard from Windows SBS 2008" and I've reached the point where I am to demote the old SBS 2008 server.
I run DCPROMO, making sure NOT to check the boxes "Delete the domain because this server is the last domain controller in the domain" and "Delete the DNS delegations pointing to this server".
When the wizard is to perform the demotion, it stops with the error
The operation failed because:
Active Directory Domain Services could not transfer the remaining data in directory partition DC=ForestDnsZones,DC=MyDom ain,DC=loc al to
Active Directory Domain Controller \\NewSBSServer.MyDomain.lo cal.
"The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers."
I've read articles referring to the NTDSUTIL command and using that to transfer the FSMO roles manually, but I am a bit worried about doing this on a Small Business Server.
Any advice? Should I run dcpromo /forceremoval?
Thanks!
I am on the process of migrationg from SBS 2008 to SBS 2011. I've been following Microsoft's instructions in the document "Migrate to Windows SBS 2011 Standard from Windows SBS 2008" and I've reached the point where I am to demote the old SBS 2008 server.
I run DCPROMO, making sure NOT to check the boxes "Delete the domain because this server is the last domain controller in the domain" and "Delete the DNS delegations pointing to this server".
When the wizard is to perform the demotion, it stops with the error
The operation failed because:
Active Directory Domain Services could not transfer the remaining data in directory partition DC=ForestDnsZones,DC=MyDom
Active Directory Domain Controller \\NewSBSServer.MyDomain.lo
"The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers."
I've read articles referring to the NTDSUTIL command and using that to transfer the FSMO roles manually, but I am a bit worried about doing this on a Small Business Server.
Any advice? Should I run dcpromo /forceremoval?
Thanks!
I had this problem when migrating our SBS 2003 to SBS v7 bits though no specifics were found as to why. I had to force remove the SBS 03 box.
It happened again when migrating from v7 to SBS RTM.
Look in the logs. You may find the reference to an old server that once held a FSMO role. If you do, use ADSIEdit to clean up the bad entry on the SBS 11 box.
If you need more info I can get it when back in the shop on Monday.
Philip
It happened again when migrating from v7 to SBS RTM.
Look in the logs. You may find the reference to an old server that once held a FSMO role. If you do, use ADSIEdit to clean up the bad entry on the SBS 11 box.
If you need more info I can get it when back in the shop on Monday.
Philip
ASKER
I checked DNS, and I saw that the old server was listed with a Name Server record (NS), along with the new server. I removed the incorrect NS record, and ran DCPROMO, and then it completed successfully.
Could this have been the actual reason, or was I just lucky?
Another thing: Looking in AD Users & Computers, I noticed that the OU <domain>\MyBusiness\Comput ers\SBSSer vers was empty. Instead, I found my new server in the <domain>\Domain Controllers OU. Is this correct?
Could this have been the actual reason, or was I just lucky?
Another thing: Looking in AD Users & Computers, I noticed that the OU <domain>\MyBusiness\Comput
ASKER
Oh, and before I ran DCPROMO, I checked all the FSMO roles, and they were already pointing to the new server.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
The problem we were experiencing was that the FSMO Role owners were correct in the MMCs.
It was a deep seated setting accessible via ADSIEdit that had the reference to a DC from way back.
Glad things worked out for you.
Philip
It was a deep seated setting accessible via ADSIEdit that had the reference to a DC from way back.
Glad things worked out for you.
Philip
ASKER
Thanks a lot! The server appears to run fine now. A few warnings in the Event logs, but nothing critical, and I am sure that I should be able to get rid of those as well.
Thank you all, had the same problem, and the fix was DNS!!!!
-Cliff