FAQ Menu

Find quick answers to your queries.

EDB to Office 365. EDB to Live Exchange Server. EDB to PST Converter FAQ's

EDB to Live Exchange

EDB to Live Exchange

  1. Can I Import mails to Live Exchange Server?

    Yes. Using EdbMails you can import mails to Live Exchange Server.

    top

  2. How to perform EDB to Live Exchange Server Migration?

    top

  3. How to test the Impersonation rights and connectivity using the Microsoft Remote Connectivity Analyzer?

    For a successful EDB to Live Exchange migration, you must test the Impersonation rights and connectivity using the Microsoft Remote Connectivity Analyzer. Click here to open the Microsoft Remote Connectivity Analyzer webpage. Upon opening Microsoft Remote Connectivity Analyzer webpage, under 'Exchange Server' tab, test the connectivity for "Exchange ActiveSync Autodiscover". Connection must be successful to proceed with the next step.

    top

  4. How to set Impersonation Rights for Live Exchange server user account?

    Follow the below links to set Impersonation Rights for Live Exchange user account.

    top

  5. I'm trying to Login Live Exchange user account using EdbMails for EDB to Live Exchange server Migration, it is failing. Why?

    Ensure that you have set "Impersonation rights" for this user account. Click here to know steps to setup Impersonation rights

    top

  6. Why am I getting a '407 proxy authentication required' while connecting to live Exchange server?

    This problem occurs when there is something wrong with your environment network configuration, most likely DNS settings.

    top

  7. How do I map source and target mailboxes / user accounts during EDB to Live Exchange Server migration?

    EdbMails allows you to select appropriate source and target mailboxes during EDB to Live Exchange Server migration. For this, select the mailbox / user account in the list of mailbox / folders there are selected for EDB to Live Exchange Server migration as shown in the below screen.
    upgrade to paid version select

    top

  8. Do I need to set Impersonation Rights to each and every Exchange Server user accounts?

    No. You no need to set Impersonation rights to all the Exchange server mailbox accounts. You need to set Impersonation rights to only the user with administrative credentials and use this user for Live Exchange Server user login via the EdbMails application during EDB to Live Exchange Server migration. Using this Impersonated user, EdbMails will list all the other users and you can map them to any Mailboxes for EDB To Live Exchange migration.

    top

  9. How to resolve Error 'The server cannot service this request right now'?

    This error is most likely to be caused by Exchange Web Services (EWS) throttling, particularly on busy servers.

    To resolve this issue, you should remove EWS throttling. To do this, follow the steps below:

    1. Open the Exchange Management Shell.

    2. Create a new throttling policy (for example: “Unlimited", using the following command:

     

    Command:
    New-ThrottlingPolicy Unlimited

    Run one of the following commands (depending on Exchange version) to change the new throttling policy, setting the EWS connections for “Unlimited” to “Null/Unlimited”:

     

    For Exchange 2010:

    Command:
    Set-ThrottlingPolicy Unlimited -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -CPUStartPercent $null

     

    For Exchange 2013 and above:

    Command:
    Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited

     

    If you continue to see the same error, please contact support-mail

    top