We are currently setting up a new Server 2012 Remote Desktop environment. We want to use "User Profile Disks" for users' roaming profiles and this, in it's simplest form, is ticking a box and specifying the server share to store the .vhdx files. This is all working fine and the .vhdx file gets created etc. The problem that we are getting is that the user profile path that is specified against the user object in AD (for logging on to our regular desktop computers) is also being applied.
Traditionally, terminal services and remote desktop profile paths could be specified in AD or via Group Policy and would override the user profile path, specified against the AD user object, when connecting to a remote session host. Now though, because the path for the "User Profile Disks" is a setting on the remote desktop server there is nothing to set in group policy or AD to override the roaming profile path on the AD user object. If I remove the user profile path from AD then it all works as it should.
I hope this makes sense O_o
Anybody have any ideas how to NOT apply the user profile path from AD when using RD User Profile Disks?
Here's a list of a lot of problems users are experiencing with User Profile Disks, (UPD's) I love the idea, but it's just not ready for prime time.
There are currently 1 users browsing this thread. (0 members and 1 guests)