We have released the updated version of the Microsoft Transporter Suite. The download is available here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=35FC4205-792B-4306-8E4B-0DE9CCE72...
Updated Jul 01, 2019
Version 2.0
Blog Post
Is anyone else having performance issues with Transporter? The Hub Transport (where it's installed) appears to eat a CPU core while migrating users (brand new Xeon Quad Core 1.8GHz, not the fastest but still not exactly sluggish) and takes an age (20mins) to do 4,000 small emails with no attachments using command line PowerShell with 'quiet' switches.
The same copy - on a client PC running Outlook using the old "IMAP to Exchange profile drag and drop" trick, is so much faster - leading me to believe our performance problems could be caused by PowerShell, which hardly strikes me as streamlined having worked with creating and calling PowerShell Engines and Pipelines in C#. (No this isnt an option for a bulk migration, we have to have minimal user interaction)
Even if you do multiple mailboxes at once, and each uses a core, there is no way this will scale to doing over 2,000 users mailboxes in a reasonable time - some of which have over 10,000 mails.
We are also getting many warnings, possibly where subjects are blank and similar instances noted above by others. So even if we manage to get the mail in we arent at all confident about the quality of the data transferred.
Add to that the lack of proxyauth support (surely this was tested against non Exchange IMAP!?) mentioned above and things are going to be very very difficult.
Please Microsoft, give those of us willing to make the switch from a competitor a good way to do it. I spent a lot of time convincing people how great Exchange 2007 would be and plan to implement the full UM/OCS experience, hopes are high and I need to deliver something better than a crib sheet for users to perform a DIY migration.
The same copy - on a client PC running Outlook using the old "IMAP to Exchange profile drag and drop" trick, is so much faster - leading me to believe our performance problems could be caused by PowerShell, which hardly strikes me as streamlined having worked with creating and calling PowerShell Engines and Pipelines in C#. (No this isnt an option for a bulk migration, we have to have minimal user interaction)
Even if you do multiple mailboxes at once, and each uses a core, there is no way this will scale to doing over 2,000 users mailboxes in a reasonable time - some of which have over 10,000 mails.
We are also getting many warnings, possibly where subjects are blank and similar instances noted above by others. So even if we manage to get the mail in we arent at all confident about the quality of the data transferred.
Add to that the lack of proxyauth support (surely this was tested against non Exchange IMAP!?) mentioned above and things are going to be very very difficult.
Please Microsoft, give those of us willing to make the switch from a competitor a good way to do it. I spent a lot of time convincing people how great Exchange 2007 would be and plan to implement the full UM/OCS experience, hopes are high and I need to deliver something better than a crib sheet for users to perform a DIY migration.