Windows Key with Virtual Desktop

[BrianTofft]

Hi all,

MIght be a noob question, but trying anyway.

I have thin clients booting Win XPe and logging into virtual desktops imidiately - all works fine.

Until someone pressed the "windows key" working inside the virtual desktop. The windows key reveals the startmenu of the thin client OS and thereby confusing and messing up the users work????

Any sugestions on how to remap/disable/redirect the "windows key" to the virtual desktop instead of the local device?

/Brian

[admin]

What you could do is starting the View client (wswc.exe) as the Windows shell. Just set that in the registry and the View client will immediately start when you turn on the client. On a locked down device the user can't start a task manager and so he shouldn't get managed to start the explorer as shell. The administrator can ...

[BrianTofft]

Hi Christoph,

Thx for answering.

Could you be a little more specific on how to change this?? E.g. which reg. setting (Path) etc.

/Brian

[admin]

Hi there,

Sorry I didn't sent a link directly: http://msdn.microsoft.com/en-us/library/ms838576(WinEmbedded.5).aspx

I've also added it to my FAQ: http://www.thatsmyview.net/faq/client-related/changing-the-windows-xpe-shell/

Thanks,

Christoph

[grossag]

This can be controlled by setting the KeyboardHookMode value in the registry ( http://msdn.microsoft.com/en-us/library/aa381299(VS.85).aspx ). You set it in the registry key HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware VDM\Client by creating a string KeyboardHookMode to whichever value listed in the registry. Unfortunately a value of "2" currently acts the same as the value of "0" but the default value is "1" which is what you see. The only other thing you can try is "0", which is to send the Windows key to the local machine whether you're in Windowed or Fullscreen mode. But we are working on supporting a value of "2" in future releases. Hope this helps.

[acabs]

did you get a proper resolution on this?we got the same issue here and users are making some stuff outside the vmware session.is there a way to disable those vmware stroke?