User Provision process runs in error - the Exchange cmdlets (Enable-MailUser, Set-MailUser) will be send to different domain controllers. Could I set a defined domain controller for all Exchange activities?

Werun in a problem with the provisioning wizard. The environment is configured for a complete coexistence. For directory sync, mail flow and free busy we use the Quest CMN components. Only groups will be provisioned by MNE. (Our setup is tested in the test environment with one limit - we only use one domain controller.)

We defined a small user group for a pilot phase in the productive environment. During the provision process 50% of the users in the collection run in errors. In the MNE log we see the error "the object couldn't be found on" "domain controller 2". In the MNE profile for section Active Directory we defined the "domain controller 1" with the full qualified host name.

During our troubleshooting we took a look on the Exchange audit logs. There we saw that the Exchange cmdlet "Enable-MailUser" was processed. But the next cmdlet "Set-MailUser" not. There is only one difference the first command use the option of the domain controller the second not.

What we have to set that all Exchange powershell cmdlets will be executed on one domain controller?