We typically recommend clicking the task bar. Were then provided a refund and informed that they would let us know when a fix is in place.Ĭlicking anywhere outside of the RemoteApp applications will correct the inversion. The ticket was escalated, and we were eventually informed that this is a known issue that hasn't been documented. We placed a paid ticket with Microsoft Support where we explained the issue and provided instructions on how to recreate.
This also works in clean installations on both Server 2012r.Ĭurrently none. I have tested this in several applications including: Adobe, WordPad, Word, Excel, PowerPoint. The caps lock/num lock key will now be out of sync.Press the "Caps Lock" or "Num Lock" key before pressing anything else.Publish "Notepad" in your RemoteApp environment.You can recreate the problem easily by doing the following: Again, only if the Caps Lock/Numlock keys are the first input. However, if you right click a folder, select"open in new window", click the search bar in the new window, then hit the caps lock key, it will. For instance, if you launch a published instance of File Explorer, click the search bar, and hit the "Caps Lock" key, the issue doesn't happen. They don't get keyboard sync information until text is input. It appears that when new Windows are generated from the published application The Caps Lock/Num Lock keys are inverted when the application opens a new window, a text field is selected, and the “Caps Lock” or "Num Lock" keys are the first input. For example, the keyboard indicator shows Caps Lock is off, but capitalizes all characters in In Server 2012r2 and Server 2016 RDS environments, while in published RemoteApp applications, the Caps lock/Numlock keys become inverted from the local computer.
While investigating I've read every post/article I could find on the topic and wanted to share my findings, as well as include instructions how to recreate the issue which I haven't seen This issue has been a thorn in my side for the past several months.
0 kommentar(er)
