Resolving PowerShell Remote Session Issues with Exchange 2016/2029

 

Resolving PowerShell Remote Session Issues with Exchange 2016/2029

If you've ever encountered the dreaded New-PSSession error while trying to connect to an Exchange 2016/2019 server, you're not alone. This error can be frustrating, but with a bit of troubleshooting, you can get your remote PowerShell session up and running. In this post, I'll walk you through a common issue and its solution after i made some finetune the settings against data serialization (  falsing the data serialization) . I will walk through the data serializations in another post on which I encounter the issue 

The Problem

When attempting to establish a remote PowerShell session using the New-PSSession cmdlet, you might encounter an error message like this:

New-PSSession : [ServerName] Connecting to remote server Servername failed with the

following error message :  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 : -2144108477,PSSessionOpenFailed

The Solution

After some research and troubleshooting, I found a solution that worked for me. The issue was related to the SSL certificate configuration in IIS Manager. Here's what you need to do:

1. Check SSL Certificate in IIS Manager:

   • Open IIS Manager on your Exchange server.
   • Navigate to "Default Web Site" and "Exchange Back End".
   • Under "Bindings", ensure that a valid SSL certificate is assigned to HTTPS.

Step-by-Step Guide

1. Open IIS Manager:

   • Press Win + R, type inetmgr, and press Enter.

2. Navigate to Sites:

   • In the left pane, expand your server node and then expand "Sites".

3. Check Bindings:

• Select "Default Web Site".
• In the right pane, click "Bindings".
• Ensure that a valid SSL certificate is assigned to HTTPS.

Conclusion

By ensuring the correct SSL certificate is assigned and adjusting the SSL settings in IIS Manager, you can resolve the New-PSSession error and successfully establish a remote PowerShell session with your Exchange 2013 server. This solution saved me a lot of time and frustration, and I hope it helps you too!

https://hope-this-helps.de/serendipity/archives/Exchange-2013-Powershell-Error-FailureCategoryCafe-SendFailure-FullyQualifiedErrorId-2144108477-493.html

For more details, you can refer to the original solution provided the above link that helped me resolve this issue.