Has anyone else noticed that menus in Tessitura are "Reverse-aligned" when the application is delivered over remote desktop?

I recently upgraded our RDS deployment from Windows Server 2008 R2 to Windows Server 2016, and noticed a behavior that I had seen before in the Tessitura Sandbox, but never anywhere else (we're self-hosted, so I don't know what this is like on RAMP). Basically, on our old 2008 R2 RDS deployment and when launching the client locally, menus inside the client (File, GoTo, Tools, etc) appear traditionally, with the left edge of the list of menu items aligned with the left edge of the menu itself. In other words, when you click on a menu, you can next expect to move your mouse cursor down and to the right to mouse over the menu items.

In contrast, on our new Server 2016 RDS deployment (and in the Tessitura Sandbox, which I believe is on 2012 R2 or thereabouts), the RIGHT edge of the list of menu items is aligned with the right edge of the menu itself. Here's a visual aid:

Has anyone else noticed this? I can't be the only person who finds this irksome. Would love to know if there's a fix.

Parents
  • Nick, It appears that's a Windows user registry setting and it applies to all applications.  1 for left and 0 for right.  Tessitura doesn't change this setting.  Notice that with it set to 1 the file menus shift to stay withing the RDP session boundaries.  That may be MS's new desired experience. 

Reply
  • Nick, It appears that's a Windows user registry setting and it applies to all applications.  1 for left and 0 for right.  Tessitura doesn't change this setting.  Notice that with it set to 1 the file menus shift to stay withing the RDP session boundaries.  That may be MS's new desired experience. 

Children
  • AMAZING!!! I hadn't noticed that this was also applying to other applications within my RDP sessions, so I assumed it was something with Tessi. So odd that the left dropdown is set by default on a fresh Server 2016 installation... Actually on further reflection, it's only the server I have Remote Desktop Services installed on. On our other Windows Server 2016 machines, this key doesn't exist (so presumedly uses the default value of 0.

    Setting this value to 0 and re-logging in solved it. Thanks Chris!