So stumbled upon a interesting case the other day where I had a setup using RemoteApps and User Profile disks, sounds simple enough right?
Now we had a web portal where the users accessed their applications and they also wanted access to a full desktop as well (Which is a known change in 2012 RDS that you can either have RemoteApps or full desktops)
There is of course an registry fix to change this to show a full desktop conncetion in the web portal (Which needs to be changed on the connection broker)
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms\<collection>\RemoteDesktops\<collection>
ShowInPortal REG_DWORD 0×00000001 (1 means SHOW the desktop connection icon, 0 will hide it)
After enabling this we have a application in the web portal which allows us to access a full desktop to the session collection.
Now the problem is when a user connects to a remoteapp in a collection. When the user logs in the connection will map the login with the user profile disk which is attached to that user.
If the user (Which already has an connection) start a new connection with the full desktop app in the portal, this is where the problem happens.
Since the user profile disk is locked to the first session, the user will get a temporary profile generated and a blank screen in the GUI since it is unable to load the profile.
Now there is no fixes for this, just to make people clear of this issue. A user cannot have a remoteapp and full desktop connection at the same time against a collection which has user profile disks enabled!