Migrating user profiles from one RDS 2016 to another RDS 2016

Alexandre Michel
Alexandre Michel used Ask the Experts™
on
Hi Experts

This is a follow up on a question asked previously on this forum (https://www.experts-exchange.com/questions/29073016/A-number-of-Services-stop-on-a-RDS-Server-2016.html)

We have a sick RDS 2016.
  • It has ~ 15 users. It is VM on a HyperV 2016.
  • It is a member of an AD.
  • The other VM server is the DC + File & Print
  • Users are using Office 365
  • Each user's Outlook can have between 1 and 5 mailboxes

I have spent several days (probably 40h+) trying to fix it to no avail.

I am considering building a new RDS and migrate all the profiles if I cannot otherwise fix the issues on the RDS.

Questions
  1. What would be the recommended way to build the 2nd server to minimise work of transferring profiles (Roaming profile, scripting, RDS farms,...?)
  2. Is there an Expert interested in assisting me with this


Alexandre
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2018
Commented:
Backing up and restoring the profile folder would be fast and should be transparent if the environment is healthy. Moving forward though I always recommend user profile disks for RDS ND this is one reason why.
Alexandre MichelManager; IT Consultant

Author

Commented:
Hi Cliff,

So building a new RDS and just overwriting the C:\Users folder would work???

Alexandre
Distinguished Expert 2018

Commented:
Yes. With a full backup so permissions are retained and as long as the environment is domain joined (which most RDS environments are.)
Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
I suggest the use of User Profile Disks (UPDs) hosted on a network located folder also mentioned by Cliff.

Also, a better idea is to do the following for a RDS setup:
1: VM hosts Broker, Gateway, and RDWeb
2: VM hosts Session Host (RemoteApps and Desktops) Member of Collection on Broker

Then, if something blows up the "fix" is actually quite simple:

Set up new VM and install Session Host Role via Broker. Set up apps and log users in. They get their profile via UPD thus no tweaking required.

Cliff's backup and restore process is probably your best bet.
Alexandre MichelManager; IT Consultant

Author

Commented:
Thanks for your help
Alexandre MichelManager; IT Consultant

Author

Commented:
@Phliip: While we have decided NOT to rebuild this RDS, I am intrigued with suggestion nevertheless. Does this work when there is only one RDS or do we need a farm?

Alexandre
Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
In a single server configuration one need only add another RDS Session Host via the Broker. By default we now set up an individual VM with Broker/Gateway/RDWeb roles installed and configured and set up a dedicated Session Host VM for the users. This gives us a lot more flexibility.

And yes, another Session Host should be able to be brought in to an existing setup/collection.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial