Hi yurik,
In the Setting for TestExecute program you can select "Run this program as an administrator".
- Open the Testexecute installation folder (usually C:\Program Files (x86)\SmartBear\TestExecute 11\Bin)
- Right click on TestExecute
- Select Properties
- Go in the Compatibility tab
- In the Settings panel select "Run this program as an administrator"
- Click on "OK"
The next time TestExecute will be run it will be as an administrator. Don't forget to decrease the security level to avoid prompt at starting.
You may control with the Task Manager that Test Excecute is executed with "Elevated privilege".
Regards,
Christophe
Hi Christophe,
I've tried "Run this program as an administrator" but the application still behaves differently: When I start the application manually it behaves, but when I start the application from a TC script running on Master machine it still misbehaves.
I'll explain the setup one more time: The script is running in TestComplete on Master PC and starts TestExecution on the RemoteHost. TestExecution runs a script that starts the application that I'm testing. Master PC runs WIN7 , Remote host is WIN 8.
Now, there are several ways I've found to work around this issue:
1. If I use TestedAppObj["Run"] to start myApplication then possible workaround it to start TE with elevated privileges using Scheduled Tasks when PC boots up. However this means that if I restart TE from Master then myApplication stops behaving.
2. If I use TestedAppObj["RunAs"], providing the Domain, Username and Password of the remote host , then myApplication behaves even if TE was started from Master PC.
So it looks like myApplication has to run with elevated privileges, so even if I tick "run as administrator" for TE and myApplication executables, when I start them remotely they are still running in limited privileges (even if TaskManager shows that TE is in Elevated mode)
