This issue occurs because Windows Server 2012 and Windows Server 2012 R2 use the Remote Desktop Keyboard Device to handle the keyboard inputs in remote desktop sessions. In a remote desktop session to a Windows Server 2008 R2-based computer, if we do the same steps, the Caps Lock key on the client's physical keyboard also turns to off status, which is synced with the remote desktop session. The Word feature that triggers this issue is named correct accidental usage of cAPs LOCK keyin AutoCorrect options. It is not synced with the remote desktop session Caps Lock key status. However, on the client's physical keyboard, the Caps Lock light is still on, and it is still in Caps Lock On status. In this situation, the hELLO in Word will be corrected to Hello automatically, and Caps Lock is turned off in the remote desktop session. If an application, such as winword.exe or osk.exe, changes the Caps Lock key status, this change will not be synchronized back to the client computer.įor example, in a remote desktop session, when you open Microsoft Word, type h, turn on Caps Lock by pressing the keyboard, and then type ELLO, the word is hELLO. This article provides a solution to an issue where the Caps Lock key status change triggered by an application in a remote computer isn't synchronized back to the client computer.Īpplies to: Windows Server 2012 R2 Original KB number: 3120433 SymptomsĪssume that you connect to a remote computer in a remote desktop session.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |