Skip to main content

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key.
image
Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General.
Change the Keyboard and mouse priority to Host side user and click Apply at the bottom.
On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works.
Uncheck Turn on Sticky Keys.
image
Click Set up Sticky Keys.
Uncheck Turn on Sticky Keys when SHIFT is pressed five times.
image
Click OK twice.

If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem.

Updated Information: March 20, 2013

If you continue to have problems, Uncheck Turn on Filter Keys.


Comments

mantis2k said…
I have reproduced the same issue...hoping there will be a fix soon from logmein.
Anonymous said…
thank you, this was driving me mad setting up a Hyper_V host and guests over LogMeIn tonight (of course all my passwords also have lots of shifted characters...)
Ronnie,

I added one more step to the end of the post that may help.

Jason
Anonymous said…
I have just resorted to using the on screen keyboard for when I need to press shift more than once. Once the next OS based on Windows 8 that everyone loves they will fix it. :rolleyes:
Anonymous said…
Thank you very much. This was driving me crazy. To the other comments, make sure you do this on the host machine and all VM's.
Unknown said…
I have a Hyper-V host with 2 2012 Server VM's running on it. On all 3 the Host setting for Logmein is checked and on all three Sticky Keys are turned off and Turn on Filter Keys is unchecked, and yet it still keeps asking to turn on sticky keys after every keystroke that has a Shift in it for a capital letter.

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the ma...