• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 13 subscribers
  • Views 12221 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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?

jens.kleiner2
over 7 years ago

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?

Parents
  • 0 over 7 years ago
    Hello Trevor,
    the MNE Group Provision Process is running fine.
    1.) Our MNE release is 4.13 - tomorrow we will update to the latest release.

    The User Provision runs in errors. Two different Exchange cmd-lets will be executed. The first to enable the mail user and some milliseconds later Exchange should set an additional value. Both jobs are started by the Quest provision process. The technical problem - only the first command has the option attached "-DomainController hostname", the second not. So Exchange can choose to which global catalog system will be used. In our case on one other AD system. There is the user object not mail enabled.

    Currently we check to define a static Exchange Domain Controller and Global Catalogs so that all commands will be execute on one AD system.

    Kind regards
    Jens
Reply
  • 0 over 7 years ago
    Hello Trevor,
    the MNE Group Provision Process is running fine.
    1.) Our MNE release is 4.13 - tomorrow we will update to the latest release.

    The User Provision runs in errors. Two different Exchange cmd-lets will be executed. The first to enable the mail user and some milliseconds later Exchange should set an additional value. Both jobs are started by the Quest provision process. The technical problem - only the first command has the option attached "-DomainController hostname", the second not. So Exchange can choose to which global catalog system will be used. In our case on one other AD system. There is the user object not mail enabled.

    Currently we check to define a static Exchange Domain Controller and Global Catalogs so that all commands will be execute on one AD system.

    Kind regards
    Jens
Children
No Data