Using the /agent argument to start remote suites

Best practices, code snippets for common functionality, examples, and guidelines.
Posts: 6
Joined: Wed May 08, 2019 7:57 pm

Using the /agent argument to start remote suites

Post by ian807 » Wed May 08, 2019 8:00 pm

I'm running Ranorex 8.1.2+git.31d95a93

I have an agent on a remote machine (hou-ranorex10). When I use the remote tab, I connect to the remote system and can start my test suite without problems.

I need to schedule unattended operation. One method I've tried is to use the command line "Scripts.exe /agent:<agentname> method decribed in the Ranorex documentation on my development system.

When I run the Scripts.exe file like so: "Scripts /agent:hou-ranorex10"

All that happens is that the Scripts start running on my development system, NOT the remote hou-ranorex10 system. In fact, no command line argument I've tried thus far as worked other than scripts /?, which lists no option for the agent.

User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA

Re: Using the /agent argument to start remote suites

Post by Support Team » Wed May 08, 2019 9:01 pm

Hi ian807,

The /agent command line feature was add in Ranorex 8.3 (release notes). You will need to upgrade to Ranorex 8.3 or newer in order to take advantage of this feature.

I hope this clarifies why it does not work for you!