| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| Microsoft.PowerShell.Core | About Hidden (5.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Hidden.md | --- -description: Describes the Hidden keyword, which hides class members from default Get-Member results. +description: Describes the `hidden` keyword, which hides class members from default `Get-Member` results. Locale: en-US Previously updated : 01/04/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hidden?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Hidden Title: about Hidden # about_Hidden ## Short description-Describes the Hidden keyword, which hides class members from default -Get-Member results. +Describes the `hidden` keyword, which hides class members from default +`Get-Member` results. ## Long description -When you use the Hidden keyword in a script, you hide the members of a class -by default. The Hidden keyword can hide properties, methods (including -constructors, events, alias properties, and other member types, including -static members, from the default results of the Get-Member cmdlet, and from -IntelliSense and tab completion results. To display members that you have -hidden with the Hidden keyword, add the -Force parameter to a Get-Member -command. +When you use the `hidden` keyword in a script, you hide the members of a class +by default. Hidden members do not display in the default results of the +`Get-Member` cmdlet, IntelliSense, or tab completion results. To display members +that you have hidden with the `hidden` keyword, add the **Force** parameter to a +`Get-Member` command. -Hidden members are not displayed by using tab completion or IntelliSense, -unless the completion occurs in the class that defines the hidden member. +The `hidden` keyword can hide: -A new attribute, System.Management.Automation.HiddenAttribute, has been added, -so that C\# code can have the same semantics within PowerShell. +- methods (including constructors) +- events +- alias properties +- other member types (including static members) -The Hidden keyword is useful for creating properties and methods within a -class that you do not necessarily want other users of the class to see, or -readily be able to edit. +Hidden members are not displayed in tab completion or IntelliSense unless the +completion occurs in the class that defines the hidden member. -The Hidden keyword has no effect on how you can view or make changes to -members of a class. Like all language keywords in PowerShell, Hidden is not +The new attribute, **System.Management.Automation.HiddenAttribute**, enables C# +code to have the same semantics within PowerShell. ++The `hidden` keyword is useful for creating properties and methods within a +class that you do not necessarily want users of the class to see or readily be +able to edit. ++The `hidden` keyword has no effect on how you can view or make changes to +members of a class. Like all language keywords in PowerShell, `hidden` is not case-sensitive, and hidden members are still public. -Hidden, along with custom classes, was introduced in PowerShell 5.0. +The `hidden` keyword, along with custom classes, was introduced in Windows +PowerShell 5.0. ## EXAMPLE -The following example shows how to use the Hidden keyword in a class -definition. The Car class method, Drive, has a property, rides, that does not -need to be viewed or changed (it merely tallies the number of times that Drive -is called on the Car class, a metric that is not important to users of the -class; consider, for example, that when you are buying a car, you do not ask -the seller on how many drives the car has been taken. +The following example shows how to use the `hidden` keyword in a class +definition. The **Car** class method, **Drive**, has a property, **rides**, that +does not need to be viewed or changed as it merely tallies the number of times +that **Drive** is called on the **Car** class. That metric that is not important +to users of the class (consider, for example, that when you are buying a car, +you do not ask the seller on how many drives the car has been taken). -Because there is little need for users of the class to change this property, -we can hide the property from Get-Member and automatic completion results by -using the Hidden keyword. +Because there is little need for users of the class to change this property, we +can hide the property from `Get-Member` and automatic completion results by +using the `hidden` keyword. -Add the Hidden keyword by entering it on the same statement line as the +Add the `hidden` keyword by entering it on the same statement line as the property and its data type. Although the keyword can be in any order on this-line, starting the statement with the Hidden keyword makes it easier for you +line, starting the statement with the `hidden` keyword makes it easier for you later to identify all members that you have hidden. ```powershell class Car } ``` -Now, create a new instance of the Car class, and save it in a variable, -\$TestCar. +Now, create a new instance of the **Car** class, and save it in a variable, +`$TestCar`. ```powershell $TestCar = [Car]::new() ``` -After you create the new instance, pipe the contents of the $TestCar variable -to Get-Member. Observe that the rides property is not among the members listed -in the Get-Member command results. +After you create the new instance, pipe the contents of the `$TestCar` variable +to `Get-Member`. Observe that the **rides** property is not among the members +listed in the `Get-Member` command results. ```output PS C:\Windows\system32> $TestCar | Get-Member ModelYear Property string ModelYear {get;set;} ``` -Now, try running Get-Member again, but this time, add the -Force parameter. -Note that the results contain the hidden rides property, among other members +Now, try running `Get-Member` again, but this time, add the `-Force` parameter. +Note that the results contain the hidden **rides** property, among other members that are hidden by default. ```output rides Property int rides {get;set;} [about_Wildcards](about_Wildcards.md) [Get-Member](xref:Microsoft.PowerShell.Utility.Get-Member)+ |
| Microsoft.PowerShell.Core | About Cimsession (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_CimSession.md | --- description: Describes a **CimSession** object and the difference between CIM sessions and PowerShell sessions. Locale: en-US Previously updated : 05/13/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_cimsession?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about CimSession PowerShell sessions. ## Long description +> This information only applies to PowerShell running on Windows. + A Common Information Model (CIM) session is a client-side object that represents a connection to a local computer or a remote computer. You can use CIM sessions as an alternative to PowerShell sessions (PSSessions). Both approaches have advantages. -You can use the `New-CimSession` cmdlet to create a CIM session that contains -information about a connection, such as computer name, the protocol used for -the connection, session ID, and instance ID. +You can use the `New-CimSession` cmdlet on a Windows computer to create a CIM +session that contains information about a connection, such as computer name, +the protocol used for the connection, session ID, and instance ID. After you create a **CimSession** object that specifies information required to establish a connection, PowerShell does not establish the connection understand the **ThrottleLimit**. [New-CimSession](xref:CimCmdlets.New-CimSession) [about_PSSessions](about_PSSessions.md)+ |
| Microsoft.PowerShell.Core | About Hidden (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Hidden.md | --- -description: Describes the Hidden keyword, which hides class members from default Get-Member results. +description: Describes the `hidden` keyword, which hides class members from default `Get-Member` results. Locale: en-US Previously updated : 01/04/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hidden?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Hidden Title: about Hidden # about_Hidden ## Short description-Describes the Hidden keyword, which hides class members from default -Get-Member results. +Describes the `hidden` keyword, which hides class members from default +`Get-Member` results. ## Long description -When you use the Hidden keyword in a script, you hide the members of a class -by default. The Hidden keyword can hide properties, methods (including -constructors, events, alias properties, and other member types, including -static members, from the default results of the Get-Member cmdlet, and from -IntelliSense and tab completion results. To display members that you have -hidden with the Hidden keyword, add the -Force parameter to a Get-Member -command. +When you use the `hidden` keyword in a script, you hide the members of a class +by default. Hidden members do not display in the default results of the +`Get-Member` cmdlet, IntelliSense, or tab completion results. To display members +that you have hidden with the `hidden` keyword, add the **Force** parameter to a +`Get-Member` command. -Hidden members are not displayed by using tab completion or IntelliSense, -unless the completion occurs in the class that defines the hidden member. +The `hidden` keyword can hide: -A new attribute, System.Management.Automation.HiddenAttribute, has been added, -so that C\# code can have the same semantics within PowerShell. +- methods (including constructors) +- events +- alias properties +- other member types (including static members) -The Hidden keyword is useful for creating properties and methods within a -class that you do not necessarily want other users of the class to see, or -readily be able to edit. +Hidden members are not displayed in tab completion or IntelliSense unless the +completion occurs in the class that defines the hidden member. -The Hidden keyword has no effect on how you can view or make changes to -members of a class. Like all language keywords in PowerShell, Hidden is not +The new attribute, **System.Management.Automation.HiddenAttribute**, enables C# +code to have the same semantics within PowerShell. ++The `hidden` keyword is useful for creating properties and methods within a +class that you do not necessarily want users of the class to see or readily be +able to edit. ++The `hidden` keyword has no effect on how you can view or make changes to +members of a class. Like all language keywords in PowerShell, `hidden` is not case-sensitive, and hidden members are still public. -Hidden, along with custom classes, was introduced in PowerShell 5.0. +The `hidden` keyword, along with custom classes, was introduced in Windows +PowerShell 5.0. ## EXAMPLE -The following example shows how to use the Hidden keyword in a class -definition. The Car class method, Drive, has a property, rides, that does not -need to be viewed or changed (it merely tallies the number of times that Drive -is called on the Car class, a metric that is not important to users of the -class; consider, for example, that when you are buying a car, you do not ask -the seller on how many drives the car has been taken. +The following example shows how to use the `hidden` keyword in a class +definition. The **Car** class method, **Drive**, has a property, **rides**, that +does not need to be viewed or changed as it merely tallies the number of times +that **Drive** is called on the **Car** class. That metric that is not important +to users of the class (consider, for example, that when you are buying a car, +you do not ask the seller on how many drives the car has been taken). -Because there is little need for users of the class to change this property, -we can hide the property from Get-Member and automatic completion results by -using the Hidden keyword. +Because there is little need for users of the class to change this property, we +can hide the property from `Get-Member` and automatic completion results by +using the `hidden` keyword. -Add the Hidden keyword by entering it on the same statement line as the +Add the `hidden` keyword by entering it on the same statement line as the property and its data type. Although the keyword can be in any order on this-line, starting the statement with the Hidden keyword makes it easier for you +line, starting the statement with the `hidden` keyword makes it easier for you later to identify all members that you have hidden. ```powershell class Car } ``` -Now, create a new instance of the Car class, and save it in a variable, -\$TestCar. +Now, create a new instance of the **Car** class, and save it in a variable, +`$TestCar`. ```powershell $TestCar = [Car]::new() ``` -After you create the new instance, pipe the contents of the $TestCar variable -to Get-Member. Observe that the rides property is not among the members listed -in the Get-Member command results. +After you create the new instance, pipe the contents of the `$TestCar` variable +to `Get-Member`. Observe that the **rides** property is not among the members +listed in the `Get-Member` command results. ```output PS C:\Windows\system32> $TestCar | Get-Member ModelYear Property string ModelYear {get;set;} ``` -Now, try running Get-Member again, but this time, add the -Force parameter. -Note that the results contain the hidden rides property, among other members +Now, try running `Get-Member` again, but this time, add the `-Force` parameter. +Note that the results contain the hidden **rides** property, among other members that are hidden by default. ```output rides Property int rides {get;set;} [about_Wildcards](about_Wildcards.md) [Get-Member](xref:Microsoft.PowerShell.Utility.Get-Member)+ |
| Microsoft.PowerShell.Core | About Language Modes (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Language_Modes.md | --- description: Explains language modes and their effect on PowerShell sessions. Locale: en-US Previously updated : 08/03/2021 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_language_modes?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Language Modes FullLanguage ``` On other session configurations, you can find the language mode indirectly by-finding the language mode of a session that is created by using the session +finding the language mode of a session that is created with the session configuration. +> [!NOTE] +> Session configurations are a feature of WSMan-based PowerShell remoting. They are used only when you +> use the `New-PSSession`, `Invoke-Command`, or `Enter-PSSession` cmdlets +> to connect to a remote Windows computer. The `Get-PSSessionConfiguration` +> cmdlet is only available on Windows computers. + ### Finding the language mode of a session You can find the language mode of a **FullLanguage** or **ConstrainedLanguage** |
| Microsoft.PowerShell.Core | About Pssession Details (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_PSSession_Details.md | --- description: Provides detailed information about PowerShell sessions and the role they play in remote commands. Locale: en-US Previously updated : 06/09/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pssession_details?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about PSSession Details and manage only the PSSessions that you created. ## Can I Connect to a PSSession From a Different Computer? -Beginning in Windows PowerShell 3.0, PSSessions are independent -of the sessions in which they were created. Active PSSessions +Beginning in Windows PowerShell 3.0, PSSessions on Windows computers are +independent of the sessions in which they were created. Active PSSessions are maintained on the computer at the remote or "server-side" of a connection. -You can use the `Disconnect-PSSession` cmdlet to disconnect -from a PSSession. The PSSession is disconnected from the +On a Windows computer, you can use the `Disconnect-PSSession` cmdlet to +disconnect from a PSSession. The PSSession is disconnected from the local session, but is maintained on the remote computer. Commands continue to run in the disconnected PSSession. You can close PowerShell and shut down the originating computer without interrupting the PSSession. Then, even hours later, you can use the `Get-PSSession` cmdlet to get the PSSession and the `Connect-PSSession` cmdlet to connect to the-PSSession from a new session on a different computer. +PSSession from a new session on a different Windows computer. For more information, see [about_Remote_Disconnected_Sessions](about_Remote_Disconnected_Sessions.md). |
| Microsoft.PowerShell.Core | About Pssessions (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_PSSessions.md | --- description: Describes PowerShell sessions (PSSessions) and explains how to establish a persistent connection to a remote computer. Locale: en-US Previously updated : 01/03/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pssessions?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about PSSessions You can also create a PSSession on the local computer and run commands in it. A local PSSession uses the PowerShell remoting infrastructure to create and maintain the PSSession. -Beginning in Windows PowerShell 3.0, PSSessions are independent of the -sessions in which they are created. Active PSSessions are maintained on the -remote computer (or the computer at the remote end or "server-side" of the -connection). As a result, you can disconnect from the PSSession and reconnect -to it at a later time from the same computer or from a different computer. +Beginning in Windows PowerShell 3.0, PSSessions on Windows are independent +of the sessions in which they are created. Active PSSessions are maintained +on the remote computer (or the computer at the remote end or "server-side" +of the connection). As a result, on Windows you can disconnect from a PSSession +on a remote Windows computer and reconnect to it at a later time from the +same computer or from a different Windows computer. This topic explains how to create, use, get, and delete PSSessions. For more advanced information, see Get-Help *-PSSession session - Remove-PSSession: Deletes the PSSessions in the current session +> [!NOTE] +> Disconnected sessions are only supported on Windows. The `Connect-PSSession`, +> `Disconnect-PSSession`, and `Receive-PSSession` cmdlets are only available +> on Windows. For more information about disconnected sessions, see +> [about_Remote_Disconnected_Session](about_Remote_Disconnected_Sessions.md) + ## For More Information For more information about PSSessions, see [about_PSSession_Details](about_PSSession_Details.md). For more information about PSSessions, see [about_PSSession_Details](about_PSSes [New-PSSession](xref:Microsoft.PowerShell.Core.New-PSSession) [Remove-PSSession](xref:Microsoft.PowerShell.Core.Remove-PSSession)+ |
| Microsoft.PowerShell.Core | About Providers (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Providers.md | --- description: Describes how PowerShell providers provide access to data and components that wouldn't otherwise be easily accessible at the command line. The data is presented in a consistent format that resembles a file system drive. Locale: en-US Previously updated : 03/27/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_providers?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Providers your session, type: Get-PSProvider ``` +> [!NOTE] +> The **Certificate**, **Registry**, and **WSMan** providers are only +> available on the Windows platform. + ## Installing and removing providers Providers are typically installed via PowerShell modules. Importing the module Get-Help * -Category Provider [about_Locations](about_Locations.md) [about_Path_Syntax](about_Path_Syntax.md)+ |
| Microsoft.PowerShell.Core | About Pwsh (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Pwsh.md | --- description: Explains how to use the `pwsh` command-line interface. Displays the command-line parameters and describes the syntax. Locale: en-US Previously updated : 10/22/2020 Last updated : 03/07/2022 no-loc: [-File, -f, -Command, -c, -ConfigurationName, -config, -CustomPipeName, -EncodedCommand, -e, -ec, -ExecutionPolicy, -ex, -ep, -InputFormat, -inp, -if, -Interactive, -i, -Login, -l, -MTA, -NoExit, -noe, -NoLogo, -nol, -NonInteractive, -noni, -NoProfile, -nop, -OutputFormat, -o, -of, -SettingsFile, -settings, -SSHServerMode, -sshs, -STA, -Version, -v, -WindowStyle, -w, -WorkingDirectory, -wd, -Help] online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pwsh?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 intended or supported for any other use. ### -STA Start PowerShell using a single-threaded apartment. This is the default. This-switch is only available on Windows. +switch is only available on the Windows platform. ### -Version | -v |
| Microsoft.PowerShell.Core | About Registry Provider (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Registry_Provider.md | --- description: Registry Locale: en-US Previously updated : 09/28/2021 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_registry_provider?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Registry Provider Provides access to the registry keys, entries, and values in PowerShell. ## Detailed description +> This information only applies to PowerShell running on Windows. + The PowerShell **Registry** provider lets you get, add, change, clear, and delete registry keys, entries, and values in PowerShell. |
| Microsoft.PowerShell.Core | About Remote Disconnected Sessions (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Disconnected_Sessions.md | --- description: Explains how to disconnect and reconnect to a PowerShell Session (PSSession). Locale: en-US Previously updated : 12/01/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_disconnected_sessions?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Remote Disconnected Sessions state is maintained and commands in the PSSession continue to run while the session is disconnected. The Disconnected Sessions feature is only available when the remote computer is-running PowerShell 3.0 or a later version. +a Windows computer running PowerShell 3.0 or a later version and the local +computer is running Windows. The Disconnected Sessions feature allows you to close the session in which a PSSession was created, and even close PowerShell, and shut down the computer, without disrupting commands running in the PSSession. Disconnected sessions are useful for running commands that take an extended time to complete, and provides the time and device flexibility that IT professionals require. -You can't disconnect from an interactive session that is started by using the +You can't disconnect from an interactive session that is started with the `Enter-PSSession` cmdlet. You can use disconnected sessions to manage PSSessions that were disconnected PowerShell doesn't attempt to maintain the PSSession. [Receive-PSSession](xref:Microsoft.PowerShell.Core.Receive-PSSession) [Invoke-Command](xref:Microsoft.PowerShell.Core.Invoke-Command)+ |
| Microsoft.PowerShell.Core | About Remote Output (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Output.md | --- description: Describes how to interpret and format the output of remote commands. Locale: en-US Previously updated : 12/01/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_output?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Remote Output in a streaming list. When objects are not formatted automatically, you can use the formatting cmdlets, such as Format-Table or Format-List, to format and display-selected properties. Or, you can use the Out-GridView cmdlet to display -the objects in a table. +selected properties. On a Windows computer, you can use the `Out-GridView` +cmdlet to display the objects in a table. Also, if you run a command on a remote computer that uses cmdlets that you do not have on your local computer, the objects that the command returns computers are interspersed. [Invoke-Command](xref:Microsoft.PowerShell.Core.Invoke-Command) [Select-Object](xref:Microsoft.PowerShell.Utility.Select-Object)+ |
| Microsoft.PowerShell.Core | About Session Configuration Files (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Session_Configuration_Files.md | --- description: Describes session configuration files, which are used in a session configuration (also known as an endpoint) to define the environment of sessions that use the session configuration. Locale: en-US Previously updated : 01/03/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_session_configuration_files?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Session Configuration Files sessions that use the session configuration. ## Long description +> This information only applies to PowerShell running on Windows. + A "session configuration file" is a text file with a .pssc file name extension that contains a hash table of session configuration properties and values. You can use a session configuration file to set the properties of a session working with an empty session. [Get-PSSessionCapability](xref:Microsoft.PowerShell.Core.Get-PSSessionCapability) [New-PSRoleCapabilityFile](xref:Microsoft.PowerShell.Core.New-PSRoleCapabilityFile)+ |
| Microsoft.PowerShell.Core | About Session Configurations (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Session_Configurations.md | --- description: Describes session configurations, which determine the users who can connect to the computer remotely and the commands they can run. Locale: en-US Previously updated : 12/09/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_session_configurations?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Session Configurations New-PSSessionConfiguration cmdlet. For more information about session configuration files, see [about_Session_Configuration_Files](about_Session_Configuration_Files.md). -Session configurations are a feature of Web Services for Management -(WS-Management) based PowerShell remoting. They are used only when you use the -New-PSSession, Invoke-Command, or Enter-PSSession cmdlets to connect to a -remote computer. +Session configurations are a feature of WSMAN-based PowerShell remoting. They +are used only when you use the `New-PSSession`, `Invoke-Command`, or +`Enter-PSSession` cmdlets to connect to a remote Windows computer. -Note: To manage the session configurations, start PowerShell with the -"Run as administrator" option. +To manage the session configurations on a Windows computer, start +PowerShell with the **Run as administrator** option. About Session Configurations about_SessionConfigurations [Test-PSSessionConfigurationFile](xref:Microsoft.PowerShell.Core.Test-PSSessionConfigurationFile) [Unregister-PSSessionConfiguration](xref:Microsoft.PowerShell.Core.Unregister-PSSessionConfiguration)+ |
| Microsoft.PowerShell.Core | About Signing (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Signing.md | --- description: Explains how to sign scripts so that they comply with the PowerShell execution policies. Locale: en-US Previously updated : 01/21/2022 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Signing policies. ## Long description +> This information only applies to PowerShell running on Windows. + The Restricted execution policy does not permit any scripts to run. The **AllSigned** and **RemoteSigned** execution policies prevent PowerShell from running scripts that do not have a digital signature. |
| Microsoft.PowerShell.Security | About Certificate Provider (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Security/About/about_Certificate_Provider.md | --- description: Information about the Certificate provider. Locale: en-US Previously updated : 06/04/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.security/about/about_certificate_provider?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Certificate Provider Provides access to X.509 certificate stores and certificates in PowerShell. ## Detailed description +> This information only applies to PowerShell running on Windows. + The PowerShell **Certificate** provider lets you get, add, change, clear, and delete certificates and certificate stores in PowerShell. |
| Microsoft.WSMan.Management | About Wsman Provider (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.WSMan.Management/About/about_WSMan_Provider.md | --- description: WSMan Locale: en-US Previously updated : 10/18/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.wsman.management/about/about_wsman_provider?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about WSMan Provider information. ## Detailed description +> This information only applies to PowerShell running on Windows. + The **WSMan** provider for PowerShell lets you add, change, clear, and delete WS-Management configuration data on local or remote computers. |
| Microsoft.PowerShell.Core | About Cimsession (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_CimSession.md | --- description: Describes a **CimSession** object and the difference between CIM sessions and PowerShell sessions. Locale: en-US Previously updated : 05/13/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_cimsession?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about CimSession PowerShell sessions. ## Long description +> This information only applies to PowerShell running on Windows. + A Common Information Model (CIM) session is a client-side object that represents a connection to a local computer or a remote computer. You can use CIM sessions as an alternative to PowerShell sessions (PSSessions). Both approaches have advantages. -You can use the `New-CimSession` cmdlet to create a CIM session that contains -information about a connection, such as computer name, the protocol used for -the connection, session ID, and instance ID. +You can use the `New-CimSession` cmdlet on a Windows computer to create a CIM +session that contains information about a connection, such as computer name, +the protocol used for the connection, session ID, and instance ID. After you create a **CimSession** object that specifies information required to establish a connection, PowerShell does not establish the connection |
| Microsoft.PowerShell.Core | About Hidden (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Hidden.md | --- -description: Describes the Hidden keyword, which hides class members from default Get-Member results. +description: Describes the `hidden` keyword, which hides class members from default `Get-Member` results. Locale: en-US Previously updated : 01/04/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hidden?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Hidden Title: about Hidden # about_Hidden ## Short description-Describes the Hidden keyword, which hides class members from default -Get-Member results. +Describes the `hidden` keyword, which hides class members from default +`Get-Member` results. ## Long description -When you use the Hidden keyword in a script, you hide the members of a class -by default. The Hidden keyword can hide properties, methods (including -constructors, events, alias properties, and other member types, including -static members, from the default results of the Get-Member cmdlet, and from -IntelliSense and tab completion results. To display members that you have -hidden with the Hidden keyword, add the -Force parameter to a Get-Member -command. +When you use the `hidden` keyword in a script, you hide the members of a class +by default. Hidden members do not display in the default results of the +`Get-Member` cmdlet, IntelliSense, or tab completion results. To display members +that you have hidden with the `hidden` keyword, add the **Force** parameter to a +`Get-Member` command. -Hidden members are not displayed by using tab completion or IntelliSense, -unless the completion occurs in the class that defines the hidden member. +The `hidden` keyword can hide: -A new attribute, System.Management.Automation.HiddenAttribute, has been added, -so that C\# code can have the same semantics within PowerShell. +- methods (including constructors) +- events +- alias properties +- other member types (including static members) -The Hidden keyword is useful for creating properties and methods within a -class that you do not necessarily want other users of the class to see, or -readily be able to edit. +Hidden members are not displayed in tab completion or IntelliSense unless the +completion occurs in the class that defines the hidden member. -The Hidden keyword has no effect on how you can view or make changes to -members of a class. Like all language keywords in PowerShell, Hidden is not +The new attribute, **System.Management.Automation.HiddenAttribute**, enables C# +code to have the same semantics within PowerShell. ++The `hidden` keyword is useful for creating properties and methods within a +class that you do not necessarily want users of the class to see or readily be +able to edit. ++The `hidden` keyword has no effect on how you can view or make changes to +members of a class. Like all language keywords in PowerShell, `hidden` is not case-sensitive, and hidden members are still public. -Hidden, along with custom classes, was introduced in PowerShell 5.0. +The `hidden` keyword, along with custom classes, was introduced in Windows +PowerShell 5.0. ## EXAMPLE -The following example shows how to use the Hidden keyword in a class -definition. The Car class method, Drive, has a property, rides, that does not -need to be viewed or changed (it merely tallies the number of times that Drive -is called on the Car class, a metric that is not important to users of the -class; consider, for example, that when you are buying a car, you do not ask -the seller on how many drives the car has been taken. +The following example shows how to use the `hidden` keyword in a class +definition. The **Car** class method, **Drive**, has a property, **rides**, that +does not need to be viewed or changed as it merely tallies the number of times +that **Drive** is called on the **Car** class. That metric that is not important +to users of the class (consider, for example, that when you are buying a car, +you do not ask the seller on how many drives the car has been taken). -Because there is little need for users of the class to change this property, -we can hide the property from Get-Member and automatic completion results by -using the Hidden keyword. +Because there is little need for users of the class to change this property, we +can hide the property from `Get-Member` and automatic completion results by +using the `hidden` keyword. -Add the Hidden keyword by entering it on the same statement line as the +Add the `hidden` keyword by entering it on the same statement line as the property and its data type. Although the keyword can be in any order on this-line, starting the statement with the Hidden keyword makes it easier for you +line, starting the statement with the `hidden` keyword makes it easier for you later to identify all members that you have hidden. ```powershell class Car } ``` -Now, create a new instance of the Car class, and save it in a variable, -\$TestCar. +Now, create a new instance of the **Car** class, and save it in a variable, +`$TestCar`. ```powershell $TestCar = [Car]::new() ``` -After you create the new instance, pipe the contents of the $TestCar variable -to Get-Member. Observe that the rides property is not among the members listed -in the Get-Member command results. +After you create the new instance, pipe the contents of the `$TestCar` variable +to `Get-Member`. Observe that the **rides** property is not among the members +listed in the `Get-Member` command results. ```output PS C:\Windows\system32> $TestCar | Get-Member ModelYear Property string ModelYear {get;set;} ``` -Now, try running Get-Member again, but this time, add the -Force parameter. -Note that the results contain the hidden rides property, among other members +Now, try running `Get-Member` again, but this time, add the `-Force` parameter. +Note that the results contain the hidden **rides** property, among other members that are hidden by default. ```output |
| Microsoft.PowerShell.Core | About Language Modes (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Language_Modes.md | --- description: Explains language modes and their effect on PowerShell sessions. Locale: en-US Previously updated : 08/03/2021 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_language_modes?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Language Modes FullLanguage ``` On other session configurations, you can find the language mode indirectly by-finding the language mode of a session that is created by using the session +finding the language mode of a session that is created with the session configuration. +> [!NOTE] +> Session configurations are a feature of WSMan-based PowerShell remoting. They are used only when you +> use the `New-PSSession`, `Invoke-Command`, or `Enter-PSSession` cmdlets +> to connect to a remote Windows computer. The `Get-PSSessionConfiguration` +> cmdlet is only available on Windows computers. + ### Finding the language mode of a session You can find the language mode of a **FullLanguage** or **ConstrainedLanguage** |
| Microsoft.PowerShell.Core | About Pssession Details (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_PSSession_Details.md | --- description: Provides detailed information about PowerShell sessions and the role they play in remote commands. Locale: en-US Previously updated : 06/09/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pssession_details?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about PSSession Details and manage only the PSSessions that you created. ## Can I Connect to a PSSession From a Different Computer? -Beginning in Windows PowerShell 3.0, PSSessions are independent -of the sessions in which they were created. Active PSSessions +Beginning in Windows PowerShell 3.0, PSSessions on Windows computers are +independent of the sessions in which they were created. Active PSSessions are maintained on the computer at the remote or "server-side" of a connection. -You can use the `Disconnect-PSSession` cmdlet to disconnect -from a PSSession. The PSSession is disconnected from the +On a Windows computer, you can use the `Disconnect-PSSession` cmdlet to +disconnect from a PSSession. The PSSession is disconnected from the local session, but is maintained on the remote computer. Commands continue to run in the disconnected PSSession. You can close PowerShell and shut down the originating computer without interrupting the PSSession. Then, even hours later, you can use the `Get-PSSession` cmdlet to get the PSSession and the `Connect-PSSession` cmdlet to connect to the-PSSession from a new session on a different computer. +PSSession from a new session on a different Windows computer. For more information, see [about_Remote_Disconnected_Sessions](about_Remote_Disconnected_Sessions.md). |
| Microsoft.PowerShell.Core | About Pssessions (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_PSSessions.md | --- description: Describes PowerShell sessions (PSSessions) and explains how to establish a persistent connection to a remote computer. Locale: en-US Previously updated : 01/03/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pssessions?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about PSSessions You can also create a PSSession on the local computer and run commands in it. A local PSSession uses the PowerShell remoting infrastructure to create and maintain the PSSession. -Beginning in Windows PowerShell 3.0, PSSessions are independent of the -sessions in which they are created. Active PSSessions are maintained on the -remote computer (or the computer at the remote end or "server-side" of the -connection). As a result, you can disconnect from the PSSession and reconnect -to it at a later time from the same computer or from a different computer. +Beginning in Windows PowerShell 3.0, PSSessions on Windows are independent +of the sessions in which they are created. Active PSSessions are maintained +on the remote computer (or the computer at the remote end or "server-side" +of the connection). As a result, on Windows you can disconnect from a PSSession +on a remote Windows computer and reconnect to it at a later time from the +same computer or from a different Windows computer. This topic explains how to create, use, get, and delete PSSessions. For more advanced information, see Get-Help *-PSSession session - Remove-PSSession: Deletes the PSSessions in the current session +> [!NOTE] +> Disconnected sessions are only supported on Windows. The `Connect-PSSession`, +> `Disconnect-PSSession`, and `Receive-PSSession` cmdlets are only available +> on Windows. For more information about disconnected sessions, see +> [about_Remote_Disconnected_Session](about_Remote_Disconnected_Sessions.md) + ## For More Information For more information about PSSessions, see [about_PSSession_Details](about_PSSession_Details.md). |
| Microsoft.PowerShell.Core | About Providers (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Providers.md | --- description: Describes how PowerShell providers provide access to data and components that wouldn't otherwise be easily accessible at the command line. The data is presented in a consistent format that resembles a file system drive. Locale: en-US Previously updated : 03/27/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_providers?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Providers your session, type: Get-PSProvider ``` +> [!NOTE] +> The **Certificate**, **Registry**, and **WSMan** providers are only +> available on the Windows platform. + ## Installing and removing providers Providers are typically installed via PowerShell modules. Importing the module |
| Microsoft.PowerShell.Core | About Pwsh (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Pwsh.md | --- description: Explains how to use the `pwsh` command-line interface. Displays the command-line parameters and describes the syntax. Locale: en-US Previously updated : 10/22/2020 Last updated : 03/07/2022 no-loc: [-File, -f, -Command, -c, -ConfigurationName, -config, -CustomPipeName, -EncodedCommand, -e, -ec, -ExecutionPolicy, -ex, -ep, -InputFormat, -inp, -if, -Interactive, -i, -Login, -l, -MTA, -NoExit, -noe, -NoLogo, -nol, -NonInteractive, -noni, -NoProfile, -nop, -OutputFormat, -o, -of, -SettingsFile, -settings, -SSHServerMode, -sshs, -STA, -Version, -v, -WindowStyle, -w, -WorkingDirectory, -wd, -Help] online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pwsh?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 intended or supported for any other use. ### -STA Start PowerShell using a single-threaded apartment. This is the default. This-switch is only available on Windows. +switch is only available on the Windows platform. ### -Version | -v |
| Microsoft.PowerShell.Core | About Registry Provider (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Registry_Provider.md | --- description: Registry Locale: en-US Previously updated : 09/28/2021 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_registry_provider?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Registry Provider Provides access to the registry keys, entries, and values in PowerShell. ## Detailed description +> This information only applies to PowerShell running on Windows. + The PowerShell **Registry** provider lets you get, add, change, clear, and delete registry keys, entries, and values in PowerShell. |
| Microsoft.PowerShell.Core | About Remote Disconnected Sessions (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Disconnected_Sessions.md | --- description: Explains how to disconnect and reconnect to a PowerShell Session (PSSession). Locale: en-US Previously updated : 12/01/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_disconnected_sessions?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Remote Disconnected Sessions state is maintained and commands in the PSSession continue to run while the session is disconnected. The Disconnected Sessions feature is only available when the remote computer is-running PowerShell 3.0 or a later version. +a Windows computer running PowerShell 3.0 or a later version and the local +computer is running Windows. The Disconnected Sessions feature allows you to close the session in which a PSSession was created, and even close PowerShell, and shut down the computer, without disrupting commands running in the PSSession. Disconnected sessions are useful for running commands that take an extended time to complete, and provides the time and device flexibility that IT professionals require. -You can't disconnect from an interactive session that is started by using the +You can't disconnect from an interactive session that is started with the `Enter-PSSession` cmdlet. You can use disconnected sessions to manage PSSessions that were disconnected |
| Microsoft.PowerShell.Core | About Session Configurations (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Session_Configurations.md | --- description: Describes session configurations, which determine the users who can connect to the computer remotely and the commands they can run. Locale: en-US Previously updated : 12/09/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_session_configurations?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Session Configurations New-PSSessionConfiguration cmdlet. For more information about session configuration files, see [about_Session_Configuration_Files](about_Session_Configuration_Files.md). -Session configurations are a feature of Web Services for Management -(WS-Management) based PowerShell remoting. They are used only when you use the -New-PSSession, Invoke-Command, or Enter-PSSession cmdlets to connect to a -remote computer. +Session configurations are a feature of WSMAN-based PowerShell remoting. They +are used only when you use the `New-PSSession`, `Invoke-Command`, or +`Enter-PSSession` cmdlets to connect to a remote Windows computer. -Note: To manage the session configurations, start PowerShell with the -"Run as administrator" option. +To manage the session configurations on a Windows computer, start +PowerShell with the **Run as administrator** option. About Session Configurations |
| Microsoft.PowerShell.Core | About Signing (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Signing.md | --- description: Explains how to sign scripts so that they comply with the PowerShell execution policies. Locale: en-US Previously updated : 01/21/2022 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Signing policies. ## Long description +> This information only applies to PowerShell running on Windows. + The Restricted execution policy does not permit any scripts to run. The **AllSigned** and **RemoteSigned** execution policies prevent PowerShell from running scripts that do not have a digital signature. |
| Microsoft.PowerShell.Security | About Certificate Provider (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Security/About/about_Certificate_Provider.md | --- description: Information about the Certificate provider. Locale: en-US Previously updated : 06/04/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.security/about/about_certificate_provider?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Certificate Provider Provides access to X.509 certificate stores and certificates in PowerShell. ## Detailed description +> This information only applies to PowerShell running on Windows. + The PowerShell **Certificate** provider lets you get, add, change, clear, and delete certificates and certificate stores in PowerShell. |
| Microsoft.WSMan.Management | About Wsman Provider (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.WSMan.Management/About/about_WSMan_Provider.md | --- description: WSMan Locale: en-US Previously updated : 10/18/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.wsman.management/about/about_wsman_provider?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about WSMan Provider information. ## Detailed description +> This information only applies to PowerShell running on Windows. + The **WSMan** provider for PowerShell lets you add, change, clear, and delete WS-Management configuration data on local or remote computers. |
| Microsoft.PowerShell.Core | About Cimsession (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_CimSession.md | --- description: Describes a **CimSession** object and the difference between CIM sessions and PowerShell sessions. Locale: en-US Previously updated : 05/13/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_cimsession?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about CimSession PowerShell sessions. ## Long description +> This information only applies to PowerShell running on Windows. + A Common Information Model (CIM) session is a client-side object that represents a connection to a local computer or a remote computer. You can use CIM sessions as an alternative to PowerShell sessions (PSSessions). Both approaches have advantages. -You can use the `New-CimSession` cmdlet to create a CIM session that contains -information about a connection, such as computer name, the protocol used for -the connection, session ID, and instance ID. +You can use the `New-CimSession` cmdlet on a Windows computer to create a CIM +session that contains information about a connection, such as computer name, +the protocol used for the connection, session ID, and instance ID. After you create a **CimSession** object that specifies information required to establish a connection, PowerShell does not establish the connection |
| Microsoft.PowerShell.Core | About Hidden (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Hidden.md | --- -description: Describes the Hidden keyword, which hides class members from default Get-Member results. +description: Describes the `hidden` keyword, which hides class members from default `Get-Member` results. Locale: en-US Previously updated : 01/04/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hidden?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Hidden Title: about Hidden # about_Hidden ## Short description-Describes the Hidden keyword, which hides class members from default -Get-Member results. +Describes the `hidden` keyword, which hides class members from default +`Get-Member` results. ## Long description -When you use the Hidden keyword in a script, you hide the members of a class -by default. The Hidden keyword can hide properties, methods (including -constructors, events, alias properties, and other member types, including -static members, from the default results of the Get-Member cmdlet, and from -IntelliSense and tab completion results. To display members that you have -hidden with the Hidden keyword, add the -Force parameter to a Get-Member -command. +When you use the `hidden` keyword in a script, you hide the members of a class +by default. Hidden members do not display in the default results of the +`Get-Member` cmdlet, IntelliSense, or tab completion results. To display members +that you have hidden with the `hidden` keyword, add the **Force** parameter to a +`Get-Member` command. -Hidden members are not displayed by using tab completion or IntelliSense, -unless the completion occurs in the class that defines the hidden member. +The `hidden` keyword can hide: -A new attribute, System.Management.Automation.HiddenAttribute, has been added, -so that C\# code can have the same semantics within PowerShell. +- methods (including constructors) +- events +- alias properties +- other member types (including static members) -The Hidden keyword is useful for creating properties and methods within a -class that you do not necessarily want other users of the class to see, or -readily be able to edit. +Hidden members are not displayed in tab completion or IntelliSense unless the +completion occurs in the class that defines the hidden member. -The Hidden keyword has no effect on how you can view or make changes to -members of a class. Like all language keywords in PowerShell, Hidden is not +The new attribute, **System.Management.Automation.HiddenAttribute**, enables C# +code to have the same semantics within PowerShell. ++The `hidden` keyword is useful for creating properties and methods within a +class that you do not necessarily want users of the class to see or readily be +able to edit. ++The `hidden` keyword has no effect on how you can view or make changes to +members of a class. Like all language keywords in PowerShell, `hidden` is not case-sensitive, and hidden members are still public. -Hidden, along with custom classes, was introduced in PowerShell 5.0. +The `hidden` keyword, along with custom classes, was introduced in Windows +PowerShell 5.0. ## EXAMPLE -The following example shows how to use the Hidden keyword in a class -definition. The Car class method, Drive, has a property, rides, that does not -need to be viewed or changed (it merely tallies the number of times that Drive -is called on the Car class, a metric that is not important to users of the -class; consider, for example, that when you are buying a car, you do not ask -the seller on how many drives the car has been taken. +The following example shows how to use the `hidden` keyword in a class +definition. The **Car** class method, **Drive**, has a property, **rides**, that +does not need to be viewed or changed as it merely tallies the number of times +that **Drive** is called on the **Car** class. That metric that is not important +to users of the class (consider, for example, that when you are buying a car, +you do not ask the seller on how many drives the car has been taken). -Because there is little need for users of the class to change this property, -we can hide the property from Get-Member and automatic completion results by -using the Hidden keyword. +Because there is little need for users of the class to change this property, we +can hide the property from `Get-Member` and automatic completion results by +using the `hidden` keyword. -Add the Hidden keyword by entering it on the same statement line as the +Add the `hidden` keyword by entering it on the same statement line as the property and its data type. Although the keyword can be in any order on this-line, starting the statement with the Hidden keyword makes it easier for you +line, starting the statement with the `hidden` keyword makes it easier for you later to identify all members that you have hidden. ```powershell class Car } ``` -Now, create a new instance of the Car class, and save it in a variable, -\$TestCar. +Now, create a new instance of the **Car** class, and save it in a variable, +`$TestCar`. ```powershell $TestCar = [Car]::new() ``` -After you create the new instance, pipe the contents of the $TestCar variable -to Get-Member. Observe that the rides property is not among the members listed -in the Get-Member command results. +After you create the new instance, pipe the contents of the `$TestCar` variable +to `Get-Member`. Observe that the **rides** property is not among the members +listed in the `Get-Member` command results. ```output PS C:\Windows\system32> $TestCar | Get-Member ModelYear Property string ModelYear {get;set;} ``` -Now, try running Get-Member again, but this time, add the -Force parameter. -Note that the results contain the hidden rides property, among other members +Now, try running `Get-Member` again, but this time, add the `-Force` parameter. +Note that the results contain the hidden **rides** property, among other members that are hidden by default. ```output |
| Microsoft.PowerShell.Core | About Language Modes (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Language_Modes.md | --- description: Explains language modes and their effect on PowerShell sessions. Locale: en-US Previously updated : 08/03/2021 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_language_modes?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Language Modes FullLanguage ``` On other session configurations, you can find the language mode indirectly by-finding the language mode of a session that is created by using the session +finding the language mode of a session that is created with the session configuration. +> [!NOTE] +> Session configurations are a feature of WSMan-based PowerShell remoting. They are used only when you +> use the `New-PSSession`, `Invoke-Command`, or `Enter-PSSession` cmdlets +> to connect to a remote Windows computer. The `Get-PSSessionConfiguration` +> cmdlet is only available on Windows computers. + ### Finding the language mode of a session You can find the language mode of a **FullLanguage** or **ConstrainedLanguage** |
| Microsoft.PowerShell.Core | About Pssession Details (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_PSSession_Details.md | --- description: Provides detailed information about PowerShell sessions and the role they play in remote commands. Locale: en-US Previously updated : 06/09/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pssession_details?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about PSSession Details and manage only the PSSessions that you created. ## Can I Connect to a PSSession From a Different Computer? -Beginning in Windows PowerShell 3.0, PSSessions are independent -of the sessions in which they were created. Active PSSessions +Beginning in Windows PowerShell 3.0, PSSessions on Windows computers are +independent of the sessions in which they were created. Active PSSessions are maintained on the computer at the remote or "server-side" of a connection. -You can use the `Disconnect-PSSession` cmdlet to disconnect -from a PSSession. The PSSession is disconnected from the +On a Windows computer, you can use the `Disconnect-PSSession` cmdlet to +disconnect from a PSSession. The PSSession is disconnected from the local session, but is maintained on the remote computer. Commands continue to run in the disconnected PSSession. You can close PowerShell and shut down the originating computer without interrupting the PSSession. Then, even hours later, you can use the `Get-PSSession` cmdlet to get the PSSession and the `Connect-PSSession` cmdlet to connect to the-PSSession from a new session on a different computer. +PSSession from a new session on a different Windows computer. For more information, see [about_Remote_Disconnected_Sessions](about_Remote_Disconnected_Sessions.md). |
| Microsoft.PowerShell.Core | About Pssessions (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_PSSessions.md | --- description: Describes PowerShell sessions (PSSessions) and explains how to establish a persistent connection to a remote computer. Locale: en-US Previously updated : 01/03/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pssessions?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about PSSessions You can also create a PSSession on the local computer and run commands in it. A local PSSession uses the PowerShell remoting infrastructure to create and maintain the PSSession. -Beginning in Windows PowerShell 3.0, PSSessions are independent of the -sessions in which they are created. Active PSSessions are maintained on the -remote computer (or the computer at the remote end or "server-side" of the -connection). As a result, you can disconnect from the PSSession and reconnect -to it at a later time from the same computer or from a different computer. +Beginning in Windows PowerShell 3.0, PSSessions on Windows are independent +of the sessions in which they are created. Active PSSessions are maintained +on the remote computer (or the computer at the remote end or "server-side" +of the connection). As a result, on Windows you can disconnect from a PSSession +on a remote Windows computer and reconnect to it at a later time from the +same computer or from a different Windows computer. This topic explains how to create, use, get, and delete PSSessions. For more advanced information, see Get-Help *-PSSession session - Remove-PSSession: Deletes the PSSessions in the current session +> [!NOTE] +> Disconnected sessions are only supported on Windows. The `Connect-PSSession`, +> `Disconnect-PSSession`, and `Receive-PSSession` cmdlets are only available +> on Windows. For more information about disconnected sessions, see +> [about_Remote_Disconnected_Session](about_Remote_Disconnected_Sessions.md) + ## For More Information For more information about PSSessions, see [about_PSSession_Details](about_PSSession_Details.md). |
| Microsoft.PowerShell.Core | About Providers (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Providers.md | --- description: Describes how PowerShell providers provide access to data and components that wouldn't otherwise be easily accessible at the command line. The data is presented in a consistent format that resembles a file system drive. Locale: en-US Previously updated : 03/27/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_providers?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Providers your session, type: Get-PSProvider ``` +> [!NOTE] +> The **Certificate**, **Registry**, and **WSMan** providers are only +> available on the Windows platform. + ## Installing and removing providers Providers are typically installed via PowerShell modules. Importing the module |
| Microsoft.PowerShell.Core | About Pwsh (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Pwsh.md | --- description: Explains how to use the `pwsh` command-line interface. Displays the command-line parameters and describes the syntax. Locale: en-US Previously updated : 10/22/2020 Last updated : 03/07/2022 no-loc: [-File, -f, -Command, -c, -ConfigurationName, -config, -CustomPipeName, -EncodedCommand, -e, -ec, -ExecutionPolicy, -ex, -ep, -InputFormat, -inp, -if, -Interactive, -i, -Login, -l, -MTA, -NoExit, -noe, -NoLogo, -nol, -NonInteractive, -noni, -NoProfile, -nop, -OutputFormat, -o, -of, -SettingsFile, -settings, -SSHServerMode, -sshs, -STA, -Version, -v, -WindowStyle, -w, -WorkingDirectory, -wd, -Help] online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pwsh?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 intended or supported for any other use. ### -STA Start PowerShell using a single-threaded apartment. This is the default. This-switch is only available on Windows. +switch is only available on the Windows platform. ### -Version | -v |
| Microsoft.PowerShell.Core | About Registry Provider (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Registry_Provider.md | --- description: Registry Locale: en-US Previously updated : 09/28/2021 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_registry_provider?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Registry Provider Provides access to the registry keys, entries, and values in PowerShell. ## Detailed description +> This information only applies to PowerShell running on Windows. + The PowerShell **Registry** provider lets you get, add, change, clear, and delete registry keys, entries, and values in PowerShell. |
| Microsoft.PowerShell.Core | About Remote Disconnected Sessions (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Remote_Disconnected_Sessions.md | --- description: Explains how to disconnect and reconnect to a PowerShell Session (PSSession). Locale: en-US Previously updated : 12/01/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_disconnected_sessions?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Remote Disconnected Sessions state is maintained and commands in the PSSession continue to run while the session is disconnected. The Disconnected Sessions feature is only available when the remote computer is-running PowerShell 3.0 or a later version. +a Windows computer running PowerShell 3.0 or a later version and the local +computer is running Windows. The Disconnected Sessions feature allows you to close the session in which a PSSession was created, and even close PowerShell, and shut down the computer, without disrupting commands running in the PSSession. Disconnected sessions are useful for running commands that take an extended time to complete, and provides the time and device flexibility that IT professionals require. -You can't disconnect from an interactive session that is started by using the +You can't disconnect from an interactive session that is started with the `Enter-PSSession` cmdlet. You can use disconnected sessions to manage PSSessions that were disconnected |
| Microsoft.PowerShell.Core | About Session Configurations (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Session_Configurations.md | --- description: Describes session configurations, which determine the users who can connect to the computer remotely and the commands they can run. Locale: en-US Previously updated : 12/09/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_session_configurations?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Session Configurations New-PSSessionConfiguration cmdlet. For more information about session configuration files, see [about_Session_Configuration_Files](about_Session_Configuration_Files.md). -Session configurations are a feature of Web Services for Management -(WS-Management) based PowerShell remoting. They are used only when you use the -New-PSSession, Invoke-Command, or Enter-PSSession cmdlets to connect to a -remote computer. +Session configurations are a feature of WSMAN-based PowerShell remoting. They +are used only when you use the `New-PSSession`, `Invoke-Command`, or +`Enter-PSSession` cmdlets to connect to a remote Windows computer. -Note: To manage the session configurations, start PowerShell with the -"Run as administrator" option. +To manage the session configurations on a Windows computer, start +PowerShell with the **Run as administrator** option. About Session Configurations |
| Microsoft.PowerShell.Core | About Signing (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Signing.md | --- description: Explains how to sign scripts so that they comply with the PowerShell execution policies. Locale: en-US Previously updated : 01/21/2022 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Signing policies. ## Long description +> This information only applies to PowerShell running on Windows. + The Restricted execution policy does not permit any scripts to run. The **AllSigned** and **RemoteSigned** execution policies prevent PowerShell from running scripts that do not have a digital signature. |
| Microsoft.PowerShell.Security | About Certificate Provider (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Security/About/about_Certificate_Provider.md | --- description: Information about the Certificate provider. Locale: en-US Previously updated : 06/04/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.security/about/about_certificate_provider?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Certificate Provider Provides access to X.509 certificate stores and certificates in PowerShell. ## Detailed description +> This information only applies to PowerShell running on Windows. + The PowerShell **Certificate** provider lets you get, add, change, clear, and delete certificates and certificate stores in PowerShell. |
| Microsoft.WSMan.Management | About Wsman Provider (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.WSMan.Management/About/about_WSMan_Provider.md | --- description: WSMan Locale: en-US Previously updated : 10/18/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.wsman.management/about/about_wsman_provider?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about WSMan Provider information. ## Detailed description +> This information only applies to PowerShell running on Windows. + The **WSMan** provider for PowerShell lets you add, change, clear, and delete WS-Management configuration data on local or remote computers. |
| Microsoft.PowerShell.Core | About Cimsession (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_CimSession.md | --- description: Describes a **CimSession** object and the difference between CIM sessions and PowerShell sessions. Locale: en-US Previously updated : 05/13/2020 -online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_cimsession?view=powershell-7.3&WT.mc_id=ps-gethelp Last updated : 03/07/2022+online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_cimsession?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about CimSession --- PowerShell sessions. ## Long description +> This information only applies to PowerShell running on Windows. + A Common Information Model (CIM) session is a client-side object that represents a connection to a local computer or a remote computer. You can use CIM sessions as an alternative to PowerShell sessions (PSSessions). Both approaches have advantages. -You can use the `New-CimSession` cmdlet to create a CIM session that contains -information about a connection, such as computer name, the protocol used for -the connection, session ID, and instance ID. +You can use the `New-CimSession` cmdlet on a Windows computer to create a CIM +session that contains information about a connection, such as computer name, +the protocol used for the connection, session ID, and instance ID. After you create a **CimSession** object that specifies information required to establish a connection, PowerShell does not establish the connection |
| Microsoft.PowerShell.Core | About Hidden (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Hidden.md | --- -description: Describes the Hidden keyword, which hides class members from default Get-Member results. +description: Describes the `hidden` keyword, which hides class members from default `Get-Member` results. Locale: en-US Previously updated : 01/04/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hidden?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Hidden Title: about Hidden # about_Hidden ## Short description-Describes the Hidden keyword, which hides class members from default -Get-Member results. +Describes the `hidden` keyword, which hides class members from default +`Get-Member` results. ## Long description -When you use the Hidden keyword in a script, you hide the members of a class -by default. The Hidden keyword can hide properties, methods (including -constructors, events, alias properties, and other member types, including -static members, from the default results of the Get-Member cmdlet, and from -IntelliSense and tab completion results. To display members that you have -hidden with the Hidden keyword, add the -Force parameter to a Get-Member -command. +When you use the `hidden` keyword in a script, you hide the members of a class +by default. Hidden members do not display in the default results of the +`Get-Member` cmdlet, IntelliSense, or tab completion results. To display members +that you have hidden with the `hidden` keyword, add the **Force** parameter to a +`Get-Member` command. -Hidden members are not displayed by using tab completion or IntelliSense, -unless the completion occurs in the class that defines the hidden member. +The `hidden` keyword can hide: -A new attribute, System.Management.Automation.HiddenAttribute, has been added, -so that C\# code can have the same semantics within PowerShell. +- methods (including constructors) +- events +- alias properties +- other member types (including static members) -The Hidden keyword is useful for creating properties and methods within a -class that you do not necessarily want other users of the class to see, or -readily be able to edit. +Hidden members are not displayed in tab completion or IntelliSense unless the +completion occurs in the class that defines the hidden member. -The Hidden keyword has no effect on how you can view or make changes to -members of a class. Like all language keywords in PowerShell, Hidden is not +The new attribute, **System.Management.Automation.HiddenAttribute**, enables C# +code to have the same semantics within PowerShell. ++The `hidden` keyword is useful for creating properties and methods within a +class that you do not necessarily want users of the class to see or readily be +able to edit. ++The `hidden` keyword has no effect on how you can view or make changes to +members of a class. Like all language keywords in PowerShell, `hidden` is not case-sensitive, and hidden members are still public. -Hidden, along with custom classes, was introduced in PowerShell 5.0. +The `hidden` keyword, along with custom classes, was introduced in Windows +PowerShell 5.0. ## EXAMPLE -The following example shows how to use the Hidden keyword in a class -definition. The Car class method, Drive, has a property, rides, that does not -need to be viewed or changed (it merely tallies the number of times that Drive -is called on the Car class, a metric that is not important to users of the -class; consider, for example, that when you are buying a car, you do not ask -the seller on how many drives the car has been taken. +The following example shows how to use the `hidden` keyword in a class +definition. The **Car** class method, **Drive**, has a property, **rides**, that +does not need to be viewed or changed as it merely tallies the number of times +that **Drive** is called on the **Car** class. That metric that is not important +to users of the class (consider, for example, that when you are buying a car, +you do not ask the seller on how many drives the car has been taken). -Because there is little need for users of the class to change this property, -we can hide the property from Get-Member and automatic completion results by -using the Hidden keyword. +Because there is little need for users of the class to change this property, we +can hide the property from `Get-Member` and automatic completion results by +using the `hidden` keyword. -Add the Hidden keyword by entering it on the same statement line as the +Add the `hidden` keyword by entering it on the same statement line as the property and its data type. Although the keyword can be in any order on this-line, starting the statement with the Hidden keyword makes it easier for you +line, starting the statement with the `hidden` keyword makes it easier for you later to identify all members that you have hidden. ```powershell class Car } ``` -Now, create a new instance of the Car class, and save it in a variable, -\$TestCar. +Now, create a new instance of the **Car** class, and save it in a variable, +`$TestCar`. ```powershell $TestCar = [Car]::new() ``` -After you create the new instance, pipe the contents of the $TestCar variable -to Get-Member. Observe that the rides property is not among the members listed -in the Get-Member command results. +After you create the new instance, pipe the contents of the `$TestCar` variable +to `Get-Member`. Observe that the **rides** property is not among the members +listed in the `Get-Member` command results. ```output PS C:\Windows\system32> $TestCar | Get-Member ModelYear Property string ModelYear {get;set;} ``` -Now, try running Get-Member again, but this time, add the -Force parameter. -Note that the results contain the hidden rides property, among other members +Now, try running `Get-Member` again, but this time, add the `-Force` parameter. +Note that the results contain the hidden **rides** property, among other members that are hidden by default. ```output |
| Microsoft.PowerShell.Core | About Language Modes (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Language_Modes.md | --- description: Explains language modes and their effect on PowerShell sessions. Locale: en-US Previously updated : 08/03/2021 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_language_modes?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Language Modes FullLanguage ``` On other session configurations, you can find the language mode indirectly by-finding the language mode of a session that is created by using the session +finding the language mode of a session that is created with the session configuration. +> [!NOTE] +> Session configurations are a feature of WSMan-based PowerShell remoting. They are used only when you +> use the `New-PSSession`, `Invoke-Command`, or `Enter-PSSession` cmdlets +> to connect to a remote Windows computer. The `Get-PSSessionConfiguration` +> cmdlet is only available on Windows computers. + ### Finding the language mode of a session You can find the language mode of a **FullLanguage** or **ConstrainedLanguage** |
| Microsoft.PowerShell.Core | About Pssession Details (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_PSSession_Details.md | --- description: Provides detailed information about PowerShell sessions and the role they play in remote commands. Locale: en-US Previously updated : 06/09/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pssession_details?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about PSSession Details and manage only the PSSessions that you created. ## Can I Connect to a PSSession From a Different Computer? -Beginning in Windows PowerShell 3.0, PSSessions are independent -of the sessions in which they were created. Active PSSessions +Beginning in Windows PowerShell 3.0, PSSessions on Windows computers are +independent of the sessions in which they were created. Active PSSessions are maintained on the computer at the remote or "server-side" of a connection. -You can use the `Disconnect-PSSession` cmdlet to disconnect -from a PSSession. The PSSession is disconnected from the +On a Windows computer, you can use the `Disconnect-PSSession` cmdlet to +disconnect from a PSSession. The PSSession is disconnected from the local session, but is maintained on the remote computer. Commands continue to run in the disconnected PSSession. You can close PowerShell and shut down the originating computer without interrupting the PSSession. Then, even hours later, you can use the `Get-PSSession` cmdlet to get the PSSession and the `Connect-PSSession` cmdlet to connect to the-PSSession from a new session on a different computer. +PSSession from a new session on a different Windows computer. For more information, see [about_Remote_Disconnected_Sessions](about_Remote_Disconnected_Sessions.md). |
| Microsoft.PowerShell.Core | About Pssessions (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_PSSessions.md | --- description: Describes PowerShell sessions (PSSessions) and explains how to establish a persistent connection to a remote computer. Locale: en-US Previously updated : 01/03/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pssessions?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about PSSessions You can also create a PSSession on the local computer and run commands in it. A local PSSession uses the PowerShell remoting infrastructure to create and maintain the PSSession. -Beginning in Windows PowerShell 3.0, PSSessions are independent of the -sessions in which they are created. Active PSSessions are maintained on the -remote computer (or the computer at the remote end or "server-side" of the -connection). As a result, you can disconnect from the PSSession and reconnect -to it at a later time from the same computer or from a different computer. +Beginning in Windows PowerShell 3.0, PSSessions on Windows are independent +of the sessions in which they are created. Active PSSessions are maintained +on the remote computer (or the computer at the remote end or "server-side" +of the connection). As a result, on Windows you can disconnect from a PSSession +on a remote Windows computer and reconnect to it at a later time from the +same computer or from a different Windows computer. This topic explains how to create, use, get, and delete PSSessions. For more advanced information, see Get-Help *-PSSession session - Remove-PSSession: Deletes the PSSessions in the current session +> [!NOTE] +> Disconnected sessions are only supported on Windows. The `Connect-PSSession`, +> `Disconnect-PSSession`, and `Receive-PSSession` cmdlets are only available +> on Windows. For more information about disconnected sessions, see +> [about_Remote_Disconnected_Session](about_Remote_Disconnected_Sessions.md) + ## For More Information For more information about PSSessions, see [about_PSSession_Details](about_PSSession_Details.md). |
| Microsoft.PowerShell.Core | About Providers (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Providers.md | --- description: Describes how PowerShell providers provide access to data and components that wouldn't otherwise be easily accessible at the command line. The data is presented in a consistent format that resembles a file system drive. Locale: en-US Previously updated : 03/27/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_providers?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Providers your session, type: Get-PSProvider ``` +> [!NOTE] +> The **Certificate**, **Registry**, and **WSMan** providers are only +> available on the Windows platform. + ## Installing and removing providers Providers are typically installed via PowerShell modules. Importing the module |
| Microsoft.PowerShell.Core | About Pwsh (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Pwsh.md | --- description: Explains how to use the `pwsh` command-line interface. Displays the command-line parameters and describes the syntax. Locale: en-US Previously updated : 01/18/2022 Last updated : 03/07/2022 no-loc: [-File, -f, -Command, -c, -ConfigurationName, -config, -CustomPipeName, -EncodedCommand, -e, -ec, -ExecutionPolicy, -ex, -ep, -InputFormat, -inp, -if, -Interactive, -i, -Login, -l, -MTA, -NoExit, -noe, -NoLogo, -nol, -NonInteractive, -noni, -NoProfile, -nop, -OutputFormat, -o, -of, -SettingsFile, -settings, -SSHServerMode, -sshs, -STA, -Version, -v, -WindowStyle, -w, -WorkingDirectory, -wd, -Help] online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pwsh?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 intended or supported for any other use. ### -STA Start PowerShell using a single-threaded apartment. This is the default. This-switch is only available on Windows. +switch is only available on the Windows platform. ### -Version | -v |
| Microsoft.PowerShell.Core | About Registry Provider (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Registry_Provider.md | --- description: Registry Locale: en-US Previously updated : 09/28/2021 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_registry_provider?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Registry Provider Provides access to the registry keys, entries, and values in PowerShell. ## Detailed description +> This information only applies to PowerShell running on Windows. + The PowerShell **Registry** provider lets you get, add, change, clear, and delete registry keys, entries, and values in PowerShell. |
| Microsoft.PowerShell.Core | About Remote Disconnected Sessions (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Remote_Disconnected_Sessions.md | --- description: Explains how to disconnect and reconnect to a PowerShell Session (PSSession). Locale: en-US Previously updated : 12/01/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_disconnected_sessions?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Remote Disconnected Sessions state is maintained and commands in the PSSession continue to run while the session is disconnected. The Disconnected Sessions feature is only available when the remote computer is-running PowerShell 3.0 or a later version. +a Windows computer running PowerShell 3.0 or a later version and the local +computer is running Windows. The Disconnected Sessions feature allows you to close the session in which a PSSession was created, and even close PowerShell, and shut down the computer, without disrupting commands running in the PSSession. Disconnected sessions are useful for running commands that take an extended time to complete, and provides the time and device flexibility that IT professionals require. -You can't disconnect from an interactive session that is started by using the +You can't disconnect from an interactive session that is started with the `Enter-PSSession` cmdlet. You can use disconnected sessions to manage PSSessions that were disconnected |
| Microsoft.PowerShell.Core | About Remote Output (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Remote_Output.md | --- description: Describes how to interpret and format the output of remote commands. Locale: en-US Previously updated : 12/01/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_output?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Remote Output in a streaming list. When objects are not formatted automatically, you can use the formatting cmdlets, such as Format-Table or Format-List, to format and display-selected properties. Or, you can use the Out-GridView cmdlet to display -the objects in a table. +selected properties. On a Windows computer, you can use the `Out-GridView` +cmdlet to display the objects in a table. Also, if you run a command on a remote computer that uses cmdlets that you do not have on your local computer, the objects that the command returns |
| Microsoft.PowerShell.Core | About Session Configuration Files (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Session_Configuration_Files.md | --- description: Describes session configuration files, which are used in a session configuration (also known as an endpoint) to define the environment of sessions that use the session configuration. Locale: en-US Previously updated : 01/03/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_session_configuration_files?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Session Configuration Files sessions that use the session configuration. ## Long description +> This information only applies to PowerShell running on Windows. + A "session configuration file" is a text file with a .pssc file name extension that contains a hash table of session configuration properties and values. You can use a session configuration file to set the properties of a session |
| Microsoft.PowerShell.Core | About Session Configurations (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Session_Configurations.md | --- description: Describes session configurations, which determine the users who can connect to the computer remotely and the commands they can run. Locale: en-US Previously updated : 12/09/2017 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_session_configurations?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Session Configurations New-PSSessionConfiguration cmdlet. For more information about session configuration files, see [about_Session_Configuration_Files](about_Session_Configuration_Files.md). -Session configurations are a feature of Web Services for Management -(WS-Management) based PowerShell remoting. They are used only when you use the -New-PSSession, Invoke-Command, or Enter-PSSession cmdlets to connect to a -remote computer. +Session configurations are a feature of WSMAN-based PowerShell remoting. They +are used only when you use the `New-PSSession`, `Invoke-Command`, or +`Enter-PSSession` cmdlets to connect to a remote Windows computer. -Note: To manage the session configurations, start PowerShell with the -"Run as administrator" option. +To manage the session configurations on a Windows computer, start +PowerShell with the **Run as administrator** option. About Session Configurations |
| Microsoft.PowerShell.Core | About Signing (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Signing.md | --- description: Explains how to sign scripts so that they comply with the PowerShell execution policies. Locale: en-US Previously updated : 01/21/2022 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Signing policies. ## Long description +> This information only applies to PowerShell running on Windows. + The Restricted execution policy does not permit any scripts to run. The **AllSigned** and **RemoteSigned** execution policies prevent PowerShell from running scripts that do not have a digital signature. |
| Microsoft.PowerShell.Security | About Certificate Provider (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Security/About/about_Certificate_Provider.md | --- description: Information about the Certificate provider. Locale: en-US Previously updated : 06/04/2020 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.security/about/about_certificate_provider?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Certificate Provider Provides access to X.509 certificate stores and certificates in PowerShell. ## Detailed description +> This information only applies to PowerShell running on Windows. + The PowerShell **Certificate** provider lets you get, add, change, clear, and delete certificates and certificate stores in PowerShell. |
| Microsoft.WSMan.Management | About Wsman Provider (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.WSMan.Management/About/about_WSMan_Provider.md | --- description: WSMan Locale: en-US Previously updated : 10/18/2018 Last updated : 03/07/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.wsman.management/about/about_wsman_provider?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about WSMan Provider information. ## Detailed description +> This information only applies to PowerShell running on Windows. + The **WSMan** provider for PowerShell lets you add, change, clear, and delete WS-Management configuration data on local or remote computers. |