Update Test Execution version using command line (via Jenkins) or in any other way
We are running Test Execute on an Azure vm whcih is created automatically using an image, this image has Test Execute already installed but, since it was created long ago the Test Execute version is old. we are writing the scripts in Test Complete and update it frequesntly and at some point the versions are not matching, instead of creating each time a new image that will include the latest version of test execute I thought maybe there's a way to update the test execute silently on the original image once the vm is created and loading or to do it using command line or any other way via the Jenlkins pipeline?
If there's a way to update the existing version somehow it is great.
If the re's a way to install it from scratch after downloading the latest version on a clean win 10 vm that's alos good but, in this case we will need to update the following web page- Gemalto Sentinel ACC: Configuration of where the license server sits so it can fetch the floating license. and maybe to do it on the server side as well so maybe it is more complicated?
If anyone knows of a way to do that I'll be greatful.
Is there way to run the installer as admin. we are struggling by passing the UAC approval, we tried using this command like which doesn't seems to work - bat "runas /user:Administator TestExecute1481.exe -SilentInstall", it still saks for user name and password.
Is there a way to by pass the AUC via command like?
> Is there a way to by pass the AUC via command like?
Try powershell with the Runas verb: https://devblogs.microsoft.com/powershell/v2-quick-tip-starting-a-new-elevated-process-from-a-powers...
/Alex [Community Champion]
[Community Champions] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Champions]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Champion] signature is assigned on quarterly basis and is used with permission by SmartBear Software.
The truth is that we decided to take a different approach and instead of using Azure vm's we will user different technology like Packer