Working With TestExecute Under Limited User Accounts

TestExecute can work both under administrator and non-administrator (limited) user accounts. You need administrator permissions to install TestExecute, but you can install it for any user on the computer. To do this, select “Install this application for anyone who uses this computer” during the TestExecute installation.

Non-administrator accounts may have limited access to the file system, Windows registry and running applications - as set by your system administrator. Your user account permissions determine what you can and cannot do with TestExecute. Keep in mind the following limitations when running TestExecute under a non-administrator account.

• By default, the members of the Users group cannot work with processes created by other users.

• TestExecute launches tested applications under the same account under which it is running. So, your tested application will have the same permissions as this account.

• To test an application running under another user account, you must launch TestExecute as Administrator, and run the application in the RunAs mode.

• Limited user accounts may have no read or write permissions for some folders. For example, by default, the members of the Users group have no write permissions for the Program Files folder. TestExecute cannot access or change the files and folders for which your account has no permissions.

• Users may have no permissions to access some registry keys. For example, by default, the members of the Users group cannot write to the HKEY_LOCAL_MACHINE registry key.

  For example, the HKEY_LOCAL_MACHINE node is used to register COM objects. If your tests do this, you need to run TestExecute as Administrator.

• If you reboot the computer as part of your test, TestExecute saves the domain name, user name and password for logging on in the following registry key:

  HKEY_USERS\{USER_SID}\Software\Microsoft\Windows\CurrentVersion\RunOnce

  TestExecute removes this data from the registry once it is launched after the restart. However, if the specified user account does not have permissions for the above-mentioned registry key, the logon parameters will remain in the registry and will be used at the next Windows startup.