WTware RDP client

win_l = remote

In 6.2.46 new option added to bypass win-l to server:
[code]win_l = remote[/code]

1. New "lock"-feature was done because locking in RDP session can be
unlocked by disconnecting network cable. It is windows bug and
Microsoft won't fix it because regular windows machines get locked by Win-L
locally, not in RDP session, so unaffected by this bug. Now wtware locks
locally like windows machine. Here are more details:
https://forum.wtware.com/viewtopic.php?t=57594

2. "sleep=20" in wtware config only turn monitor off. It has no relation
to login to RDP session. Windows has policy that disconnects RDP session
after period inactivity. This policy disconnects RDP session so user
should log in into RDP session.


I have another idea. WTware only locks if there is active RDP session
on screen. What if I instruct wtware to unlock if server disconnects RDP
session?

So there will be only one login to user. If wtware is locked by Win-L
and RDP session is still active, user will enter password for wtware. If
RDP session disconnects, wtware unlocks and user will enter password to
RDP session. Will it work?

Please try wtware 6.2.38 version. Show me the log if something goes wrong: http://wtware.com/logs.html

Hi!

Since version 6.2.32 there's the new "lock"-feature. Is it possible to disable this in the config?

Problem: all clients have

sleep = 20

in their config. When the user comes back to his client he has to login twice: once in the WTWare screen and another time in his RDP session.