Windows Server 2012 Standard. How to best workstations to new Server.

Last time I did this was ALONG time ago on a 2003 Server.  However, the current situation is... the client had an existing Windows Server 2012 Standard, Server.  It's only six months old and it crashed, with no onsite backup.  Here is where I entered the scene.  I ended up having to do a clean install on the same physical Sever with the same Server 2012 standard version software.  So my question is when I return the Server to her office on Monday, how do I join the existing workstations to this newer installed Server?  I can name the domain the same as the old or different.  And, it will have the same ip address.  What is the easiest way to do this?  VERY IMPORTANT THING is that I don't have to redo the user accounts with there local preferences and I don't have to move any data stored locally.  I hope that makes sense.   In other words, I want the users preferences and files to look and be exactly the same as it is now, after I join the domain.  Currently, (since the Server crashed) they are logged onto domainname.local.  I don't think they even knew they weren't actually connected to the Server other than by the fact that they couldn't access a lot of data files.  Everything else looked the same and I need to keep it that way or I'm going to have a very long week.  Hopefully that helped explain a little more.
Thank You.
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.

Lee W, MVPTechnology and Business Process AdvisorCommented:
If this was their ONLY server and you rebuilt it instead of repairing it, then your user accounts are gone.  You have to recreate them.  IT doesn't matter if you name the server and the domain the same - domains have unique IDs - it's the domain equivalent to government ID numbers for people ensuring that John Smith is DIFFERENT from John Smith.  

Now, you CAN try using the User Profile Wizard from Forensit to migrate the workstation profiles to the new accounts.  But otherwise, you'll have a lot of work ahead of you - BILL THE CLIENT - their fault they didn't have a backup.  (Though again, it's rare that you can't recover the AD if you understand how AD works and what tools exist - but at this point, if you reloaded, it's too late).

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
PCGalOfCalAuthor Commented:
Wow, that sucks.  UGH!
One of the biggest pains is going to be recreating all the Outlook accounts.  One user for example has six e-mails with rules for each and everything is in the exact order she likes. I don't like she even knows all of her passwords.  Any suggestions to make the Outlook move easier?
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.