Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions reference/6/Microsoft.PowerShell.Core/New-PSSession.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,14 @@ The benefit of an SSH based PowerShell remote session is that it can work across
For SSH based sessions you use the **HostName** or **SSHConnection** parameter set to specify the remote computer and relevant connection information.
For more information about how to set up PowerShell SSH remoting, see [PowerShell Remoting Over SSH](/powershell/scripting/core-powershell/ssh-remoting-in-powershell-core).

> [!NOTE]
> When using WSMan remoting from a Linux or macOS client with a HTTPS endpoint where

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure how applicable this information is, but just FYI:
I had to use these flags from Windows client as well (during Redfish work).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ignore this, in my case it was not New-pssession.

> the server certificate is not trusted (e.g., a self-signed certificate). You must
> provide a `PSSessionOption` that includes `-SkipCACheck` and `-SkipCNCheck` to
> successfully establish the connection. Only do this if you are in an environment
> where you can be certain of the server certificate and the network connection to
> the target system.

## EXAMPLES

### Example 1: Create a session on the local computer
Expand Down