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...)
Unknown said…
This is all done as you describe - I still get the sticky keys on the guest OS' password prompt when logging on.
Unknown said…
This is all done, but I still get sticky keys warning on guest OS' when logging on to them via the Hyper-V manager when connected to the Hyper-V server by either logmein website or ignition.
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

Determine which Domain Controller a client is connected to with PowerShell

When a Windows client comes online, it must find a domain controller to bind to.  Either through a static configuration or DHCP, the client will request a list of all Domain Controllers in the domain from a DNS server.  Once the list is received, the client will randomly go through the list to find a DC that will respond.  Once the client has authenticated itself with the DC, the DC will transmit the site information to the client.  The site information will contain the site name, the subnet(s) associated with that site, and any domain controllers in that site.  The client will then take a look at it’s own IP address to determine which site it is in.  From the list of DCs in the same site, it will attempt to bind to one of those DCs to receive it’s Group Policies.You can use PowerShell and WMI to locate the domain controller that a client is connected to.Get-WMIObject Win32_NTDomainLook for the DomainControllerName property.

Test to see what that data type of a value is in PowerShell

PowerShell has a comparison operator called –is.  The –is operator simply response True or False when you use it to verify the data type of a value.  The valid data types in PowerShell are:
[string]    Fixed-length string of Unicode characters
[char]      A Unicode 16-bit character
[byte]      An 8-bit unsigned character
[int]       32-bit signed integer
[long]      64-bit signed integer
[bool]      Boolean True/False value
[decimal]   A 128-bit decimal value
[single]    Single-precision 32-bit floating point number
[double]    Double-precision 64-bit floating point number
[DateTime]  Date and Time
[xml]       Xml object
[array]     An array of values
[hashtable] Hashtable object

Below is a script that will use –is to test some values.
$String="Hello"$Boolean=$True$Int=15Write-Host"Test for string"$String-is [String] $Boolean-is [String] $Int-is [String] Write-Host" "Write-Host"Test for Boolean"…

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015
When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.  

My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication.
This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell.
The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes.
Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account ManagementDouble click User Account ManagementCheck Configure the f…