cannot connect to Exchange Management Shell

[MateKovacs]

Hi All,

Since yesterday I cannot connect to Exchange Management Shell(Exchange Server 2016), and ECP is also not reachable in a browser.
This is the error in EMS-PS:
New-PSSession : [<Servername>] Processing data from remote server <Servername> failed with the
following error message: Unable to load the type
"Microsoft.Exchange.Configuration.Authorization.ExchangeAuthorizationPlugin" specified in the
"InitializationParameters" section. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed

I've tried restaring IIS, applying new updates, even restarting the server but nothing worked.
Yesterday it worked, I was even running a Healthcheck.ps1 script.

Thanks!

[#2]

Hi @MateKovacs,

the error you're having indicates that the account used to connect to the Exchange Server lacks Remote PowerShell privileges.

This could be the reason for the inability to access the Exchange Management Shell (EMS) and the Exchange Control Panel (ECP).

You can try this to resolve this issue:

Activate Remote PowerShell for your account:
Request your Exchange Administrator to execute the 'Set-User -RemotePowerShellEnabled' command to enable Remote PowerShell for your account.

Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.

If the post was useful in other ways, please consider giving it Like.

Kindest regards,

Leon Pavesic
(LinkedIn)

[#3]

Hi,

Thanks for your response.
Its not it, it is enabled for all users in our tenant.

[#4 · Accepted solution]

Looks like the issue is regarding 3rd party AV, although we are not able to figure out the exclusions which need to be set. We have the Microsoft recommendations set ( and more and still does not work properly), only if we remove the AV completely.