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

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...