Suggestion: Windows - Full shell experience. #107
Description
The SAC is great to provide basic troubleshooting, but for the majority of the management scenarios it does nothing.
For example, we have a Microsoft Configuration Manager hierarchy here that uses several Cloud Management Gateways, that uses Virtual Machine Scale Sets behind a load balancer.
The instances are completely isolated, with the exception of the web app communication.
Things that would help:
- The ability to scroll. Sometimes copying log files is not possible, and without scroll is impossible to read through the console.
- Backspace to delete only a character, instead of a section up to the next 'separator' character.
- The ability to use special keys like 'Home', 'End', and combinations, like 'Ctrl + Arrow', etc.
- If you hit one of these special keys, or a combination of them, the text already written is replaced completely by those weird character combinations, like [A, [3~).
- When running on a window that have a different background color, sometimes the console doesn't completely cover the original background, leading to a background color for text and other for empty space.
- When using the console through Az CLI in a PowerShell host, I couldn't exit the console without killing the process. Tried the key combination from the documentation, but with no success.
I know this is not trivial, and my knowledge doesn't fully range over what it takes, or how hard it is to implement something more sophisticated, but the current experience for Windows VMs is just awful.
Are we planning on having something in the likes of when you access another VM using PowerShell remoting? Where you have a PowerShell process running on the target machine, on the original shell.
The feeling I got it's like we had to develop something for Linux, and tried to port to Windows, while we have the greatest shell in the world installed in every single Windows computer.
Thank you for the time!