I'm doing a cross forest AD and exchange migration (exchange 2007->2010). We needed to get the users over into the other forest, so I first copied all their accounts, passwords, and groups over using ADMT. As I understand it, ADMT excludes msExchange and associated attributes by default. Now that I have mailbox servers build, I see half the users who exist in AD and were migrated over to the new domain now showing up in the Recipient container. If I click on them in there I see a few erros: "The properties on this object have invalid data. If you click OK, default values will be used instead...." and "Database is mandatory on UserMailbox Database is mandatory on UserMailbox" (says it twice, strangely enough, with different spacing on each line. :)) This tipped me off that maybe the old attributes made the trip and are still pointing to the old 2007 server. Sure enough, if I look using my LDAP tool on these items, they are there. Question: Why didn't ADMT exclude these by default, as I keep reading it does? Question 2: Do I need to redo the migrations or will a PrepareMoveRequest resolve these problems? Strangely enough, I migrated a test user who had a mailbox in the domain, and manually excluded the msexch*.* attributes and they of course, don't get copied over. However, when I click on this user in the Recipient area, it gives me the same error message "The properties on this object have invalid data..." ?? Thanks

I also notice that on all users in the new domain, they do not have the mail, and proxyaddress (SMTP) attributes. I think these are needed for the PrepareMoveRequest script. Is there a way to get these to come over? It seems I lost the attributes I needed, and got the ones I didn't (exch) in the migration. Thanks

Hi there, Your understanding is correct that by default ADMT is excluding all Exchange Attributes, however, it convert the user account created or merged by ADMT to Mail Enabled User before running Prepare-moverequest.ps1. So my questions are: When did you click the user account and receive the error message? Before running Prepare-MoveRequest.ps1 or after? And what attribute did you see in LDAP tool? What is the error recorded in Application event log? THanks. REfer to:http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx Fiona Liao TechNet Community Support

I have never run the prepare-moverequest.ps1 script. I get the error when double clicking on the users in the Recipient area of the new Exchange- the users appeared in here automatically (the ones with mailboxes in the old domain anyway - not about 400 of 900 total AD users). I used ADExplorer to view the attributes and verify all these users showing up in here had the mxexchang*.* attributes and values from the old domain. I also verified that I must exclude the msexchange*.* attributes manually for these not to show up. The users also do not have the mail and proxyaddress values - the values I believe needed for the preparemoverequest script to work. How do I get these over and remove the msexch*.* ones? Thanks

Hi, Thanks for your update and clarification. I am suspecting the issue is caused by ADMT tool: Administrators can define a list of attributes that are excluded from each migration. This is called an attribute exclusion list. By default, when using the ADMT console, state information for attributes that are configured to be excluded is stored in the user interface (UI) and included in the exclusion list for the next migration. Scripting and command-line attributes do not have state information. Therefore, they are not stored in the UI. These attributes must be added to the attribute exclusion list for each migration operation, either by means of the attribute name or by means of an option file. See http://blogs.technet.com/b/askds/archive/2010/06/19/admt-3-2-released.aspx I'd suggest you verify the exclusion list and migrate user again. If there is more questions on ADMT configuration, please feel free to post the question in AD forum. Your understanding would be appreciated. Meanwhile, I've tried to involved a next level support engineer in this thread. Hope the issue is resolved soon. Fiona Liao TechNet Community Support

Fiona, thanks for your reply. I know this is the way the UI is supposed to work, but it did not. It brought all the exch*.* attributes across by default. I did not select these to be excluded, because I thought they were supposed to be excluded already. But lo, they are now there. So my question now is, how do I remove them? Do I need to delete all the users, re-migrate and specifically call these attributes out in the UI to have them excluded? I am hesitant to do this because the users have subsequently been moved to appropriate OUs, so I do not want to lose that work. My other question is - the mail and proxyaddress attributes did not come across, but as I understand it, I need these SMTP email addresses in the new domain so that users mailboxes can be migrated from old domain to new. Why did it remove these attributes, but bring across the msexch* attributes? Thank you for your advice.