This document explains how the Active Roles Management Shell selects which service it connects too.
The service is returned from Active Directory’s Global Catalogue. Active Directory sets the priority of the selection of the service.
The Active Roles Management Shell follows the following sequence when selecting a service:
1) Localhost: If the shell and service are running from localhost, then it will select the local service without looking further.
2) Cache: it will check the cache for the service path, if any is present there then it will select that same service. Cached files are found here:
C:\Program Files\Common Files\Quest Shared\ARSADSITempFiles
3) Forest: it will get all the Services present in the forest and filter them according to:
a) The provider will try to connect to any Administration service that is a member of the replication group.
b) Specified Service Name.
As per current product design the only two options available to influence the connection would be:
1) Use cmdlet: connect-QADService -service 'path of the service' –proxy
2) Clear all other files from cache and keep the one you’d like to connect to
3) Create a script to connect to the desired service(s). The script can have a list of all available services according the desired connection priority. The script can then check each service one by one, if the 1st service fails then it should attempt a connection to 2nd service from that list and so on.