Powershell & CMD.exe Launch Options
Add ability to launch both CMD.exe and PowerShell as either the SYSTEM user or Logged-In User.
Hello, Thanks so much for submitting your idea! It’s currently under review by our product team, and should a decision be reached to develop it, we’ll keep you in the loop!
-
Nick Maynard commented
this is crucial when running winget or WSL. This should be implemented. At present I have no way have running winget or WSL as the end user
-
Marco Miele commented
This feature is really important.
This is because many times we find ourselves having to give simple commands which however must be given as a logged in user and not as system.
Until now I have used Ninja One which allowed you to select the following options:CMD:
--> USER 32Bit
--> USER 64Bit--> SYSTEM 32Bit
--> SYSTEM 64BitPOWERSHELL:
--> USER 32Bit
--> USER 64Bit--> SYSTEM 32Bit
--> SYSTEM 64Bit -
Rob Klarner commented
This is present in many other RMM solutions and is so useful.
-
admin admin commented
Most of every other RMM i have used has this!
This would be great as sometimes you need to be in a remote shell/cmd as the logged in user. i.e cmd net use, to view network drives or add and delete them.
-
Adam Beer commented
This would be super helpful. Sometimes we just want to run a quick command through CMD or Powershell as the current user. But in order to do this, we have to create a script, then run the script.
Being able to open a command prompt as the user would be fantastic.
-
abigael abigael commented
When we go to access terminal for a command line for windows device, it would be nice if it was ran by the root or it could be run as the currently logged in user.
-
Joris Schepers commented
Would really love this one!
-
Lenny Firmin commented
A drop down as current user or for it to have the ability to read available enabled users on file would be great if a shared device
-
Synergy MSP IT Support and Consulting commented
Can I use the command prompt on the remote computer with Atera as the current user, not as a system?