Trying to promote 2012 Essentials R2 Domain Controller on SBS 2003 network

During the attempt to promote the domain controller, I keep getting this error:  An Active Directory domain controller for the domain "domain" could not be contacted
HaulnSSAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joseph OLoughlinIT Support SpecialistCommented:
First of all there are limits to domain controllers in SBS domains, the SBS domain controller must hold the FSMO roles
http://blogs.technet.com/b/sbs/archive/2007/10/04/debunking-the-myth-about-additional-domain-controllers-replica-dcs-in-an-sbs-domain.aspx
However the same limitation applies to Server 2012 Essentials

Windows Server Essentials Experience in Windows Server 2012 R2 Essentials      
Must be the domain controller at the root of the forest and domain, and must hold all the FSMO roles.
Cannot be installed in an environment with a pre-existing Active Directory domain (however, there is a grace period of 21 days for performing migrations).

This refers to the special migration mode install of 2012 essentials
http://technet.microsoft.com/en-us/library/jj200112.aspx

If this isn't working, another server is needed.  Your domain migration has become much more complex, requiring another windows domain controller onto which you seize the fsmo roles while decommissioning the SBS 2003 controller, followed by another seizure to complete the migration.  Painful.
0
hecgomrecCommented:
This versions are not like regular versions to work with dcpromo.

You must first, make sure you did follow the wizard (2012) by selecting the installation mode: Server migration.

If you did select that option then you must complete all step to make sure your server is in control, like joining the computers to the new server, moving any data, exchange (if any), transfer GPOs, DHCP, DNS, scripts, printer, etc.

Then you can run dcpromo on the 2003 to remove the AD DS role to make it a domain member server, please Do not select "This server is the last domain controller in the domain." from the options. By demoting the 2003 will automatically make your 2012 the main DC.  You may shutdown both servers and restart your 2012 first and your 2003 after just to confirm it is in fact just a member;  Connect some PCs and troubleshoot if required.
0
HaulnSSAuthor Commented:
I moved the FSMO roles back to the 2003 server, removed  the setup from 2012 and rebooted.  Moved the roles back and all was happy.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.