Hey Everyone,
I'm experimenting with 2016 RDS, as I want to upgrade our 2012R2 Session Host servers. I have 2012R2 domain controllers (if that matters).
I am noticing that roaming RDS profiles isn't working at all on my 2016 RDS session host servers. A user logs in and gets a local profile, and when they log out, the profile isn't uploaded at all. It's basically just a regular local profile. I have the field set to \\fileserver\rdsprofiles in AD. This has worked fine in RDS in 2003, 08R2, and 2012R2.
However, if I create a GPO and set the profile location that way (Computer - Policies - Administrative Templates - Windows Components - RDS - Session Host - Profiles - Set path for Remote Desktop Services Roaming User Profile), roaming profiles are created on the share and everything works fine, and I can see a new .v6 profile being created. Logging in and out roams the profile properly.
Any thoughts as to why? Has the AD 'Remote Desktop Services Profile' attribute been depreciated for 2016?
I have tried lots of troubleshooting, deleting profiles, new shares, etc, I can't seem to get it to work with the AD attribute (but works fine when set with GPO).
EDIT: Tried this in a homelab setup as well (all 2016 servers), and same thing - only the GPO setting takes effect.