New custimer here and just trying to get the KeyboardHookMode bit to work...
Please correct me if I'm wrong but should this being set to a value of 1, pass the CRTL-ALT-DEL keyboard action through to a terminal server, andshouldn't have an effect on the local PC/thin client? We're using Windows 2003 R2 TS
I'm finding it still brings up the local CTRL-ATL-DEL screen on the local PCs, which are Windows 7 Pro x86
Are you connecting full screen? Have you tried 2 as the value? I have seen behavior before and i believe it was a local policy on a client device. However I never found out what the policy was, as the client was rebuilt which resulted in it starting to work.
You are correct in what you say, setting the KeyboardHookMode value to 1 does direct the key combinations to the remote VDI or TS session. This works for combinations such as ALT & Tab but not CTRL-ALT-DEL. The CTRL-ALT-DEL key combination is always intercepted by the client computer, when in a remote session using CTRL-ALT-END will provide the same functionality
KeyboardHookMode aside, on the (Windows) client if you set HKLM\Software\MS\Windows NT\CurrentVersion\WinLogon\AutoAdminLogon from the default value of 0 to 2 it will disable the local and will then be directed to the remote session.
DELL-Paul Fi
101 Posts
318
0
Posted October 6th, 2010 12:00
Hi Caleb,
1 = Always send to server
2 = In full screen only.
Are you connecting full screen? Have you tried 2 as the value? I have seen behavior before and i believe it was a local policy on a client device. However I never found out what the policy was, as the client was rebuilt which resulted in it starting to work.