Please fix remote command prompt and powershell
It seems as though the remote command prompt and powershell have declined in performance rather than improved. It has always been buggy and had refresh issues, but now scrolling does not work as expected -- I now have to manually scroll down (this used to work). Also, if the command prompt or powershell dialog is minimized, it is non-responsive when restored -- I have to kill it and re-open a new instance.
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Stuart Hill commented
Two and half years later and the powershell and cmd terminal options offered by Atera is still a bit disappointment.
-
Avixia Admin commented
With the recent AI updates for Command Prompt and Powershell, you guys are now using Console redirect or something. This is causing major issues with copy/paste, backspacing text, editting text in place, etc...
We troubleshoot and repair a lot of issues via console to minimize disruption to end-users. These recent changes have made the consoles much less useful and has become disruptive to our usual workflows.
We are currently writing out commands in notepad - and then copying and pasting into the console window line-by-line because of how problematic this has become.
Please give us the option to revert to the old console (prior to enablement of AI features) until this is figured out.
-
Support Two commented
The recent Updates to PowerShell have exacerbated this issue to a fever pitch.
Now CTRL + ← and CTRL + → no longer move the cursor to the beginning or end of a word, instead they run a command.
↑ is now completely non-functional.
The cursor is now permanently stuck in Replace mode rather than insert mode, effectively meaning you cannot make any mistakes while typing unless you wish to retype everything all over again.
And as aforementioned, all the previously existing issues such as the console not correctly updating with new data,
The new input line often having previous command outputs running overthem
The cursor still has no accurate depiction of its location.Instead of moving forwards the introduction of AI has moved things backwards. Frankly I would rather they roll this update back, then fix the powershell console so that it works as it does when connected to a device, or using it on your own device, or when accessing it through any other form of remote console connection such as winRM or Putty before pushing anything new out.
How about instead of introducing new features which no-one wants, you fix the stuff people are already asking for.
I've seen the top rated posts on this forum, 14 votes is the equivalent of 14000 on any other forum.
-
George Harb commented
Exactly where is the scroll bar in the command window. If the output scrolls of the window, there is no way to see it.
-
Alessandro Hernandez commented
Moved from Kaseya and although Atera is vastly superior for our needs the shell interface needs work for sure. There's always that extra "space" at the end of any line of code and say you run certain commands, you won't see the live result like you would in other solutions such as Kaseya's VSA. for example, "sfc /scannow" just a black screen until it's finally done, there are others like this.
-
Stuart Mitchell commented
Agreed! We only just moved to Atera and we find the PowerShell integration to be quite glitchy - Sometimes the bottom line is cut off, slow to open, etc.