Best way to migrate profiles from Windows Server 2008 to Windows Server 2012 (both Remote Desktop Servers)?

Currently I have a Windows Server 2008R2 (Standard) Remote Desktop Server with about 50 users. I've just finished setting up a Windows Server 2012R2 (Standard) Remote Desktop Server and I'm trying to figure out the best way to copy all the user profiles across (i.e. C:\Users)?

Or is it better to login to as each user to create new profiles & then robocopy their desktop, document, etc. folders??

I assume simply copying the entire C:\Users directory is a bad idea as it's connected with the Windows Registry and the machines are running.

They are both on the same domain & subnet, and I have domain & local administrator access. They are also both on the same 2012R2 Hyper V server so copying files between them should be quick.
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.

If just interested in just the files (and not email settings etc)  then I would redirect their desktop, documents, pictures, favorites, music, etc to a network location. You can do this by way of GPO also. Then the files would be accessible from any machine on the domain.
alex_smithAuthor Commented:
Thanks for the suggestion but I also need the settings (& many of the users are using thinclients so wouldn't benefit).
If you need the settings then it's probably best to use roaming profiles. That would ensure the registry settings follow the user. If it's an active directory domain, then it's fairly easy to convert the profiles to roaming.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

alex_smithAuthor Commented:
Thanks for the suggestion but as they only need to access the profiles/files when they are logged onto the Remote Desktop Server via a RDP client, it's not worth making them into roaming profiles.
If that's the case, then might I suggest this:

Look at their free products. I've used them for years with amazing results. It should do what you need.

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
alex_smithAuthor Commented:
Thanks, I'll check it out!
alex_smithAuthor Commented:
Do you think Windows Server Migration Tools ( would be better?
Are we talking about a lot of profiles?
alex_smithAuthor Commented:
About 50-70...
Not sure how you're going to use that tool to migrate locally stored profile content into a terminal server.

I'd probably approach it this way:

1. Ensure all user data is stored on the network. You can do this by way of folder redirection or by having your users move important data to mapped drives on the network.

2.  Standardize the applications being used. If you migrate a users profile from their existing machine to the terminal server and there are differing software packages (such as different versions of ms office for example) you may end up with shortcuts to things that are broken.

3.  Through AD, you can select multiple accounts and change their profile paths to be a network location. The next time the user logs into their station and then logs off, it should trigger a copy operation of their profile onto the profile path. If you use the %username% variable in the profile path, you should end up with unique network locations for each of these accounts. Hopefully you follow what I mean here.

4.  When they login to the terminal servers, it should load their profile off the network share previously designated in step 3. If access to their many files already Point to mapped drives as outlined in step 1, then this should be a fairly quick and painless step.

This is probably one of the quickest way that I can think of resulting in very little cleanup after migration.
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.