Microsoft Transporter suite for Internet mailboxes: configuring Exchange Impersonate permission in Exchange Server 2007

Hello folks,

If you are going to use the Microsoft Transporter to copy content from a POP3/IMAP4 to Exchange Server 2007, the Exchange Impersonation permission must be done before using the Microsoft Transporter. This permission can be assigned in a specific CAS Server, but if you are going to use a single one you must specifiy it during the wizard. There is an example in the documentation that explains how to apply the permission for all CAS Servers, in this post we will be applying in a single CAS server.

First of all, get the Client Access Server distinguishedname attribute, through the following cmdlet:

get-clientaccessserver | select name,distinguishedname | fl

Now that we have the distinguesdname handy, we can assign the permission using the following cmdlet:

add-adpermission -Identity <CAS distingueshed name> -User <user> -ExtendedRights ms-Exch-EPI-Impersonation

Now, we can move on and use the Microsoft Transporter to copy content from POP3/IMAP4 servers.

Best Regards,
Anderson Patricio


Technorati : ,
Del.icio.us : ,
Ice Rocket : ,
Flickr : ,

4 thoughts on “Microsoft Transporter suite for Internet mailboxes: configuring Exchange Impersonate permission in Exchange Server 2007

  1. Thanks for the post. They don’t really make it completely clear that you HAVE to do this. I think alot of assumptions that the Exchange Admin should just be able to do this create alot of confusion, especially for people used to the EX2K3 Mig Wizard.

  2. Ok, thanks for that. It’s working now for me. However I still have a problem using transporter. I have about 4000 Imap mailboxes to move to my exchange2k7, but don’t know how to give a root login/pwd to my get-imapmailboxdata cmdlets to be able to open each source mailbox without having to know each user’s pwd!

  3. Hi all,
    We have finally decided to reset passwords. BUT I still have a problem: it seems that transporter is not able to migrate bigger mails than 1.5Mb. Anyone has found a workaround for that?
    Thanks!

  4. Sylvain, if you have not yet figured out the error, try this:

    Add this value to your web.config file in IIS for your OWA site (make sure to create a backup file before you change it)

               <httpRuntime maxRequestLength=”10000″ />

    Enter this string right under the <system.web> line. The 100000 denotes the size limit of e-mail messages to import (in KB I think). Reset IIS and try the migration again

Leave a Reply

Your email address will not be published. Required fields are marked *