Two MSTSCs and one WKSPRT, oh de doo dah day!


hi,

i implementing enterprise sso kiosk solution need track launch , termination of rdp session if session times out workstation locks. sounds simple? not anymore.

we're using rds 2012 r2 , current remote desktop win7 (8.0), , bizarre process chaining point just, well, unpredictable.

using procmon can see consistently workflow when launching rdp file connect rds broker follows:

  1. mstsc.exe launches
  2. wksprt.exe (remoteapp , desktop connection runtime) starts
  3. a new mstsc.exe process starts up.
  4. the original mstsc.exe exits (sometimes!)
  5. wksprt.exe continues running.
  6. user disconnects or rds session times out
  7. wksprt.exe terminates mstsc.exe process started or
  8. the original 1 terminates
  9. about 7 seconds later, if either mstsc.exe session still running, terminates

the problem makes nigh on impossible monitor user logon/logout workflow in consistent way! don't know 1 iteration next, it's going do.

if track first mstsc process only, correctly detect user logon , session disconnect client side, if first instance 1 presents connection dialog. every , again second mstsc process 1 presents ui, not first one, step 4 leads think user's rdp session has terminated when it's starting up.

and particular favourite... every , then, 1 mstsc.exe instance dies when user disconnects other 1 sticks around 7-8 seconds if place dependency on "logout detection" on both instances disappearing there's 8 second window pc sat unlocked , can break thin client desktop.

and of course, wksprt.exe doesn't die unless kill manually.

window focus tracking works partially, don't want end having weird stuff mitigating user pressing ctrl-alt-del , breaking out local desktop booting them out of rds session.

does have ideas on how best tackle this?


tim staddon

hi,

 

thank question.

 

i trying involve familiar topic further @ issue. there might time delay. appreciate patience.

 

thank understanding , support.


jeremy wu

technet community support



Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Popular posts from this blog

Group Policy Event ID 1058 Error Code 1326 (The user name or password is incorrect)

Suspicious event log Event ID: 4905

DCOM received error "2147746132" from...