Today I want to write about some small issue one of my customers just had.This customer has installed an exchange server in a new forest.The installation went quite smoothly and after the setup was done, my customer wanted to start the exchange management shell.

When he started the Shell there where a lot of error messages…

 

Her he was running into a problem:

New-PSSession : [exc001.contoso.com] Processing data from remote server exc001.contoso.com failed with the
following error message: [ClientAccessServer= exc001,BackEndServer= exc001.contoso.com,RequestId=22507b0c-590b-4b79-
9338-9fed93854418,TimeStamp=16.02.2018 09:52:19]
[AuthZRequestId=ad5340a0-1de7-1234-abcd-61b4637f5226][FailureCategory=AuthZ-SetupVersionInformationCorruptException]
Unable to determine the installed file version from the registry key
'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine'. 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

As we can see in the error message, there is a problem with the Powershell version in the registry.
Now we have two ways how to fix this issue:

 

Number 1:

Go to the Technet article from Prabhat Nigam and download his PowerShell Registry Key HERE.

 

Number 2:

Try to find out if the right PowerShell versions are installed. This you can do like this:

Go to the server manager and click on “Add roles and features”:

Choose “Role-based or feature-based installation” and click Next:

Choose the right server:

Go to the server Features:

On the server features scroll down to Windows PowerShell (n of 5 installed), choose the “Windows PowerShell 2.0 Engine” and install it. In my print screen I have done it already.

If that was your issue, your exchange Management shell should be working now fine.

 

 

Photo by Joao Tzanno on Unsplash