MicrosoftDocs
diff --git a/‎reference/6/Microsoft.PowerShell.Core/About/about_Remote_Disconnected_Sessions.md
Lines changed: 1 addition & 1 deletion b/‎reference/6/Microsoft.PowerShell.Core/About/about_Remote_Disconnected_Sessions.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/6/Microsoft.PowerShell.Core/About/about_Session_Configurations.md
Lines changed: 3 additions & 1 deletion b/‎reference/6/Microsoft.PowerShell.Core/About/about_Session_Configurations.md
Lines changed: 3 additions & 1 deletion
diff --git a/‎reference/6/Microsoft.PowerShell.Core/About/about_pwsh.md
Lines changed: 10 additions & 1 deletion b/‎reference/6/Microsoft.PowerShell.Core/About/about_pwsh.md
Lines changed: 10 additions & 1 deletion
diff --git a/‎reference/6/Microsoft.PowerShell.Core/Disconnect-PSSession.md
Lines changed: 2 additions & 0 deletions b/‎reference/6/Microsoft.PowerShell.Core/Disconnect-PSSession.md
Lines changed: 2 additions & 0 deletions
diff --git a/‎reference/6/Microsoft.PowerShell.Core/Enter-PSSession.md
Lines changed: 32 additions & 3 deletions b/‎reference/6/Microsoft.PowerShell.Core/Enter-PSSession.md
Lines changed: 32 additions & 3 deletions
diff --git a/‎reference/6/Microsoft.PowerShell.Core/Invoke-Command.md
Lines changed: 36 additions & 7 deletions b/‎reference/6/Microsoft.PowerShell.Core/Invoke-Command.md
Lines changed: 36 additions & 7 deletions
diff --git a/‎reference/6/Microsoft.PowerShell.Core/New-PSSession.md
Lines changed: 6 additions & 3 deletions b/‎reference/6/Microsoft.PowerShell.Core/New-PSSession.md
Lines changed: 6 additions & 3 deletions
diff --git a/‎reference/6/Microsoft.PowerShell.Core/Save-Help.md
Lines changed: 1 addition & 1 deletion b/‎reference/6/Microsoft.PowerShell.Core/Save-Help.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/6/Microsoft.PowerShell.Core/Update-Help.md
Lines changed: 1 addition & 1 deletion b/‎reference/6/Microsoft.PowerShell.Core/Update-Help.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎reference/6/Microsoft.PowerShell.Core/Where-Object.md
Lines changed: 24 additions & 0 deletions b/‎reference/6/Microsoft.PowerShell.Core/Where-Object.md
Lines changed: 24 additions & 0 deletions
@@ -21,7 +21,7 @@ continue to run while the session is disconnected.
 
 The Disconnected Sessions feature is available only when the computer at the
 remote end of a connection is running Windows PowerShell 3.0 or a later
-version of Windows PowerShell.
+version of Windows PowerShell and using the WSMan transport.
 
 The Disconnected Sessions feature allows you to close the session in which a
 PSSession was created, and even close Windows PowerShell, and shut down the
 
@@ -195,7 +195,9 @@ supported versions of Windows, you must change the security descriptors of the
 session configurations to allow remote access.
 
 To enable remote access to the session configurations on the computer, use the
-Enable-PSRemoting cmdlet.
+Enable-PSRemoting cmdlet. This cmdlet creates two session configurations:
+- with the name defined as: "PowerShell." + "current PowerShell version"
+- with name "PowerShell.6", untied to any specific PowerShell version.
 
 Also, by default, only members of the Administrators group on the computer
 have Execute permission to the default session configurations, but you can
 
@@ -31,6 +31,7 @@ pwsh[.exe]
 [-NoProfile]
 [-OutputFormat {Text | XML}]
 [-WindowStyle <style>]
+[-WorkingDirectory <DirectoryPath>]
 [-File <FilePath> [<Args>]]
 [-Command { - | <script-block> [-args <arg-array>]
 | <string> [<CommandParameters>] } ]
@@ -107,6 +108,13 @@ Determines how output from PowerShell is formatted. Valid values are "Text"
 Sets the window style for the session. Valid values are Normal, Minimized,
 Maximized and Hidden.
 
+#### -WorkingDirectory <DirectoryPath>
+
+Sets the initial working directory when starting PowerShell.  Any valid
+PowerShell file path is supported.
+
+To start PowerShell in your home directory, use: pwsh -WorkingDirectory ~
+
 #### -Command
 
 Executes the specified commands (and any parameters) as though they were typed
@@ -146,8 +154,9 @@ pwsh -Version
 # Example using a script block
 pwsh -Command {Get-Command -Name Get-Item}
 
-# Example using a string
+# Examples using a string
 pwsh -Command "Get-Command -Name Get-Item"
