Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a RemoteApp deployment (Web, Gateway, High Available Connection Brokers, ...). We use profile disks stored on a file share. We publish most of our applications, but from time to time, a user needs a full fletched desktop.

That's why we also published mstsc with the path to the original .rdp-file from when there were no applications published.

This all works fine, unless a user has an application open when they open the desktop. The server fails to mount their profile disk (because it's already mounted by the session providing the application and thus locked).

This causes the session host to load a temporary profile.

Is there any way around this, while still using User Profile Disks?
Is it possible to get the session that is providing the apps when opening the desktop somehow?

share|improve this question

This question has come up previously (Windows 2012 RDS Temporary profile for Administrator) with no workaround. UPD was only designed to support a single session per user.

Even if you could get the RemoteApp session, which I don't believe you can, the screen resolution would end up being very screwy, since it's based on the size of the single application window.

Your best bet is simple user education, or write some kind of script that's launched when they try to enter a full-desktop session to kick any other sessions off first.

share|improve this answer

To expand on @tfrederick74656,

UPD was only designed to support a single session per user, per session collection

Best I've come up with is to provide users two session collections, both with their own UPD's. Use identical syspreps of Session Hosts across farm so the user experience is the same:

  • Collection 1: RemoteApp's, published to RDWeb
  • Collection 2: "Full Desktop", published to RDWeb

The full desktop can only be published if you don't create any Published Applications in the collection. It's an either-or scenario.

Only down side is twice as many UPD's and Session Hosts.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.