Hi there,
I am setting up a Remoteapp/ RDS environment and was hoping someone could advise on the following:
Environment: 2003 AD scheduled to be upgraded to 2012R2. All the servers below are Hyper-V VMs.
1 RD Gateway, 1 RD web, 1 RD Broker (all 2012R2).
2 Session collections, each with 4 RDS servers. Collection 1 is for remote apps and Collection 2 is for Full Desktop.
All session hosts are 2012R2.
The plan is to have roaming profiles and folder redirection along with user home drives. Roaming profiles for desktops will be on Profile01/profile$. Roaming profiles for RDS will be on Profile02/profile$. Home drives will be on FileServer01/Home$.
Additionally, we have a request that some users home folders also be 'work folder' capable.
1) I believe I am correct in that a user's Desktop and RDS profiles have to be in different places. However, what about Profiles for different RDS collections? Do the profiles for a user's RDS collections have to be located in different places (simillar to that of different RDS farms) or can 2 collections (Remoteapp and Full Desktop) share the same Profile?
2) http://blogs.technet.com/b/askds/archive/2008/06/30/automatic-creation-of-user-folders-for-home-roaming-profile-and-redirected-folders.aspx states several permissions for roaming profiles, home drives, and folder redirection. However the link is quite dated. Is there newer guidance or is the info here still valid for 2012R2?
3) Another option may be to use Profile disks for RDS. Is this more advantageous than the traditional way? The file and RDS servers themselves are Hyper-V VMs so would there be any issues mounting VHDX files within a VM? The client uses Shadowprotect to take image backups of all the servers so another concern is that the entire profile VHDX for a user gets locked while it is being backed up.
4) Is it ok for the home drive location to be the same for the user whether they log on from their desktop, collection 1 or collection 2?
Thanks,
HA