Why is Arguments: -host "xx.xx.x.xxx" required in Tests in order to RDP to a defined SUT?

Hi there,

We are using EPM v7.1.1, build 1633 on Windows.

We have found that the only way we can get a test run to connect to our SUTs is if we add the actual IP of the desired SUT in the argument field in the test. These are all 1) defined correctly in the Admin section, 2) been ping tested from the EPM box, 3) been directly RDPed to from other boxes including the EPM box itself.

This has allowed us to run tests, but requires many copies of certain tests in order to be able to easily run them against different SUTs. Without the argument, and even sometimes with it, we end up getting a purple exception in the results logs that says: “Remote Connection Unavailable”.

Does anyone have any ideas why this is required for us? Or is there a configuration change we need to make? I know I have not needed this workaround in previous versions (at other companies).

Adding the argument at the SUT level should not be required. In order version of ePM, a licenser host argument was required, but that functionality has moved to system preferences (see here: Configuring System-Wide Test Defaults)

If you leave out the argument, what error is ePM reporting?

To be clear, we are having to add the (-host “xx.xx.xx.xxxx”) argument to each test, otherwise we get the purple “Remote Connection Unavailable” exception in the Results. This means we have to make multiple copies of tests in order to be able to specify a different IP in the argument so a connection to different SUTs can occur. We are still testing various options, but so far, we have not been able to get a test run without the extra argument.