Hi Brunosousasf,
This usually comes down to one of 2 things:
-The msExchHomeServerName attribute for those mailboxes might still point to the old server. Changing that is more of an Exchange/ADSIEdit action. Since this is an EV forum, and I'm a Veritas employee, it's risky for me to discuss the ways to update that, though I'm sure that either you or your domain admins and/or Exchange admins know how to update this.
-Or, it's an issue with bidirectional trusts between the domains, which causes an issue for us to gather the details we need to provision them. Same as above, I shouldn't delve deep in to offering advice about domain trusts.
Honestly I'd kind of doubt the second option; it sounds like your trust was already ok since they were working before when they were on separate servers that truly were in separate domains. And keep in mind these are just best guesses based on my experience; a dtrace would tell you more. Speaking of dtrace....
You can find out specifically what the attribute in error is by dtracing exchangepolicysynctask (this is just our really old name for Provisioning) while running the Provisioning Task again. Usually you can see the error show up when we perform an LDAP query regarding the mailboxes, or when we perform a GC lookup for them during the trace. Hope this helps!
Hi !
The Dtrace of exchangepolicysynctask :
|Event ID: 41126 The Exchange mailbox provisioning task found some mailboxes that are not eligible for processing by this task.|This task will process mailboxes on every Exchange Server in this domain that has been added to the Administration Console.|If you want this task to process such mailboxes, add the host Exchange Server to the Administration Console.|See the provisioning task report for further details.|Task: Exchange Provisioning Task for ulis-ir.com|Domain: ulis-ir.com
Thanks.
