on-prem Exchange 2016 migration to Exchange Online

Daniel 61

Hello,

I have setup a hybrid connection between our Exchange 2016 and Exchange Online.

I have run in small issue when I try to move a mailbox from my on-prem Exchange to Exchange Online.

When I want to create a migration batch for a test user I'm not able to see the list of users. The entire list is empty.

Has anyone came across this issue?

User's image

Bruce Jing-MSFT 610 Reputation points Microsoft Vendor

2024-04-19T07:11:32.6166667+00:00

First, you could check if your permissions are Global Admins, and did other Global Admins in your organization have the same issue?

Can you see these users in the EAC/M365 admin center?

You also can check if you have the same issue using PowerShell.

You can use New-MigrationBatch cmdlet to create a migration batch in PowerShell and run the migration batch via the Start-MigrationBatch cmdlet .

You can refer to this URL: New-MigrationBatch (ExchangePowerShell) | Microsoft Learn

Start-MigrationBatch (ExchangePowerShell) | Microsoft Learn
Daniel 61 Reputation points

2024-04-22T12:49:09.45+00:00
Hi,

I have checked with multiple Global admin users an the result is the same. For every global admin the list of users that can be migrated is empty.

I tried to do a migration with New-MoveRequest PS command and the error I get is:

If I run the new-MoveRequest when user doesn't have license assigned:

#################################################################

Write-ErrorMessage : Ex43C0AC|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException|The operation

couldn't be performed because 'user@domain.com' couldn't be found.

At C:\Users\user\AppData\Local\Temp\tmpEXO_gpogryg4.bm0\tmpEXO_gpogryg4.bm0.psm1:1191 char:13

Write-ErrorMessage $ErrorObject

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo : NotSpecified: (:) [New-MoveRequest], ManagementObjectNotFoundException

FullyQualifiedErrorId : [Server=GV1MB1P566198,RequestId=d3be152b-e880-dac3-a194-9638b4fa0d27,TimeStamp=Mon, 22 A

pr 2024 12:44:02 GMT],Write-ErrorMessage

######################################################################

And if I run New-MoveRequest when test user has license assigned:

######################################################################

Write-ErrorMessage : |Microsoft.Exchange.MailboxReplicationService.TargetUserAlreadyHasPrimaryMailboxException|Target

user 'agafgat-3242ersfgsf-12fadfas3-filsa042' already has a primary mailbox.

At C:\Users\user\AppData\Local\Temp\tmpEXO_gpogryg4.bm0\tmpEXO_gpogryg4.bm0.psm1:1191 char:13

Write-ErrorMessage $ErrorObject

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo : NotSpecified: (:) [New-MoveRequest], TargetUserAlrea...ailboxException

FullyQualifiedErrorId : [Server=GV1MB1P566198,RequestId=b2e00999-e290-8d96-aa8f-151a0e2bcbea,TimeStamp=Mon, 22 A

pr 2024 12:29:14 GMT],Write-ErrorMessage

######################################################################
Bruce Jing-MSFT 610 Reputation points Microsoft Vendor

2024-04-23T10:00:18.64+00:00
According to the screenshot of your error report, we should do the migration before granting the license. It is wrong to allocate licenses first before migrating.

I need to confirm a couple more questions with you:

Can you see these users in the EAC/M365 admin center?

Are there any other issues in a hybrid deployment environment?

We need more information from you to help you solve your problem.
Daniel 61 Reputation points

2024-04-23T13:16:25.93+00:00
Hi Bruce,

no users don't have license assigned to them before migration.

Users are visible in the M365 admin center. Not in EAC.

Hybrid deployment (HCW) completed without errors.

I managed to find what was the issue. Someone (most probably the guy who was configuring AD Connect) has set a a custom rule to set msExchMailboxGuid to NULL for all synced users. After removing this rule everything works as it should.

Thanks for the input and help.

Accepted answer

Bruce Jing-MSFT 610 Reputation points Microsoft Vendor

2024-04-24T09:24:27.1933333+00:00

Hi，

Glad to know that the issue has already been resolved and thanks for sharing the solution so that others experiencing the same thing can easily reference this! The reason I keep asking if you can see the synchronized users on the M365 portal is to determine if the issue is a sync to Azure AD or a sync to Exchange Online issue.

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution in case you'd like to "Accept" the answer : )

Issue Symptom:

In a hybrid deployment environment, when migrating users, the user list is found to be empty.

Resolution:

There is a custom rule in AAD connect which set msExchMailboxGuid to NULL for all synced users. After removing this rule everything works as it should.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

on-prem Exchange 2016 migration to Exchange Online

0 additional answers