-
Título
When to use the -Proxy switch with Active Roles Management Shell PowerShell cmdlets -
Descripción
When using the Active Roles Management Shell PowerShell cmdlets, you may run into the some of the following issues:
- Actions performed using the cmdlets are not logged in the Active Roles change history.
- Virtual attributes are not accessible.
- A user that's able to perform a specific action in the MMC or Web Interface is receiving 'Access Denied' when using the cmdlets.
-
Causa
The above are all expected behavior when not using the -Proxy switch.
-
Resolución
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:
- In each use of an Active Roles cmdlet, make sure to use the -Proxy switch to tell the cmdlet to connect through the Administration Service.
-OR-
- Begin by using the following cmdlet:
- Connect-QADService -proxy
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:
$ARSession = Connect-QADService -proxy -service "MYARServerName"Set-QADUser $obj1.DN -ObjectAttributes @{edsvadeprovisiondeletiondate = $deprovDate} -Connection $ARSession