Comments on: Exchange Server Extended Protection

By: suhas

suhas — Fri, 12 Jul 2024 20:02:19 +0000

We are trying to execute the script “ExchangeExtendedProtectionManagement.Ps1” but getting the below error.

Get-Command: The term ‘ExSetup.exe’ is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At D:\temp\ExchangeExtendedProtectionManagement.Ps1:1966 char:18
+ (Get-Command ExSetup.exe |
+ ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (ExSetup.exe:String) [Get-Command], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.GetCommandCommand

By: Jaap Wesselius

Jaap Wesselius — Wed, 03 Apr 2024 16:06:53 +0000

In reply to Chico. Have a look at figure 5 in the article, that’s what you see when it is disabled.

By: Chico

Chico — Wed, 03 Apr 2024 16:03:50 +0000

In reply to Jaap Wesselius. thank you Jaap, How to tell with your script if it isn’t enabled please?

By: Chico

Chico — Wed, 03 Apr 2024 16:02:52 +0000

In reply to Jaap Wesselius. thank you Jaap, When running ‘ExchangeExtendedProtectionManagement.ps1 -ShowExtendedProtection’, what tells you that it is or isn’t enabled please?

By: Jaap Wesselius

Jaap Wesselius — Wed, 03 Apr 2024 06:18:00 +0000

In reply to Chico. Hi Chico, It is no problem at all to use the /DoNotEnableEP switch instead of the other one.

By: Chico

Chico — Tue, 02 Apr 2024 18:15:54 +0000

When running ‘ExchangeExtendedProtectionManagement.ps1 -ShowExtendedProtection’, what tells you that it is or isn’t enabled please?

Also, I used the following switch ‘/DoNotEnableEP’ rather than ‘ /DoNotEnableEP_FEEWS’ switch and then ran the healthchecker script and it showed that my 2 node 2019 exchange hybrid Extended Protection was not configured. Is it okay to run this switch rather than the front end one please?

By: Ed

Ed — Wed, 20 Mar 2024 08:37:23 +0000

Very good summary, thank you

By: Jaap Wesselius

Jaap Wesselius — Tue, 19 Mar 2024 18:47:07 +0000

In reply to John.

Hi John,
Modern Hybrid works with an agent, that’s why EP is not working there. Without anything between Exchange Online and your Exchange server, even with CU13, it should work. Is it just the mailbox migration that’s not working? Is cross-premises free/busy working? That’s using EWS as well, just like mail tips for example.
How many servers do you have? Is it possible to EP breaks between two Exchange server, because of a different certificate for example?

By: John

John — Mon, 18 Mar 2024 10:17:39 +0000

Hello Jaap,
We have a scenario with one of our clients where the Exchange is setup in a Classic Hybrid scenario.
– Exchange server 2019 with CU13 installed.
Last week, we did a quick change on just enabling Extended Protection. But one test failed which pertains to mailbox migration from on-prem to cloud. But once we Turned Off the Extended Protection in “Windows Authetication” for EWS, the migration worked fine for the test mailbox account.

In your article, you mentioned that Extended Protection works only in Classic Hybrid Scenario and not in Modern Hybrid. Can you please share your thoughts about why we could have faced this error of mailbox migration? or do you think that it is expected and that we should turn off Extended Protection only for EWS in classic hybrid scenario?

Thanks
John.

By: Frank

Frank — Sat, 16 Mar 2024 20:20:35 +0000

Thank you so much Jaap. Your explanation saved my day!