Local profiles to roaming profiles remote desktop server

Question

I have a 2016 Remote Desktop Server with several local user profiles. I plan to replace the server with 2 2019 load balanced RDP servers. I am looking for a reliable process to convert all the local profiles to roaming profiles so their data and configurations will be available on the new servers.
As a test, I setup 2 RDP servers and logged into one server to create the local profile. I changed some configurations and files to create the unique profile. I then applied the GPO to the server OU and my local profile was converted to a roaming profile. I have no problem logging onto the first server and obtaining my roaming profile.
When I log onto the 2nd server, having never logged in with the user account associated with the roaming profile I created, the server states "We can't sign you in to your account" and the server shows the profile as Roaming and the status of temporary.
Obviously it does not have the files and configurations.
I am looking for a reliable way to migrate the profiles to the new servers.
Any advice will be greatly appreciated.

Answer 1

Hello there,

There are several methods you can use to migrate local profiles to roaming profiles on a Remote Desktop Server. Here are some options you can consider:

1. Use the Microsoft User State Migration Tool (USMT) to migrate the local profiles to the new servers. USMT is a command-line utility that allows you to migrate user data and settings from one computer to another. You can use USMT to migrate the local profiles to the new servers, and then configure the servers to use roaming profiles.
2. Use a third-party migration tool. There are several tools available that can help you migrate local profiles to roaming profiles on a Remote Desktop Server. Some examples include PCmover, Laplink, and Zinstall. These tools typically have a graphical user interface and provide a more automated process for migrating local profiles.
3. Manually copy the local profiles to the new servers. You can manually copy the local profiles from the old server to the new servers, and then configure the servers to use roaming profiles. This method requires more manual effort, but it can be a good option if you don't want to use a third-party tool or if you prefer a more hands-on approach.

Whichever method you choose, be sure to test the migration process thoroughly before you decommission the old server. This will help ensure that the migration is successful and that your users can access their data and settings on the new servers.

--If the reply is helpful, please Upvote and Accept it as an answer–