Cross Tenant Mailbox Migration: NotAcceptedDomainException
This week I'm performing a new cross tenant mailbox migration. I have some experience with this kind of migrations, ( it's the third one I'm in charge of ), and with the new procedure, ( will paste the link with the instructions at the end of this article ), an Azure Key Vault is no longer required, so I was very confident and thought that I would no have any issue. But, as sometimes occurs, I was wrong The setup was quite easy, and the mail users configuration was like always, so no a big deal. But now comes the point... Once I launched the migration batch, half of the users started syncing correctly and the ther ones failed, ( neither a MoveRequest was able to start for them ). Once I checked the errors, I got the same for all the failed ones: " NotAcceptedDomainException: You can't use the domain because it's not an accepted domain for your organization ". Ok. No problem... ( I thought ). I work with Exchange since more than 10 years and this is a common error message. ( Again I was wrong ). I started to check the mail users, looking for some misspelled domain, missing alias, spaces, etc... Basically, the troubleshooting for this kind of errors. But from my perspective all looked good. So, I decided to reconfigure all the mailusers with a script, launch a delta sync, and resume the failed moverequest. But again, same error for all of them. Checked again, with PS, from source and target tenant, checked in AD, all the proxy addresses... Nothing, all was correct! Non sense... Ok. At that point I decid to compare some syncing mail users with some failed ones, looking for anything that could be a pattern. And "voilá"! The syncing users were all licensed in O365... The failed ones not! After assigning a license to the failed ones and resume the MoveRequest, all started to work smoothly. For sure, I would have saved many hours of work if the error message had been: " The user is not licensed ". But, yeah... It would have been too simple 🙂 Summarizing, make sure that the mail users have an O365 license before you start the migration batch. And remember, not always the error messages are what they seems to be 🙂 Cross Tenant Mailbox Migration procedure, ( Preview 😞 https://docs.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-mailbox-migration?view=o365-worldwide
Exchange Migration Cross forest
Hello, I planning to do an exchange Migration from forest A to forest B and the email address will be changed. I don't want to set any trust between the two, i will simply create the active directory users from scratch with new passwords and will install and configure the exchange environment in the target forest and will create the mailboxes. i will use a third-party tool to migrate the mailboxes between the two forests and after cutover i will add the alias of the old email as additional proxy address to the mailboxes. i am assuming everything will work fine however i have seen lot of articles on the internet about we have to migrate the legacyexchangeDN from the source environment and to add it as X500 proxy address as well in the destination or we might face issues in the migrated recurrent meetings when someone wants to edit or when someone reply to a migrated email.... I can afford having some meeting corrupted after migration but i cant afford the headache of NDR when someone reply to the migrated emails it will be a disaster.... anyone had this experience before to share it with me especially regarding the reply to the migrated emails and i did not lot of documentation from Microsoft about such scenario? Thank You.
PublicFolder CN=Schema,CN=Microsoft Exchange System Objects,DC=contoso,DC=com
I'm in the preparation stage of migrating our Public Folders from an on-premises Exchange 2016 CU19 server to Exchange Online. Running the SourceSiceValidation.ps1 script outputs several orphaned MEPFs in our Active Directory, and I get a similar output from the ValidateMailEnabledPublicFolders.ps1. The recommendation is to delete the orphaned MEPFs, but I'm running into an oddity that I just don't feel comfortable deleting. There's a PublicFolder named "Schema" in our MESO OU, and it just feels wrong to delete anything named "Schema" in a database. Get-ADObject "CN=Schema,CN=Microsoft Exchange System Objects,DC=***,DC=***" | fl DistinguishedName : CN=Schema,CN=Microsoft Exchange System Objects,DC=***,DC=*** Name : Schema ObjectClass : publicFolder ObjectGUID : 9*******-8***-4***-8***-2*********** Any advice on how to determine if this object really is safe to remove? Thanks!
Both The Owner & I Have Requested Assistance Regarding A Domain Transfer But Have Had No Updates.
Both the owner & I have requested assistance in regards to a domain transfer. There is a phantom account holding our already verified domain.... We have lost a full month of service for over 150 users due to the errors on Microsoft's side. Please answer one of our cases so that we can finish up the migration. We were not anticipating such a difficult experience. One of the cases is registered to the associated email. Thanks. Microsoft 365 Migrations Microsoft Entra
Public Folder Migration Failed
We have a problem migrating public folders from an Exchange 2019 OnPremise to an Exchange Online. We followed the Microsoft guide: https://learn.microsoft.com/en-us/exchange/collaboration/public-folders/migrate-to-exchange-online?view=exchserver-2019 We get to step 7. When completing the PublicFolderMigration job, the status changes to “Completing” and then to “Failed”. The error message in the EXO Shell is: Status: Failed Message: Error calling “net.tcp://be1p281mb2001.deup281.prod.outlook.com:9821/Microsoft.Exchange.MailboxReplicationService BE1P281MB2001.DEUP281.PROD.OUTLOOK.COM (15.20.8207.17 ServerCaps:FFFFFFFF, ProxyCaps:1FFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF)”. Error details: The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state. --> The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state. Does anyone have an idea what this error means? We have already removed and restarted the entire migration, but the same error occurs again.
I cannot receive external emails after migrating from Exchange Server 2013 to 2019.
Hello everyone, I just followed the step-by-step guide from the following link: https://www.collaborationpro.com/migrating-from-exchange-2013-to-exchange-2019-a-step-by-step-guide/ to migrate my Exchange 2013 server to the 2019 version. I completed all the steps mentioned, including creating the connectors, databases, etc. Currently, I have both servers coexisting. I used a test mailbox, which I migrated to one of the databases on the new 2019 server. The problem I'm encountering is that when sending an email from this mailbox to outside the organization, the emails are received. However, when I reply to that email from outside, the replies are not received in the Exchange 2019 mailbox. I used the Microsoft Remote Connectivity Analyzer tool, and it didn't show any errors. When I check the queue on the 2013 server, I can see that all the emails sent from outside are in it. The following error is indicated: Identity: UHPEX2013\Unreachable\309869005505088 Subject: RE: Test Internet Message ID: <email address removed for privacy reasons> From Address: email address removed for privacy reasons Status: Ready Size (KB): 413 Message Source Name: SMTP:Default UHPEX2013 Source IP: 200.123.132.100 SCL: 0 Date Received: 23/05/2024 02:26:42 PM Expiration Time: 25/05/2024 02:26:42 PM Last Error: There is currently no route to the mailbox database. Queue ID: UHPEX2013\Unreachable Recipients: email address removed for privacy reasons;2;3;There is currently no route to the mailbox database.;2;ExternosUHP2EX2019;0. Could you please help me resolve the issue without causing impact or disruption to my productive 2013 server?
Exchange On-Premises cross forest migration
Hi Folks, A customer has on-premises Exchange 2013 with SMTP domain (abc.com) and AD 2012 domain "alpha.com". It also has Hybrid Exchange setup. Due to business requirements, customer will have AD 2019 as "beta.com" and will keep SMTP domain (abc.com) with Exchange 2019 on-premises. For user mailbox and computer migration to new AD Domain, Quest tool will be used after establishing trust between both AD Forests. My concern is, how we will do email routing while keeping the same SMTP domain which is (abc.com) during co-existence? Any suitable link or guidance is appreciated. Thanks.
How to migrate mailbox with over 500 GB - Migration from GWS to M365
Hello, I am trying to migrate GWS mailboxes with over 500 GB to M365 utilizing third-party tool. I have around 50 mailboxes over 200 GB and 10 mailboxes over 500 GB. With third-party tool, I can migrate Gmail to archive mailbox of M365. and I am aware of the fact that it needs auto-expanding feature of archive mailbox. So I have enabled auto-expanding feature for those archive mailbox. However, the thing is the daily growth rate and It cannot exceed 1GB/day as I noticed through below link. https://learn.microsoft.com/en-us/purview/enable-autoexpanding-archiving#more-information The link says like this. Auto-expanding archiving is supported only for mailboxes used by individual users or for shared mailboxes with a growth rate that doesn't exceed 1 GB per day. Is there any way to speed up the growth rate? And provisioning speed also matters. https://learn.microsoft.com/en-us/purview/enable-autoexpanding-archiving#before-you-enable-auto-expanding-archiving the link goes like under. After you turn on auto-expanding archiving, an archive mailbox is converted to an auto-expanding archive when the archive mailbox (including the Recoverable Items folder) reaches 90 GB. It can take up to 30 days for the additional storage space to be provisioned. Is there any way to shorten the days for the additional storage space to be provisioned? How can I overcome this circumstances? or is there an other method to do this? Thank you in advance.Possibility to change move request more than 100
Dear All, We are in the middle of moving mailbox from exchange server 2016 to exchange 2019. we are using powershell to run moverequest for individual mailbox, however there a limitation of 100 concurrent mover request which slows the entire process. Our goal is to move all mailbox to exchange 2019 ASAP and decommission exchange 2016. Would like to seek some advices and suggestion how to make the transition process faster and less time consuming Thank you all in advanced.Logs of SkippedItem Failure during Migration From GWS Gmail to M365 Exchange Online
Hello, I have recently completed migration from GWS Gmail to M365 Exchange Online utilizing Migration Batch microsoft provided. Some of items, However, were skipped during the migration. With Powershell Command as below, I found 6 failure errors in common. $ustats=Get-MigrationUserStatistics "UPN" -IncludeSkippedItems -IncludeReport -DiagnosticInfo "Verbose" $ustats.Report.BadItems | FT folder,subject,failure Could anyone of you let me know of the reasons behind below SkippedItem Failure Logs? There is no such docs to give me answers for that. 1.ConversionFailedException: The message content has become corrupted. --> Decoding of header Subject failed; raw value: --> Character set name (5601) is invalid or not installed. 2. GoogleEventRecurrenceException: Error occurred while converting iCal recurrence to XSO recurrence. RRULE: 'Start.Date="" . Error : 'Invalid ICAL element: RRULE.InvalidRecurrenceUntil' 3. GoogleEventIgnoredTombstoneInstanceOrphanException: Ignored a tombstone of an instance of a series in which the user does not have access to the entire series. 4. MessageSubmissionExceededException: Cannot save changes made to an item to store. --> MapiExceptionMaxSubmissionExceeded: Unable to save changes. 5. UnsupportedGmailFilterComponentException: Unsupported Gmail filter criteria or action. 6. UnsupportedGmailFilterExpressionException: Unsupported Gmail filter expression. Thank you in advance!
