Powershell: New-PPSession: This parameter set requires WSman

Created on 22 Nov 2019  路  5Comments  路  Source: PowerShell/PowerShell

Hey,

I have an issue running this command to link to my Office 365 exchange and needed some support in connecting.

PS /Users/ztariq> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $Credentials -Authentication Basic 鈥揂llowRedirection
New-PSSession : This parameter set requires WSMan, and no supported WSMan client library was found. WSMan is either not installed or unavailable for this system.
At line:1 char:12

  • $Session = New-PSSession -ConfigurationName Microsoft.Exchange -Conne ...
  • ~~~~~~~~~~~~~~
  • CategoryInfo : ResourceUnavailable: (:) [New-PSSession], PSRemotingTransportException
  • FullyQualifiedErrorId : System.Management.Autom

Could someone help me?. I am running PSVersion 6.0.4 and am on Mojave 15.1 OSX.

Cheers,

Zeb

Issue-Question Resolution-Duplicate

Most helpful comment

How is downgrading openssl a solution

Typical solution for deprecated libraries: https://github.com/PowerShell/PowerShell/issues/10600#issuecomment-610565488

I'm going to use a docker images which contains all correct libraries instead downgrade something on my system.

docker run  \
  -v $HOME:$HOME \
  -v $HOME/.local/share/powershell/:/root/.local/share/powershell/  \
  -v $HOME/.cache/powershell/:/root/.cache/powershell/  \
  -it mcr.microsoft.com/azure-powershell pwsh

Just install the Exchange Online Module once, it will be persist on disk.

Additionally, you could raise a shell alias to call this:

alias pwsh="docker run -v $HOME:$HOME -v $HOME/.local/share/powershell/:/root/.local/share/powershell/ -v $HOME/.cache/powershell/:/root/.cache/powershell/ -it mcr.microsoft.com/azure-powershell pwsh"

All 5 comments

This issue has been marked as duplicate and has not had any activity for 1 day. It has been closed for housekeeping purposes.

How is downgrading openssl a solution to no supported WSMan client library was found?
If powershell needs "openssl" why don't you call it openssl, why do you invent "WSMan" ?
What is WSMan? Why does Microsoft invent its own terminology for stuff that has been arround universally for half a decade?

I don't see a solution in the linked comments.

How is downgrading openssl a solution

Typical solution for deprecated libraries: https://github.com/PowerShell/PowerShell/issues/10600#issuecomment-610565488

I'm going to use a docker images which contains all correct libraries instead downgrade something on my system.

docker run  \
  -v $HOME:$HOME \
  -v $HOME/.local/share/powershell/:/root/.local/share/powershell/  \
  -v $HOME/.cache/powershell/:/root/.cache/powershell/  \
  -it mcr.microsoft.com/azure-powershell pwsh

Just install the Exchange Online Module once, it will be persist on disk.

Additionally, you could raise a shell alias to call this:

alias pwsh="docker run -v $HOME:$HOME -v $HOME/.local/share/powershell/:/root/.local/share/powershell/ -v $HOME/.cache/powershell/:/root/.cache/powershell/ -it mcr.microsoft.com/azure-powershell pwsh"
Was this page helpful?
0 / 5 - 0 ratings

Related issues

JohnLBevan picture JohnLBevan  路  3Comments

concentrateddon picture concentrateddon  路  3Comments

Michal-Ziemba picture Michal-Ziemba  路  3Comments

garegin16 picture garegin16  路  3Comments

manofspirit picture manofspirit  路  3Comments