Hybrid agent setup failing on "Validating Hybrid Agent for Exchange usage

Question

Hi,

I am setting up a Hybrid Wizard config mail migration from on-prem to exchange online. I am using the Modern Hybrid Topology.

I get a Validating Hybrid Agent for Exchange usage error:

20240312_070138.log

I have also added the log file for further details of this error.

Guidance to resolve this issue will be highly appreciated.

Regards

Answer 1

Hi @Jabulani Motloung ,

Connect to Exchange Online PowerShell and run the command below after replacing "domain\admin" with the on-premises migration admin you are using:

Test-MigrationServerAvailability -ExchangeRemoteMove: $true -RemoteServer 'dd500728-4fec-405f-a706-a3b245576f1f.resource.mailboxmigration.his.msappproxy.net' -Credentials (Get-Credential -UserName domain\admin)

If you get the same error, check the Hybrid Agent Status (ACTIVE or INACTIVE) by re-running Modern HCW and check it in the GUI, reference here.

If the Hybrid Agent is ACTIVE, check and confirm with Performance Monitor that you see the requests. If the request counters (for #of requests) go up on the Agent machine when you do Test-MigrationServerAvailability to the Hybrid Agent, it's likely to be an issue with the on-premises infrastructure, especially proxy and firewall settings. Then please go through the links below and make sure all the requirements have been met:

• install requirements
• system requirements
• port and protocol requirements

Reference: Troubleshooting Hybrid Migration Endpoints in Classic and Modern Hybrid -Scenario 1: Test-MigrationServerAvailability fails because of connectivity / timeout errors.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi @Jabulani Motloung I got the exactly the same issue, would you be able to elaborate on how it was sorted please.

@Yuki Sun-MSFT

I ran the cmd as per your instructed above with mine'76101ba2-ccfb-4c99-972e-8de7fc7910d7.resource.mailboxmigration.his.msappproxy.net'

it failed with the same error in the log.

So you know it was fine before, all of a sudden it stopped working.

Any help/ advice would be appreciated

Cheers

Answer 3

Hello,

I had the same problem and it is related to Exchange Extended Protection.

To solve the problem, you need to get the Powershell script from

https://learn.microsoft.com/en-us/exchange/plan-and-deploy/post-installation-tasks/security-best-practices/exchange-extended-protection?view=exchserver-2019#extended-protection-and-modern-hybrid-configuration

Then execute this command:

.\ExchangeExtendedProtectionManagement.ps1 -ExchangeServerNames MHServer1, MHServer2 -ExcludeVirtualDirectories "EWSFrontEnd"