When first asked about this I thought this would be a simple thing but I seem to be finding it incredibly difficult. Basically on the logoff button I want to see an disconnect option, not Lock (if lock remains that's fine but ideally that can go too) but I just can't seem to find any settings for it.This is what I see on an uncontrolled start menu, yes I can remove restart and turn the Shutdown into a Logoff but crucially there is no disconnect which is what I need.
If I RDP onto the same Win 7 VM I get this, which is exactly what I want:
So it seems that it is a PCOIP issue that it is trying to be too clever and removing stuff that I am quite capable of clearing up using Group Policy. Is this a common thing? I can't find any way to control it using the ADM templates supplied in the Horizon 6.2 download package. The above screen shots are me logged on as an admin with no user policies applying.
BTW, I don't want any suggestions about using the Horizon client to disconnect or anything like that, I just want it to work like it does in RDP.
This isn't anything we are explicitly doing. When you use PCoIP to access a desktop VM the "physical" console is remoted, unlike an RDP session. So what you're seeing is the same as if you were sitting in front of the machine directly. I don't believe there's anything you can do to add the option as MS do not expose it for console sessions.
WE use the following
This caught us out years ago because in a non persistant environment if you allow the users to shutdown then the desktop ends up in an "Already used" state.
We solved the issue by using that key.
you should end up with Log off> Lock and switch user (greyed out)
Disconnect is present on RDP because you're effectively running a terminal services session to the desktop - so you get the option to disconnect the RDP session, which in turn drops that from the View client.
With a PCoIP session, you're logging into the actual console (hence you see the usual logoff restart and so on, but don't see disconnect).
As you say, you can use the Group Policy to remove and prevent access to Shutdown, restart, sleep and hibernate (For info - User configuration>Policies>Administrative Templates>Start Menu and Task Bar>Remove and prevent access to the Shutdown, restart etc etc) for a start. This will hide these items and force the user to disconnect from the session from the View client
You could try pinning a shortcut to the Start Menu for C:\Windows\System32\tsdiscon.exe - this is the Terminal Session Disconnect utility - this will trigger a disconnect of the running Windows session, but whether that will end the PCoIP session to the Horizon Client, I don't know. Might be fun to test though.
Although VMware is not at fault here that the start menu does not show the disconnect option, it would still be great if there was a elegant way to disconnect a session from inside the desktop, similar to the way you can disconnect a session from the View web console or pressing X on the client.
This becomes an issue with users that move around between thin clients often and need their session to persist through out the day (In our case, clinical workers). To make matters worse, our thin clients use a Kiosk/Appliance mode that completely hides the client toolbar. In this case, it is impossible to disconnect the session other than Start menu > Log Off.
The disconnect utility found under c:\windows\system32 (called tsdiscon.exe) does indeed work to actually disconnect a running PCoIP session. The trick now will be to find an elegant way to put that shortcut somewhere where the user will see/use it. Whether that's as a pinned icon on the taskbar or somewhere in the start menu is probably up to your environment and users. I imagine if you pinned that on the taskbar, disabled the ability to Lock or Shut Down and made Log Off the default option you'll probably have things covered nicely.