Forum Discussion
ISSUE - WON'T FIX - Failover Cluster Manager via RDP
Dear Windows Server insider Team,
I would like to raise awareness about a long standing issue, I hope you can address in Windows Server vNext.
Problem: The context menus (right click) in Failover Cluster Manager MMC have a problem with the graphical display, only when used via RDP. The menu pops up correct but when you use the keyboard (cursor keys) or to navigate to a specific item, then the menu disappears and you are only seeing the one selected.
As Windows Admin Center 2311 Cluster Manager extension is still not up to par with featureset and especially performance, even years after launch, there is - very unfortunately - still a usecase for the traditional MMC.
Same with my earllier posted wish for Server Manager and missing print management in context menu, I sincerely hope you can look into this.
- After all of Karl's help, I am disappointed to say that we will not be fixing this bug.
The feature team investigated and shared some notes with me:
* The issue is related to screen scaling factors > 100%. This can happen both locally and with RD.
* The issue is related to various custom control implementations that were made in the WS2012R2 timeframe.
* The team is prioritizing work on cluster management functionality itself, rather than the user interface, particularly since the bug has been there for roughly ten years.
The Windows Admin Center team plans to continue investing in extensions and tools; our goal is to super-set the Win32 management UI eventually. So, I hope to turn FCM into modern, web UI rather than Win32 custom controls.
Thanks,
Michael
Repro:
via an RDP Session launch FCM mmc and open context menus, e.g. Roles then navigate through the options with mouse or cursor keys. only the highlighted will be visible other disappear.
MSBernsteinMicrosoft
Hi, Karl. My contact in the Failover Cluster Mgmt team wanted to know the exact resolution of your display and if you had high DPI enabled on either the host or the guest side. We're having some trouble reproducing the issue on our side - thanks!
Michael Bernstein
Windows Server EngineeringHello MSBernstein I am sure high-dpi (font scaling) was not enabled I am trying to repro it to provide more details.
