Last post Nov 30, 2007 12:52 PM by rippy
Nov 28, 2007 02:10 PM|rippy|LINK
I'm testing migration from HMC 3.5 to HMC 4.0. All migrated users can see address lists and users from other organizations through OWA. New users created on the HMC 4.0 don't have this problem. Access via Outlook AnyWhere isn't affected at all.
Nov 28, 2007 06:46 PM|dbrannan|LINK
How are you doing the actual migration? Are you using the migration toolkit and using the Import namespaces?
Nov 29, 2007 09:31 AM|DmitriG|LINK
Check msExchQueryBaseDN attribute fo this user. looks like it is empty. I'm not sure why it happend, AFAIK, if user has been created by any version of HMC, this attribute must have correct value (organization OU DN for business user).
Nov 29, 2007 02:01 PM|rippy|LINK
Yes. you are right. For some reason the msExchQueryBaseDN attribute is empty.
I'm using Hosted Messaging and Collaboration version 4.0 Migration Kit with a little difference in migration process. I didn't import business organization. We have our own CP (control panel) so I created a new reseller OU and business organization with
CP instead of import. With CP I assigned a plan for organization and users, assigned SMTP domain and then I migrated user accounts (ADMT 3.0) and imported them via ImportUser.xml. I moved mailboxes and then imported them using ImportMailbox.xml. I don't think
that my simplification is the source of this problem because a new user created inside the same organization isn't affected.
Thank you for advice.
Nov 29, 2007 03:02 PM|DmitriG|LINK
Well, it explains everything. [8-|]
Procedures Hosted Active Directory Import::ImportUser and Hosted Email 2007 Import::ImportMailbox do not care about proper value for msExchQueryBaseDN attribute. It means, that if it wasn't populated before import, it will not get proper value after ImportUser/ImportMailbox
calls. You do Side-by-Side migration, so, you have to assign proper value to msExchQueryBaseDN after ImportMailbox call. I do not think that ADMT will help you because new value for msExchQueryBaseDN must reflect new/target domain name and can't be blindly
copied from old/source account.
Nov 29, 2007 05:35 PM|DmitriG|LINK
I do not think that ADMT will help you ...
Just found a conformation in NeboMigrationWhitePaper.docx (page 71):
Important: You may see that the
users were migrated with Warnings or Errors. Certain
user attributes, including
Exchange Server–related attributes and “otheWellKnownObjects” cannot be migrated by ADMT. This is an expected error.
Nov 30, 2007 12:52 PM|rippy|LINK
You are right, ADMT can't help. I expected to cmdlet move-mailbox can do this job because it copied proxyaddresses and mailbox limits. I was wrong the value of this attribut is different on source and on target so it can not be transferred.
Thank you for your help.