Hi All,

Maybe this is not the right forum but i have the following problem.
On a thin client that is member of a domain, i use KIX to determine if a user is member of an AD group, if it is then it's starts an RDP session, if not it starts a local IE.
If the RDP session is activated kix also watch if the process mstsc.exe is running, if not (user is clicking on logoff) the Thin Client is also logging of.
So far so good.

Now the challenge ;\)
If a user is locking the RDP session, the Thin Client isn't locked. But we have a connection bar at the top so a user can switch to the Thin Client environment for using MS Lync 2010 with Webcam and Sound. If an other user is clicking on the connection bar he can click again on the icon on the desktop to start the RDP session and he's logging in. That's because the Thin Client is a member of the domain and single sign on is on.

There are many options to solve this, but is there an option if the RDP session locks kix can determine this and lock the thin client ?
Other solutions i thought are:
- remove the connection bar at the top, but then MS Lync can not be used
- the quick key's like winkey+l, alt+tab are working in the RDP session, remove that and bring it back to the thin client is a solution, but user still needs to press winkey+l
- removing the icon from the desktop, kix looks now to that shortcut to start the RDP session, but user can also access Z-drive (RAM drive) where also this is used
- remove single sign on, but that was the main reason to put the thin clients in the domain
- waiting to MS lync 2013 where it is possible to have video in a RDP session is also not an option.

Hopefully you have some good idea's and solutions for my problem.

Kind regards,

Jappie J