Server 2003 to Server 2012 - Your thoughts

Real simple network.

One server, 2003 Standard, 7 PCs a mix of XP and 7.  Server is handling DNS and DHCP.
Barely even any file sharing going on.

They want to move to Server 2012.

I can go through the whole process of adding the Server 2012 to the domain, migrating FSMO roles, etc etc.

I am debating just copying files over, shutting off the 2003 server, bring up the 2012 box with the same name and IP as the old one.  I just wonder when someone logs in from their PC, will they get a whole diff desktop and email (IMAP) settings because the SIDs may be different?

How would you handle this?  And if I do add the 2012 to the domain, go through the routine, demote the 2003..etc etc... how much work is that?
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.

I think adding to the domain and seizing roles is an option. You then demote the 2003 server.

Alternative is to create an entire clean domain and rejoin the computers to the new domain. It's only 7 computers so not a huge amount of work. Make sure you have the local admin password on the client computers. Move Desktop/Docs/faves/etc/ Move archives if any.

Good opportunity to ensure roaming profiles are sorted. Little chance of inheriting any of the legacy issues (if any).

Good Luck.

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
Seth SimmonsSr. Systems AdministratorCommented:
users will not have any issues logging in since the domain is the same and nothing will be changing as far as user or computer accounts; AD information (account sid, etc.) will replicate from the 2003 server.

once your services, fmso roles are moved over, i would turn off the 2003 server (or just disconnect from the network) for a few days and see how things work with just the 2012 server.  if things look ok then connect the 2003 server back and demote.  no reason to change the 2012 server and address to match the 2003 server.

your environment seems pretty straightforward and shouldn't be too difficult to migrate
dougp23Author Commented:
Does MS have a document for doing this?
I did this once with 2003 to 2008, I think I had to run ADPREP to get the 2003 and 2008 to have the same schema, and from there, it was quite  a  lot of things to do!
Seth SimmonsSr. Systems AdministratorCommented:
the process is similar though it can now be done on the 2012 server directly; no need to run adprep from the legacy server
Seth SimmonsSr. Systems AdministratorCommented:
scroll about half way down to the ntdsutil section; easier to transfer fsmo roles from the command line then having to register dll's and manually add mmc snap-ins to use gui tools
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.