@wrx7m said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD: @black3dynamite said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD: @wrx7m said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD: @dafyre said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD: @dafyre said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD: @pmoncho said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD: @wrx7m Just curious, when you chose UPD, did you choose to store all settings or just certain folders? Some applications don't play nicely with roaming profiles. UPDs mount at the usual C:\Users\user.name and the applications can't tell a difference. Right. But, only when the user is logged in. After they logout, that path doesn't exist. I am trying to figure out how to work around that for adding the custom (for each user) erp shortcut on their desktop in their session. Add the shortcut to C:\Users\Public\Desktop. That way it will always show up on each user Desktop. This would be nice and easy, but each user has a custom shortcut- It has a workstation ID in the target path. https://www.pdq.com/blog/pdq-deploy-and-powershell/ Create a script that creates the shortcut each user Desktop and append the workstation id in the target path.

@pmoncho said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?: @Dashrender said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?: Cool, then you should have it easy. FYI - Published apps still create a full profile on the RDS box, Just the desktop isn't presented to the user. If the application allows them to browse around, they could typically see the drive letters, the mapped printers, etc... that's why you still need to lock all that stuff down. Thanks for the info. I will keep that in mind. I was debating about using UPD's like @wrx7m and that was my interest in this post. Also, still planning out where to put Connection Broker, WebAccess and Licensing but that is another post. For local profile management, UPDs are a lot cleaner. If we are not putting them on a file server across the network then a second partition/VHDX is set up for that task to keep them separate. With the inclusion of FSLogix with RDS CALs/SALs now it's a no-brainer, IMNSHO, to set the project up on the FSLogix version. Storage management is another reason why UPDs on a network or separate partition make sense. Keeping a local profile on the C:\ of the session host is messy and can cause issues down the road with users coming and going. As far as the Broker/Gateway/Web put those roles on one VM but separate from the Session Host.

@NashBrydges said in Trying my luck in Toronto, Ontario: @manxam said in Trying my luck in Toronto, Ontario: @JaredBusch : Waterloo is over an hour away from Toronto, so quite the difference. Considerably different "way of life" as well. Similar to saying you live in Buffalo when, in fact, you live in Rochester... Agree. I live in the Waterloo area and it is NOTHING like Toronto. Not to anyone from outside the immediate area. Let alone another country halfway around the world.