Share via

Powershell on Mac/Linux - New-PSSession to Exchange Server -> MI_RESULT_FAILED Error

ITS ByteSec 0 Reputation points
2024-07-03T08:53:54.16+00:00

How can the following error be resolved when trying to connect to an Exchange server via PowerShell from a Mac/Linux machine? (working fine from windows machine though)

"New-PSSession: [<exchangeserver.domain>] Connecting to remote server <exchangeserve.domain> failed with the following error message: MI_RESULT_FAILED. For more information, see the about_Remote_Troubleshooting Help topic."

Additionally, I am unable to locate the troubleshooting document or any information on the MI_RESULT_FAILED error.

Could you provide guidance on this issue?

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,180 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,569 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,481 questions
Windows Server PowerShell
Windows Server PowerShell
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.PowerShell: A family of Microsoft task automation and configuration management frameworks consisting of a command-line shell and associated scripting language.
5,449 questions
PowerShell
PowerShell
A family of Microsoft task automation and configuration management frameworks consisting of a command-line shell and associated scripting language.
2,288 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rich Matheisen 45,671 Reputation points
    2024-07-05T15:37:17.6666667+00:00

    There were multiple reports of problems using WSMAN on non-Microsoft machines years ago, and support for WSMAN on those machines was dropped (refer to the last post in this thread): https://github.com/PowerShell/PowerShell/issues/5130

    There's a replacement for the WSMAN here: https://www.powershellgallery.com/packages/PSWSMan/2.3.1

    0 comments