Migrating user profiles from one RDS 2016 to another RDS 2016
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.
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
Alexandre
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
- What would be the recommended way to build the 2nd server to minimise work of transferring profiles (Roaming profile, scripting, RDS farms,...?)
- Is there an Expert interested in assisting me with this
Alexandre
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Yes. With a full backup so permissions are retained and as long as the environment is domain joined (which most RDS environments are.)
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.
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.
ASKER
Thanks for your help
ASKER
@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
Alexandre
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.
And yes, another Session Host should be able to be brought in to an existing setup/collection.
ASKER
So building a new RDS and just overwriting the C:\Users folder would work???
Alexandre