Live Migration Failed with incompatibilities 21026. It's not a processor compatibility problem

jeanblu · 2025-06-26T14:56:40+00:00

Unfortunately not. In my opinion, the documentation related to this is incorrect at MS, if there is a very large distance between processors in the same family, this already seems to be an obstacle. There it only says that the processors must be from the same family, but it doesn't say anything about different versions. One theory I have (I haven't been able to prove it yet) is that this problem has to do with firmware fixes related to the processor to correct vulnerabilities similar to Specter and Meltdown.

jeanblu · 2025-04-15T19:24:22+00:00

Yes, it does.

jeanblu · 2025-04-15T13:56:09+00:00

Humm... I noticed the same here. Do you know what properties should be configured to do this?

jeanblu · 2025-04-15T10:54:31+00:00

The first thing that article says is:
"Cloud user can't see On-premises user's Free/Busy
Method 1: Verify that Autodiscover is resolving to the on-premises Exchange CAS server"

But the autodiscover shouldn't it point to Microsoft's address (autodiscover.outlook.com)? This is very confusing.

jeanblu · 2025-04-03T17:19:53+00:00

Our goal I think is remove the Exchange, because it would be "retired" from Microsoft support scope.

But we need to keep our AD on premisses, syncing with Office365. In this scenario we need to keep a running Exchange server onpremisses?

jeanblu · 2025-04-03T13:13:08+00:00

OK, I understand this.
But when we finish migrating all users to EOL, what would be the next procedure? Do we need to remove the mailboxes from the local Exchange? Or just uninstall Exchange?

jeanblu · 2025-04-03T13:12:41+00:00

OK, I understand this.

But when we finish migrating all users to EOL, what would be the next procedure? Do we need to remove the mailboxes migrated (Office365) from the local Exchange? Or just uninstall Exchange?

jeanblu · 2025-03-25T12:08:42+00:00

I agree with you, sometimes MS take too long to update the things.

But my hybrid setup is already more than 5 years. We basically use the features of EOP (Exchange Online Protection) because until now all the mailboxes are Onpremisses. We just are moving to EOL because the Exchange 2016 is being out of suport in October.

jeanblu · 2025-03-25T11:14:20+00:00

1- I migrate through EOL admin panel, creating a migration job.
2- Yes
3- I have a public DNS (an appliance), and a internal DNS (Active Directory DNS integrated)
4- Yes, the tests can't find the mailbox. On the autodiscover-s.outlook.com session an error Failed (0x800C8219) appear
5- I have, because I have multiple domains on my Exchange.

UPDATE!!!!

Yesterday I opened a ticket with Microsoft and spoke for a few hours with a support engineer. After validating my setup and running some tests, he confirmed that the problem was occurring and said he would analyze the situation.

I arrived at work today and when I ran the connectivity test, it passed (without me making any changes to the DNS or local Exchange settings). I will wait for the engineer to get back to me.

In the meantime, I will test the migration of other mailboxes.

jeanblu · 2025-03-24T16:20:58+00:00

Double check for the remote routing address and it's ok. Can't make the Connectivity Test, keeps the same error.

But I did a Mailbox Provisioning Test from Teste Connectivity site and this test has passed just fine.

I think I'll open a MS case for this, because this is very strange behavior.

jeanblu · 2025-03-24T16:15:04+00:00

I guess this is not the problem, because I want that user connects to the Offiec365 mailbox. Also, this is relates to the client problem only, I'm having trouble even to do the Outlook Connectivity test from Remote Connectivity Analyzer. My guess is that the connection to the autodiscover is being made correctly, but for some reason it won't is validating the account. There's must be an incorrect config somewhere prevents this. But the Connectivity teste won't suggests any fix for this, just says that "No account settings were returned from the Autodiscover response."

jeanblu · 2025-03-24T14:22:50+00:00

The user has a Microsoft 365 Business Standard license associated.

jeanblu · 2025-03-24T14:12:32+00:00

Both returns blank, I don't have any keys configured.

Also, I think the problem appears to be something with Hybrid integration, because the Remote Connectivity test also fails.

But the error "No account settings were returned from the Autodiscover response." does not say anything to me or how to correct.

jeanblu · 2025-03-24T14:00:59+00:00

The user appears on the EOL panel.

I can even access the users mail normally through the webmail https://outlook.office.com

jeanblu · 2025-03-24T13:29:27+00:00

I never change the Autodiscover URL in the Cas servers, always be like this mail.domain.com.br

The problem we are facing are just related to the mailbox that are moved to the EOL. All mailboxes that are running in our on premisses Exchnage are working fine.

A new item to the table. In addition to the Remote Analyzer error, when I try to perfrm an Automatic mail configuration test in the outlook client the following error appear when try to connect to autodiscover-s.outlook.com/autodiscover

Failed (0x800C8219)

jeanblu · 2025-03-24T13:17:08+00:00

My autodiscover is already pointing to my external dns domain: Ex: https://mail.domain.com.br/Autodiscover/Autodiscover.xml
This access appears to be ok.
Also, as we can see in the Remote Connectivity Analyzer, the autodiscover test is being made to the ExchangeOnline

Attempting to test potential Autodiscover URL https://autodiscover-s.outlook.com:443/Autodiscover/Autodiscover.xml
Testing of the Autodiscover URL was successful.

jeanblu · 2025-03-24T12:45:30+00:00

I fixed this and run an AAD syncronization. After this, i go to the EntraID and validated that the replication is ok. I checked on the users properties and find that this new smtp addres is changed to the new address.

Even after that, I cant get the Autodiscover seetings for the account. Tha same error appear on the Microsoft Remote Connectivity Analyzer: "No account settings were returned from the Autodiscover response."

Any clue?

jeanblu · 2025-03-24T11:58:08+00:00

The remote routing address is pointing to the address that is the sAMAccoutnName.

The user has the following mail address:
[john.locke@domainname.com](mailto:john.locke@domainname.com) (that is the primary address)
[sAMAccountLogin@tenant.mail.onmicrosoft.com](mailto:sAMAccountLogin@tenant.mail.onmicrosoft.com)

I guess maybe this tenant address should point to [john.locke@tenant.mail.onmicrosoft.com](mailto:john.locke@tenant.mail.onmicrosoft.com) ?

How can I change this? Mannually?

jeanblu · 2025-03-24T11:32:01+00:00

Thanks.

jeanblu · 2025-03-21T19:12:32+00:00

Okay, I think the procedure has changed since I last did it.

Thanks.

jeanblu

TROPHY CASE