One of the most common issues with the migrating Office 365, there are a lot of small and medium business who rely on the Office 365 migration. It not an easy thing to perform, but ensuring your data change server on-premises should be perform in rightful manner.
A lot of users have report, they have encountered the “Mailbox size exceeds target quota” during the migration process. Allow us to help your query, and we will be sharing some troubleshoot to fix your error. Without further ado, let’s check it out.
Troubleshooting for “Mailbox size exceeds target quota” Mailbox Size 6.527 GB (6,834,336,719 bytes) exceeds target quota 2 GB (2,147,483,648 bytes).
Check Enabling of mDBUseDefaults attribute
Check this from the on-premises Active directory/ exchange server which are active during the session of Active Directory users and computer.
- Open Administrative tool, and then head over to the Active Directory users and computer.
- Now, change the view option to Details to view.
- Click on View from the navigation panel, and then choose Advance Features.
- It will pop-up a new window, where you can tweak some of the attribute settings.
- After that, choose the users and then right-click on it.
- Choose Properties, and then from the Properties windows choose the Attribute Editor tab.
- There you have mDBUseDefaults attribute, and then ensure the value set to FALSE.
- For this, you have an edit button the pop-up window of mDBUserFDefaults. Simply set the value from TRUE to FALSE.
- Click ok to save your action.
Now Retry migration
Starting with loading and login with the Exchange Admin Center (EAC), begin to migrate of Microsoft Office 365 to different database according to your on-premise exchange server.
- On the Recipient of Exhange Admin Center, click on the “+” icon button, and then choose Move to different database.
- Choose the users for which you want, and click on Next to proceed next.
- Assign the name to your New Migration Name Box, and then choose the following Mailbox, archive, or both based on your requirements.
- After that, it will ask you to select the dataset where you want to migrate your Mailbox and the target archive.
- This was your database for Mailbox archive, use the correct target database to avoid delay and error.
- Once you finish setup this, now you can start retry the Mailbox Import.
Check your Mailbox Quota for the Migration in Office 365
It is importat to check, because if there is any limit on your mailbox then you won’t be able to migrate, for this you can use Get-Mailbox. Where it will display if there is any quota exceed on your Mailbox server. However, you require to use Exchange Online PowerSheel with active connected, Use the following command to check the Office 365 actual Limit.
- Get-Mailbox <email address> | FL
- This will show you all the details of Mailbox, check these following field
- Issuewarningquota
- Prohibitsendquota
- Prohibisendrecivequota
If you have any quota limit applied to your Mailbox, then you can tweak the setting busing the following command example. Not to mentioned you can configure based on your demand.
Set-mailbox <email address> -prohibitsendquota <size in GB example 10GB> -prohibitsendreceivequota <size in GB example 10GB> -issuewarningquota <size in GB example 10GB>
Check your Microsoft Office Subscription
There is a different limit for the Subscription model you have sign-up for, as for Office 365 Business and Stand it’s 50GB. On the other hand, Enterprise License, you have 100GB and Smaller Subscription have 2GB of Quota Limit to be used during active subscriptions.
Migrating to office 365, and working with the exchange on-premis server but it comes with a bit of hassle. In order to have a seamless expereince check everything before doing the migrations.
