O365 throttling

Hi all,

I will be migrating 100's of users over to Exchange Online over the next few months. The ones I've completed so far took a very very long time to migrate and I think it;s because of the throttling that MS apply to O365 tennants.

Via the Microsoft 365 admin center I have lifted the EWS throttling for 90 days but my question is, does NME use EWS? Will the change I made in the admin center make any difference or do I need to log a support ticket with MS to have another kind of throttling lifted?

Thanks

  • Hello Raj,

    If you are using Migrator for Notes to Exchange (MNE), version 4.16.2 or later, then you should be using "Differential Templates", which would be updated with the new Admin Pool settings automatically. If you are using an older version of MNE, or upgraded from an older version and didn't select the option to upgrade to "Differential Templates", then you can use the steps below to change existing MNE Configuration Templates (or create new Configuration Templates):

    1.) Open the MNE Migration Manager.
    2.) Click on the menu button in the upper-right (3 lines)
    3.) Enable "Advanced Wizard Settings".
    4.) Click on Migrate User Data, select the Collection and click Migrate.
    5.) Select the option to Modify the template.
    6.) Click on the Edit button.
    7.) Edit the parameter(s) as required.
    8.) Continue through the wizard until you get to the screen to schedule the migration, which says "Now on this Computer" and click Cancel, which will allow the new configuration to be saved. Alternatively, you can actually start the migration if desired as well.

    The new parameter is now saved in this template. If there are multiple templates for migrating user mail data, then they will need to be updated using the steps above.

    If the new parameter is added to the MNE Global Default Settings, then it will be automatically be included for new templates created in the future.

    Regards,

    Trevor Taegder
    Senior Technical Support Engineer
    Quest | Support

  • Thanks Trevor - I'm using 4.16.0.44.

    There is a bit in the wizard where it show it is using the Admin Pool so all good!

    One other question - can the number of threads be changed during a migration or does it need to be set earlier? The reason I ask is that mine always start at 2 threads and then I manually have to change it to 10 after the copy process kicks off.

    Thanks

  • Hello Raj,

    Using the same steps as above to modify existing Configuration Templates, you can increase the threads by adjusting the parameter below, which should already be present in the settings file:

    [General]
    ThreadCnt=4

    Or, you can certainly increase the thread counts after starting the migration as well.

    Regards,

    Trevor Taegder
    Senior Technical Support Engineer
    Quest | Support

  • Thanks Trevor.

    I have one more issue:

    When I do a migration of around 10 mailboxes, 6 or 7 fail to connect to the target mailbox and I end up having to wait for the successful ones to complete before trying the failed ones again. This happens every time. What is going on here?

    The log file errors are:

    ERROR: [4072-25-4-00000000]Unable to open target mail store 'xxxxxxxxx@xxxxxxx.com'.

    or

    09:26:16 ERROR: [7444-1-156-00000000]ADFWD::AddProxies (1): Processing 'xxxxxxx@xxxxxx.com'
    09:26:16 Single object not found in AD.

    Thanks

  • forgot to add - could this me a Microsoft replication problem? I always apply the full access permissions via a PowerShell script to all the newly created MBs at the same time so I can't understand how some of them are inaccessible?

  • This could be related to Office 365 propagation delay but I see you have an open Service Request. The engineer that picks this up will be able to better understand once they have a chance to review the logs.

    Darin MacKenzie
    Sr. Technical Product Specialist
    Quest | Support

  • Thanks Darin - I think you are correct - I ran a migration this morning for 10 mailboxes - 3 were OK and 7 failed. I then ran the other 7 about 2 hours later and 5 were ok and 2 failed. I then ran the last two again an hour later and they finally migrated. This definitely proves its permissions propagation.