When a user connects via RDWeb and closes all the applications, the session is disconnected. If that same user, then connects via RDP to the full desktop, a new session is created instead of reconnecting the disconnected session from RDWeb.

Aside from bringing a continuity issue, it also breaks mapped drives.

Any idea what might cause this?

  • 1
    AFAIK, it isn't possible to connect to the same session. The web and desktop sessions are managed by two different hosts (services hosting the sessions).
    – dartonw
    Sep 13, 2014 at 6:33
  • Crap. That's a bad design. On top of that, there seem to be no way to log off of an RDWeb session. Sep 15, 2014 at 16:48
  • Agreed, one would think there are enough similarities that the sessions could use the same interfaces/base classes and allow integrated management by a single process.
    – dartonw
    Sep 15, 2014 at 16:59
  • dartonw: make your first comment an answer and I'll validate it. Sep 16, 2014 at 14:02

1 Answer 1


This is by design, RDWeb and full RDP session are using different services.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .