It's important to keep in mind that actions you see in the left pane of individual asset and user pages are run in the security context of the user initiating the action. More specifically, the username/password combination of the user account your web browser is running under is used to execute the command. This implies that, if an action requires administrative privileges on the target machine (and some do), the user who opened the web browser and clicked on the action must have those administrative privileges on the target machine. Scanning credentials submitted in the Scanning\Scanning Credentials section of the web console are *not* used to run asset or user actions.
To run an asset or user action as a different user, do one of the following:
- Run the browser you're accessing the Lansweeper web console with under that user. Shift+right-click your browser shortcut and select Run as different user. You'll be presented with a popup to submit your username/password combination. Use the format NetBIOS domain name\username for domain users and .\username for local users. In the sample screenshots below, we ran our browser under domain account lansweeper\administrator.
- Change the action path of the action you are running to include runas.exe. Runas.exe is a tool built into Windows that can be used to run processes under different users. Browse to the Configuration\Asset Pages section of the Lansweeper web console and place the below around your action command, inserting your own username and action command into the syntax. Use the format NetBIOS domain name\username for domain users and .\username for local users. The action will be run under the specified user. In the sample screenshots below, we used runas.exe to run the Remote Control tool (lsremote.exe) under domain account lansweeper\administrator.runas.exe /profile /env /user:<your user account> "<your action>"