Hello.
I'm trying to enforce some policies (in particular, assigning address book policies and disabling OWA/Activesync) on our mailboxes using script agent.
I'm using scripting agent configuration like this:
<Feature Name="MailboxProvisioning" Cmdlets="enable-mailbox,new-mailbox">
<ApiCall Name="OnComplete">
if($succeeded) {
if ($provisioningHandler.UserSpecifiedParameters["Identity"] -ne $null) {$user = $provisioningHandler.UserSpecifiedParameters["Identity"].ToString()}
else {$user = $provisioningHandler.UserSpecifiedParameters["Name"].ToString()}
if($provisioningHandler.UserSpecifiedParameters["AddressBookPolicy"] -eq $null) { Set-Mailbox $user -AddressBookPolicy ABP_Default }
Set-CasMailbox $user -OWAEnabled $false -ActiveSyncEnabled $false
}
</ApiCall>
The problem is that we have three domain controllers in the AD site. So, if I use new-mailbox cmdlet immediately followed by set-mailbox (or any other mailbox or user operation), Exchange can query different domain controllers. AD replication isn't instant,
and I got errors because cmdlet cannot find AD object.
If I configure all setting by himself, I can use Set-ADServerSettings cmdlet, and all queries in single powershell session will be done to one DC. But mailbox tasks in our organization can be done by different people in different ways, so I want to use scripting
agent to enforce correct settings.
Is there any way to tell scripting agent to use the same DC in affected cmdlets and in agent's script blocks? The only way that I can think of is to use Set-ExchangeServer to set static DC configuration, but I want to avoid such extreme thing.
Script agent - problem with domain controllers.
