Replacing crashed domain controller with new server

I recently had a Windows Server 2003 crash and burn that was the domain controller of the client network. There also is a Windows 2011 Essentials server running as the GC on the network.

I'm installing server 2008 standard R2 on the new server and have it as the DC again. I was thinking that I could give it the same name and install it back on the network to replicate AD from the 2011 server. Am I wrong in my thinking?

Normally in this situation I would just make the 2011 server the DC, but it was not installed for the purpose of running AD. It is primarily used to run medical applications and the client would like that role only to be used as a backup on this server.

These are the only two servers on the network.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

I have not encountered windows server essentials, but this is how I would do it:

If the old dc held all of the FSMO roles, then I would start by seizing these onto the windows server essentials box

Then once this is complete, vefify, then join the new "DC" to the domain.

Make the new "DC" a domain controller, and GC

Transfer the FSMO roles back to the new DC
Also don't make it the same name, if any old AD records are out there with the old server name it could cause problems or confusion with AD.
ict4usaAuthor Commented:
The 2011 is the new version of small business server.

I kind of figured I shouldn't give the server the same name, but what about in regards to the domain name. Could I go back with the same domain name?
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

if you move the fsmo roles to the 2011 server which would make this the new master, you can join the domain again.
ict4usaAuthor Commented:
That's the problem. I can't get the fsmo roles because the 2003 server is dead with no good backup.
look at seize fsmo roles part, you can't transfer i know.
Log onto the 2011 server, go to command prompt and use ntdsutil to seize the roles in the link about.  This should work for you, i had to do the same thing last year when one of my dc's died that had the roles.
Once the roles are seized you should be able to transfer the role to the sbs2011 server using ntdsutil
here are better steps for you

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
Microsoft Server OS

From novice to tech pro — start learning today.