When using the Active Roles Management Shell PowerShell cmdlets, you may run into the some of the following issues:
The above are all expected behavior when not using the -Proxy switch.
By default, the Active Roles Management Shell PowerShell cmdlets will connect directly to Active Directory, bypassing the Active Roles Administration Service. This means that things like Change History, Policies and Access Templates do not come into play. In any of these cases, do one of the following:
When using the Connect-QADService -proxy cmdlet, it is not necessary to use the -proxy switch on all subsequent cmdlets within the same script.
For multi-AR Server environments, it can be possible to direct script traffic to a "less busy" server using below cmdlets: