So we have a forest that is controlled by CompanyA. There is a child domain in that forest controlled by CompanyB. The two companies implemented their own instances of ARS. I work for CompanyA.
We loaded the ARS cmdlets on a server where the ticketing product (ServiceNow) lives so the product can interface with the cmdlets to make changes in ARS automatically. It works rather well except when the cmdlets try to connect to CompanyB's ARS servers since we're in the same forest. We had them use the connect-qadservice cmdlet to connect to one of our ARS servers but we don't want that to be permanent.
Is there a way to tell the cmdlets to ignore CompanyB's ARS servers? In addition, is there a way to test if an ARS service is online? Our servers are rebooted on a routine basis as part of maintenance and due to the size of this particular environment, it can take 20-30 minutes for the service to build before it's available for service.
We do have the ticketing folk working to do this automation via SPML but the powers that be wanted something "yesterday" so we have to keep this method going until they can figure that part out.