+pwsh -Command "& {Get-Command -Name Get-Command}"
 
 # Example using a command as the last parameter
 pwsh -Command Get-Command -Name Get-Item
 
@@ -45,6 +45,8 @@ The **Disconnect-PSSession** cmdlet disconnects a Windows PowerShell session (**
 As a result, the **PSSession** is in a disconnected state.
 You can connect to the disconnected **PSSession** from the current session or from another session on the local computer or a different computer.
 
+Note that this capability only works with PSSessions using the WSMan transport.
+
 The **Disconnect-PSSession** cmdlet disconnects only open **PSSessions** that are connected to the current session.
 **Disconnect-PSSession** cannot disconnect broken or closed **PSSession** objects, or interactive **PSSession** objects started by using the Enter-PSSession cmdlet, and it cannot disconnect **PSSession** objects that are connected to other sessions.
 
 
@@ -68,7 +68,8 @@ Enter-PSSession -ContainerId <String> [-ConfigurationName <String>] [-RunAsAdmin
 
 ### HostName
 ```
-Enter-PSSession [-HostName] <string> [-Port <int>] [-UserName <string>] [-KeyFilePath <string>] [-SSHTransport] [<CommonParameters>]
+Enter-PSSession [-HostName] <string> [-Port <int>] [-UserName <string>] [-KeyFilePath <string>] [-SSHTransport]
+ [-Subsystem <String>] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -154,14 +155,14 @@ You can also use the **Exit** keyword to end the interactive session.
 
 ### Example 6: Start an interactive session using SSH
 ```
-PS C:\> Enter-PSSession -HostName LinuxServer01 -UserName UserA
+PS C:\> Enter-PSSession -HostName UserA@LinuxServer01
 ```
 
 This example shows how to start an interactive session using Secure Shell (SSH). If SSH is configured on the remote computer to prompt for passwords then you will get a password prompt.  Otherwise you will have to use SSH key based user authentication.
 
 ### Example 7: Start an interactive session using SSH and specify the Port and user authentication key
 ```
-PS C:\> Enter-PSSession -HostName LinuxServer02 -UserName UserA -Port 22 -KeyFilePath c:\<path>\userAKey_rsa
+PS C:\> Enter-PSSession -HostName UserA@LinuxServer02:22 -KeyFilePath c:\<path>\userAKey_rsa
 ```
 
 This example shows how to start an interactive session using SSH. It uses the *Port* parameter to specify the port to use and the *KeyFilePath* parameter to specify an RSA key used to authenticate the user on the remote computer.
@@ -304,6 +305,9 @@ Specifies the session configuration that is used for the interactive session.
 Enter a configuration name or the fully qualified resource URI for a session configuration.
 If you specify only the configuration name, the following schema URI is prepended: http://schemas.microsoft.com/powershell.
 
+When used with SSH, this specifies the subsystem to use on the target as defined in sshd_config.
+The default value for SSH is the `powershell` subsystem.
+
 The session configuration for a session is located on the remote computer.
 If the specified session configuration does not exist on the remote computer, the command fails.
 
@@ -419,6 +423,10 @@ Accept wildcard characters: False
 ### -HostName
 Specifies a computer name for a Secure Shell (SSH) based connection.
 This is similar to the *ComputerName* parameter except that the connection to the remote computer is made using SSH rather than Windows WinRM.
+This parameter supports specifying the user name and/or port as part of the host name parameter value using
+the form `user@hostname:port`.
+The user name and/or port specified as part of the host name takes precedence over the `-UserName` and `-Port` parameters, if specified.
+This allows passing multiple computer names to this parameter where some have specific user names and/or ports, while others use the user name and/or port from the `-UserName` and `-Port` parameters.
 
 This parameter was introduced in PowerShell 6.0.
 
@@ -621,6 +629,27 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -Subsystem
+Specifies the SSH subsystem used for the new **PSSession**.
+
+This specifies the subsystem to use on the target as defined in sshd_config.
+The subsystem starts a specific version of PowerShell with predefined parameters.
+If the specified subsystem does not exist on the remote computer, the command fails.
+
+If this parameter is not used, the default is the 'powershell' subsystem.
+
+```yaml
+Type: String
+Parameter Sets: HostName
+Aliases:
+
+Required: False
+Position: Named
+Default value: powershell
+Accept pipeline input: True (ByPropertyName)
+Accept wildcard characters: False
+```
+
 ### -UserName
 Specifies the user name for the account used to create a session on the remote computer. User authentication method will depend on how Secure Shell (SSH) is configured on the remote computer.
 
 
@@ -116,9 +116,9 @@ Invoke-Command [-ConfigurationName <String>] [-ThrottleLimit <Int32>] [-AsJob] [
 
 ### HostName
 ```
-Invoke-Command -ScriptBlock <scriptblock> -HostName <string[]> [-Port <int>] [-AsJob]
-[-HideComputerName] [-UserName <string>] [-KeyFilePath <string>] [-SSHTransport] [-RemoteDebug]
-[-InputObject <psobject>] [-ArgumentList <Object[]>] [<CommonParameters>]
+Invoke-Command [-Subsystem <String>] -ScriptBlock <scriptblock> -HostName <string[]> [-Port <int>]
+ [-AsJob] [-HideComputerName] [-UserName <string>] [-KeyFilePath <string>] [-SSHTransport] [-RemoteDebug]
+ [-InputObject <psobject>] [-ArgumentList <Object[]>] [<CommonParameters>]
 ```
 
 ### FilePathHostName
@@ -491,21 +491,21 @@ To get the results of commands and scripts that run in disconnected sessions, us
 
 ### Example 17: Run a command on a remote computer using SSH
 ```
-PS C:\> Invoke-Command -HostName LinuxServer01 -UserName UserA -ScriptBlock { Get-MailBox * }
+PS C:\> Invoke-Command -HostName UserA@LinuxServer01 -ScriptBlock { Get-MailBox * }
 ```
 
 This example shows how to run a command on a remote computer using Secure Shell (SSH). If SSH is configured on the remote computer to prompt for passwords then you will get a password prompt. Otherwise you will have to use SSH key based user authentication.
 
 ### Example 18: Run a command on a remote computer using SSH and specify a user authentication key
 ```
-PS C:\> Invoke-Command -HostName LinuxServer01 -UserName UserA -ScriptBlock { Get-MailBox * } -KeyFilePath c:\<path>\userAKey_rsa
+PS C:\> Invoke-Command -HostName UserA@LinuxServer01 -ScriptBlock { Get-MailBox * } -KeyFilePath c:\<path>\userAKey_rsa
 ```
 
 This example shows how to run a command on a remote computer using SSH and specifying a key file for user authentication. You will not get a password prompt unless the key authentication fails and the remote computer is configured to allow basic password authentication.
 
 ### Example 19: Run a script file on multiple remote computers using SSH as a job
 ```
-PS C:\> $sshConnections = @{ HostName="WinServer1"; UserName="domain\userA"; KeyFilePath="c:\users\UserA\id_rsa" }, @{ HostName="LinuxServer5"; UserName="UserB"; KeyFilePath="c:\UserB\<path>\id_rsa }
+PS C:\> $sshConnections = @{ HostName="WinServer1"; UserName="domain\userA"; KeyFilePath="c:\users\UserA\id_rsa" }, @{ HostName="UserB@LinuxServer5"; KeyFilePath="c:\UserB\<path>\id_rsa }
 PS C:\> $results = Invoke-Command -FilePath c:\Scripts\CollectEvents.ps1 -SSHConnection $sshConnections
 ```
 
@@ -703,6 +703,9 @@ Specifies the session configuration that is used for the new **PSSession**.
 Enter a configuration name or the fully qualified resource URI for a session configuration.
 If you specify only the configuration name, the following schema URI is prepended: http://schemas.microsoft.com/PowerShell.
 
+When used with SSH, this specifies the subsystem to use on the target as defined in sshd_config.
+The default value for SSH is the `powershell` subsystem.
+
 The session configuration for a session is located on the remote computer.
 If the specified session configuration does not exist on the remote computer, the command fails.
 
@@ -1168,6 +1171,10 @@ Accept wildcard characters: False
 
 ### -HostName
 Specifies an array of computer names for a Secure Shell (SSH) based connection. This is similar to the ComputerName parameter except that the connection to the remote computer is made using SSH rather than Windows WinRM.
+This parameter supports specifying the user name and/or port as part of the host name parameter value using
+the form `user@hostname:port`.
+The user name and/or port specified as part of the host name takes precedence over the `-UserName` and `-Port` parameters, if specified.
+This allows passing multiple computer names to this parameter where some have specific user names and/or ports, while others use the user name and/or port from the `-UserName` and `-Port` parameters.
 
 This parameter was introduced in PowerShell 6.0.
 
@@ -1221,6 +1228,27 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -Subsystem
+Specifies the SSH subsystem used for the new **PSSession**.
+
+This specifies the subsystem to use on the target as defined in sshd_config.
+The subsystem starts a specific version of PowerShell with predefined parameters.
+If the specified subsystem does not exist on the remote computer, the command fails.
+
+If this parameter is not used, the default is the 'powershell' subsystem.
+
+```yaml
+Type: String
+Parameter Sets: HostName
+Aliases:
+
+Required: False
+Position: Named
+Default value: powershell
+Accept pipeline input: True (ByPropertyName)
+Accept wildcard characters: False
+```
+
 ### -UserName
 Specifies the user name for the account used to run a command on the remote computer. User authentication method will depend on how Secure Shell (SSH) is configured on the remote computer.
 
@@ -1245,9 +1273,10 @@ Accept wildcard characters: False
 ```
 
 ### -SSHConnection
-This parameter takes an array of hashtables where each hashtable contains one or more connection parameters needed to establish a Secure Shell (SSH) connection (HostName, Port, UserName, KeyFilePath).
+This parameter takes an array of hashtables where each hashtable contains one or more connection parameters needed to establish a Secure Shell (SSH) connection (HostName, Port, UserName, KeyFilePath, Subsystem).
 
 The hashtable connection parameters are the same as defined for the HostName parameter set.
+Note that the order of the keys in the hashtable result in user name and port being used for the connection where the last one specified is used.  For example, if you use `@{UserName="first";HostName="second@host"}`, then the user name `second` will be used.  However, if you use `@{HostName="second@host:22";Port=23}`, then port 23 will be used.
 
 The SSHConnection parameter is useful for creating multiple sessions where each session requires different connection information.
 
 
@@ -215,21 +215,21 @@ The value of the SessionOption parameter is the **SessionOption** object in the
 
 ### Example 12: Create a session using SSH
 ```
-PS C:\> New-PSSession -HostName LinuxServer01 -UserName UserA
+PS C:\> New-PSSession -HostName UserA@LinuxServer01
 ```
 
 This example shows how to create a new **PSSession** using Secure Shell (SSH). If SSH is configured on the remote computer to prompt for passwords then you will get a password prompt. Otherwise you will have to use SSH key based user authentication.
 
 ### Example 13: Create a session using SSH and specify the port and user authentication key
 ```
-PS C:\> New-PSSession -HostName LinuxServer01 -UserName UserA -Port 22 -KeyFilePath c:\<path>\userAKey_rsa
+PS C:\> New-PSSession -HostName UserA@LinuxServer01:22 -KeyFilePath c:\<path>\userAKey_rsa
 ```
 
 This example shows how to create a **PSSession** using Secure Shell (SSH). It uses the *Port* parameter to specify the port to use and the *KeyFilePath* parameter to specify an RSA key used to identify and authenticate the user on the remote computer.
 
 ### Example 14: Create multiple sessions using SSH
 ```
-PS C:\> $sshConnections = @{ HostName="WinServer1"; UserName="domain\userA"; KeyFilePath="c:\users\UserA\id_rsa" }, @{ HostName="LinuxServer5"; UserName="UserB"; KeyFilePath="c:\UserB\<path>\id_rsa }
+PS C:\> $sshConnections = @{ HostName="WinServer1"; UserName="domain\userA"; KeyFilePath="c:\users\UserA\id_rsa" }, @{ HostName="UserB@LinuxServer5"; KeyFilePath="c:\UserB\<path>\id_rsa }
 PS C:\> New-PSSession -SSHConnection $sshConnections
 ```
 
@@ -372,6 +372,9 @@ Specifies the session configuration that is used for the new **PSSession**.
 Enter a configuration name or the fully qualified resource URI for a session configuration.
 If you specify only the configuration name, the following schema URI is prepended: http://schemas.microsoft.com/PowerShell.
 
+When used with SSH, this specifies the subsystem to use on the target as defined in sshd_config.
+The default value for SSH is the `powershell` subsystem.
+
 The session configuration for a session is located on the remote computer.
 If the specified session configuration does not exist on the remote computer, the command fails.
 
 
@@ -189,7 +189,7 @@ Do not specify a file name or file name extension.
 ```yaml
 Type: String[]
 Parameter Sets: Path
-Aliases:
+Aliases: Path
 
 Required: True
 Position: 0
 
@@ -365,7 +365,7 @@ For more information, see about_Group_Policy_Settings (http://go.microsoft.com/f
 ```yaml
 Type: String[]
 Parameter Sets: Path
-Aliases:
+Aliases: Path
 
 Required: False
 Position: 1
 
@@ -21,6 +21,11 @@ Selects objects from a collection based on their property values.
 Where-Object [-InputObject <PSObject>] [-Property] <String> [[-Value] <Object>] [-EQ] [<CommonParameters>]
 ```
 
+### NotSet
+```
+Where-Object [-Property] <string> -Not [-InputObject <psobject>] [<CommonParameters>]
+```
+
 ### ScriptBlockSet
 
 ```
@@ -924,6 +929,25 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -Not
+Indicates that this cmdlet gets objects if the property does not exist or has a value of null or false.
+
+For example: `Get-Service | where -Not "DependentServices"`
+
+This parameter was introduced in Windows PowerShell 6.1.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: Not
+Aliases: 
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -NotContains
 
 Indicates that this cmdlet gets objects if none of the items in the property value is an exact match for the specified value.