> Force Users To Log Off
> Out of habit, it's not uncommon for an end user to:

> • | Lock shared Windows desktops

> • | Disconnect from shared Windows desktops

> • | Press the Pano button before stepping away from a shared Windows desktop

> For all collections, these actions represent disconnects and don't terminate the user's session. Only after the session terminates can other users use the DVM.
> In a Pooled Desktops collection type, for example, users must log off in order for the DVM to return to the pool. If, instead, the user presses the Pano Button, for example, when the next user tries to use the DVM, the user cannot log on to that DVM because it has not been returned to the pool, and that’s not good for workplace productivity. Pano Logic has a solution for you, and this solution can apply to any collection.
> To force users to log off:
> This procedure does exactly what’s outlined in Control Session Timeouts, except that you don’t need to edit the registry manually. The executable outlined in this procedure does it all for you.
> Perform the following steps on each DVM, or just one DVM if you are using that DVM as your template.

> 1. | From a Windows prompt, go to the BIN directory:

> > cd C:\Program Files\Pano Logic\Pano Desktop Additions\BIN\

> 2. | Run the panodascfg.exe file with the DisconnectedTimeout option set to 2.

> > panodascfg.exe –DisconnectedTimeout 2

> 3. | Reboot the Windows virtual machine.

> When the user disconnects, 2 seconds later this script logs off the user and makes the Pano device available for the next user automatically.

Did you find what you're looking for?
v2.5.1