RunAsRob details English Runas Rob details German

RunAsRob details

Differences between RunAsRob, RunAsAdmin, RunAsService and RunAsSpc:

RunAsRob RunAsAdmin
a part of RunAsRob
RunAsService
a part of RunasRob
RunAsSpc
the classic tool
Genererally Contains RunAsAdmin, RunAsService and
can control allowed applications by an encrypted file, which can send anyone to use it.
Allowed application controlled by registry settings.
Need no encrypted file.
Several applications can be configure at one go.
Support of wildcard *
Compatible with group policy.
The application is running as service automatic after you turn on the computer and before any user is logged in.
Interaction between user and program isn't possible.
Allowed applications and credentials controlled by an encrypted file or clear text.
Logon as . . . .
another user Run application under user account from encrypted file. This can be an administrator or any other user account.
Requires no installation procedure.
Not possible Not possible Possible
system Run application under system account with highest privileges and without the popup of an UAC dialog.
Suitable for installations, updates and patches.
Disadvantage: A service is not a complete account. Its missing a user profile and an own HKU registry path.
Possible The only possible login option. Not editable Not possible
administrator Launch application with administrator permissions under the own fully account of the limited user with his own profile and enviroment.
Suitable for running programs who need user properties like office.
Possible Not possible Not possible
netonly Application use logon credentials from encrypted file for remote connections. Not possible Not possible Possible


Detail guidance 1:

Command line arguments of RunasRob:


Detail guidance 2:

Edit the Registry Key of RunasRob:
HKEY_LOCAL_MACHINE\SOFTWARE\RunasRob

Here you configure the values AllowedPath, ServiceMode, LogonFlag directly or over central group policy in a domain.
Changes will take effect after restart of service RunasRob
Warning, serious problems might occur if you change the registry incorrectly.
Registry RunasRob


FAQ:

  1. The restriction of the free version for private use is the start-up window with the license information,
    which appears at random intervals, even if you set the switch /quiet.
  2. Arguments to the launching program at runtime are not possible.
  3. Environment variables can use like >> %windir%\system32\regedt32.exe\CompMgmtLauncher.exe <<
  4. Wildcards can set as authorized path. Example: >> *\updates\flashplayerversion*.exe <<.
  5. Running on Server 2008, Server 2012, Vista, Windows 7, Windows 8, Windows 10, 64 and 32 Bit
  6. Authorize only a specific user or group to run a an application.
    This can be achieved over folder permissions to the program file, encrypted file or the folder.
  7. Program arguments. Passing arguments to my application are not working, because quotation marks or complex arguments are not accepted in RunasRob.
    Workaround this problem by a one line batch file with your complete applicaton call include all arguments.
    Run this one line batch file over RunasRob.
  8. Errors Codes.
    Most errors are system errors which are returned from runasrob to user.
    This system error codes are explained by Microsoft on
    https://msdn.microsoft.com/en-us/library/ms681381.aspx

Contact:

For any suggestions, errors, questions, specific requirements or adjustments please contact:
runas@robotronic.de


Licence:

RunasRob is only free for private use.
For companies and other organisations we deliver a licensed version, registered to the organisation name.
Order RunasRob >>>
Download RunasRob >>>


Date: 2018-11-08
Data protection
Imprint