Solved

SBS 2011 Server was not promoted during migration from SBS 2008

Posted on 2013-10-27
3
577 Views
Last Modified: 2013-11-01
Good morning everyone!

I've been trying to do an SBS migration from 2008 to 2011 but I keep getting the dreaded 'Server was not promoted to Domain Controller' error.

In the log, it lists error 54 - ExitPromoDemotFailed
followed by error 26 - ExitUnableReadDomainList

The source server is completely up to date with Exchange SP3, and all Windows updates. I ran the Migration Prep Tool, found no problems and made my answer file.

Here are some of the things I tried:

Made the administrator password extra complex (it now has a capital letter, lowercase letters, numbers and a special character.)  I rebooted after changing the password

Made sure the date, time and time zone are the same on both servers

Turned off IPv6 on the 2011 server

Made sure all unused NICS are disabled on both servers

Made sure there only DNS entry in the network config of the 2008 server is its own address (the ISP's DNS was also in there and I deleted it, then cleared the cache and restarted DNS)

Seized back the schema master, infrastructure master, domain naming master, pdc master roles to the 2008 box before trying SBSSetup again.  On my first attempt, they transferred to the 2011 box, but the roles stayed on the 2008 box after I seized them back even after trying the installation several more times)

Tried making the answer file with the DHCP box both checked and unchecked (it is running on the 2008 server)

I am able to ping the 2008 server from the 2011 server using the name.

Please help!
0
Comment
Question by:mikem2k
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 18

Expert Comment

by:Netflo
ID: 39603901
0
 

Accepted Solution

by:
mikem2k earned 0 total points
ID: 39604378
I only disabled IPv6 for one attempt and then promptly re-enabled it, and did everything else in the Microsoft guide.

Came across this article

 http://www.petri.co.il/delete_failed_dcs_from_ad.htm

It turned out that the 2011 server was showing up in the metadata list of the 2008 server.  I ran the cleanup as it indicated and all is good.

Thanks so much for the quick response though.
0
 

Author Closing Comment

by:mikem2k
ID: 39616211
The exact steps outlined in the Petri article fixed the problem.
0

Featured Post

Enroll in July's Course of the Month

July's Course of the Month is now available! Enroll to learn HTML5 and prepare for certification. It's free for Premium Members, Team Accounts, and Qualified Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
A hard and fast method for reducing Active Directory Administrators members.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question