@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.