Okay, so what you want is to be able to determine the desktop (and windows station?) associated with a newly created process, make some determination, and either allow or block the creation? Note that a desktop is not a security boundary, so it is unclear what this will achieve.
I have no idea how this might be done, but first forget the concept of current. In KM, all desktops that exist are current in that they exist. Processes may be doing all kinds of things in each regardless of which the user may have on the glass terminal, and with the possibility of multiple RDP sessions and graphics drivers that have 'control panel’ applications there could be lots going on.
Would a better solution be to restrict the number of instances of your application that can run concurrently?
Sent from Surface Pro
From: xxxxx@gmail.com
Sent: Thursday, August 21, 2014 2:48 PM
To: Windows System Software Devs Interest List
Ok,
I have created another desktop using CreateDesktop api and I wanted to run only selected process inside same desktop so I am using driver to track process creation but not able detect desktop of process to restrict it.
I don’t see any other way to restrict process creation inside my desktop.
Thanks
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer