diff --git a/reference/6/Microsoft.PowerShell.Management/Clear-Content.md b/reference/6/Microsoft.PowerShell.Management/Clear-Content.md index 28ab29e26758..12bc2f9c2eba 100644 --- a/reference/6/Microsoft.PowerShell.Management/Clear-Content.md +++ b/reference/6/Microsoft.PowerShell.Management/Clear-Content.md @@ -58,7 +58,7 @@ Using a filter to restrict the command to files with the .log file name extensio Type a user name, such as "User01" or "Domain01\User01", or enter a **PSCredential** object, such as one generated by the **Get-Credential** cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: String @@ -79,7 +79,7 @@ The default is the current user. Type a user name, such as "User01" or "Domain01\User01", or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -115,7 +115,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when retrieving the objects, rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when retrieving the objects, rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -167,7 +167,7 @@ Specifies the paths to the items from which content is deleted. Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell having Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell having PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] @@ -271,8 +271,8 @@ This cmdlet does not return any objects. For instance, `Clear-Content c:\mydir\*.txt`. If you include the parameter name, you can list the parameters in any order. - You can use **Clear-Content** with the Windows PowerShell FileSystem provider and with other providers that manipulate content. -To clear items that are not considered to be content, such as items managed by the Windows PowerShell Certificate or Registry providers, use Clear-Item. + You can use **Clear-Content** with the PowerShell FileSystem provider and with other providers that manipulate content. +To clear items that are not considered to be content, such as items managed by the PowerShell Certificate or Registry providers, use Clear-Item. The **Clear-Content** cmdlet is designed to work with the data exposed by any provider. To list the providers available in your session, type `Get-PsProvider`. diff --git a/reference/6/Microsoft.PowerShell.Management/Clear-Item.md b/reference/6/Microsoft.PowerShell.Management/Clear-Item.md index 0d089d6e8b55..cb78248812d9 100644 --- a/reference/6/Microsoft.PowerShell.Management/Clear-Item.md +++ b/reference/6/Microsoft.PowerShell.Management/Clear-Item.md @@ -30,7 +30,7 @@ Clear-Item -LiteralPath [-Force] [-Filter ] [-Include Clear-Item TestVar1 This command clears the value of the variable named TestVar1. The variable remains and is valid, but its value is set to null. -The variable name is prefixed with Variable: to indicate the Windows PowerShell Variable provider. +The variable name is prefixed with Variable: to indicate the PowerShell Variable provider. -The alternate commands show that, to get the same result, you can switch to the Windows PowerShell Variable: drive and then run the **Clear-Item** command. +The alternate commands show that, to get the same result, you can switch to the PowerShell Variable: drive and then run the **Clear-Item** command. ### Example 2: Clear all registry entries ``` @@ -69,7 +69,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -105,7 +105,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -256,9 +256,9 @@ You can pipe a path string to this cmdlet. This cmdlet does not generate any output. ## NOTES -* The **Clear-Item** cmdlet is supported only by several Windows PowerShell providers, including the Alias, Environment, Function, Registry, and Variable providers. As such, you can use **Clear-Item** to delete the content of items in the provider namespaces. +* The **Clear-Item** cmdlet is supported only by several PowerShell providers, including the Alias, Environment, Function, Registry, and Variable providers. As such, you can use **Clear-Item** to delete the content of items in the provider namespaces. - You cannot use **Clear-Item** to delete the contents of a file, because the Windows PowerShell FileSystem provider does not support this cmdlet. + You cannot use **Clear-Item** to delete the contents of a file, because the PowerShell FileSystem provider does not support this cmdlet. To clear files, use the **Clear-Content**. You can also refer to **Clear-Item** by its built-in alias, cli. diff --git a/reference/6/Microsoft.PowerShell.Management/Clear-ItemProperty.md b/reference/6/Microsoft.PowerShell.Management/Clear-ItemProperty.md index 73c9060da06c..166503d3f03f 100644 --- a/reference/6/Microsoft.PowerShell.Management/Clear-ItemProperty.md +++ b/reference/6/Microsoft.PowerShell.Management/Clear-ItemProperty.md @@ -56,7 +56,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -92,7 +92,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -146,7 +146,7 @@ Specifies the path to the property being cleared. Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Convert-Path.md b/reference/6/Microsoft.PowerShell.Management/Convert-Path.md index 06dadba20241..8a2a25abd89b 100644 --- a/reference/6/Microsoft.PowerShell.Management/Convert-Path.md +++ b/reference/6/Microsoft.PowerShell.Management/Convert-Path.md @@ -11,7 +11,7 @@ title: Convert-Path # Convert-Path ## SYNOPSIS -Converts a path from a Windows PowerShell path to a Windows PowerShell provider path. +Converts a path from a PowerShell path to a PowerShell provider path. ## SYNTAX @@ -26,7 +26,7 @@ Convert-Path -LiteralPath [-UseTransaction] [] ``` ## DESCRIPTION -The **Convert-Path** cmdlet converts a path from a Windows PowerShell path to a Windows PowerShell provider path. +The **Convert-Path** cmdlet converts a path from a PowerShell path to a PowerShell provider path. ## EXAMPLES @@ -42,7 +42,7 @@ This command converts the current working directory, which is represented by a d PS C:\> Convert-Path HKLM:\Software\Microsoft ``` -This command converts the Windows PowerShell provider path to a standard registry path. +This command converts the PowerShell provider path to a standard registry path. ### Example 3: Convert a path to a string ``` @@ -59,7 +59,7 @@ Specifies, as a string array, the path to be converted. The value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] @@ -74,7 +74,7 @@ Accept wildcard characters: False ``` ### -Path -Specifies the Windows PowerShell path to be converted. +Specifies the PowerShell path to be converted. ```yaml Type: String[] @@ -121,7 +121,7 @@ You can pipe a path, but not a literal path, to this cmdlet. This cmdlet returns a string that contains the converted path. ## NOTES -* The cmdlets that contain the Path noun manipulate path names and return the names in a concise format that all Windows PowerShell providers can interpret. They are designed for use in programs and scripts where you want to display all or part of a path name in a particular format. Use them like you would use Dirname, Normpath, Realpath, Join, or other path manipulators. +* The cmdlets that contain the Path noun manipulate path names and return the names in a concise format that all PowerShell providers can interpret. They are designed for use in programs and scripts where you want to display all or part of a path name in a particular format. Use them like you would use Dirname, Normpath, Realpath, Join, or other path manipulators. You can use the path cmdlets with several providers, including the FileSystem, Registry, and Certificate providers. diff --git a/reference/6/Microsoft.PowerShell.Management/Copy-Item.md b/reference/6/Microsoft.PowerShell.Management/Copy-Item.md index cd5475d44581..bc0afa8c20ff 100644 --- a/reference/6/Microsoft.PowerShell.Management/Copy-Item.md +++ b/reference/6/Microsoft.PowerShell.Management/Copy-Item.md @@ -34,7 +34,7 @@ The **Copy-Item** cmdlet copies an item from one location to another location in For instance, it can copy a file to a folder, but it cannot copy a file to a certificate drive. This cmdlet does not cut or delete the items being copied. -The particular items that the cmdlet can copy depend on the Windows PowerShell provider that exposes the item. +The particular items that the cmdlet can copy depend on the PowerShell provider that exposes the item. For instance, it can copy files and directories in a file system drive and registry keys and entries in the registry drive. This cmdlet can copy and rename items in the same command. @@ -180,7 +180,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you are prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -230,7 +230,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than have Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than have PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -279,7 +279,7 @@ Specifies a path to the item. The value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Copy-ItemProperty.md b/reference/6/Microsoft.PowerShell.Management/Copy-ItemProperty.md index 6ee06049c0f2..f7101085be4b 100644 --- a/reference/6/Microsoft.PowerShell.Management/Copy-ItemProperty.md +++ b/reference/6/Microsoft.PowerShell.Management/Copy-ItemProperty.md @@ -51,7 +51,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -100,7 +100,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -149,7 +149,7 @@ Specifies a path to the item property. The value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Get-ChildItem.md b/reference/6/Microsoft.PowerShell.Management/Get-ChildItem.md index 241a8b3d4b7f..156a181dfd47 100644 --- a/reference/6/Microsoft.PowerShell.Management/Get-ChildItem.md +++ b/reference/6/Microsoft.PowerShell.Management/Get-ChildItem.md @@ -37,7 +37,7 @@ The `Get-ChildItem` cmdlet gets the items in one or more specified locations. If the item is a container, it gets the items inside the container, known as child items. You can use the `-Recurse` parameter to get items in all child containers and use the `-Depth` parameter to limit the number of levels to recurse. -A location can be a file system location, such as a directory, or a location exposed by a different Windows PowerShell provider, such as a registry hive or a certificate store. +A location can be a file system location, such as a directory, or a location exposed by a different PowerShell provider, such as a registry hive or a certificate store. ## Examples @@ -61,7 +61,7 @@ Get-ChildItem -Path *.txt -Recurse -Force ``` This command gets all of the .txt files in the current directory and its subdirectories. -The `-Recurse` parameter directs Windows PowerShell to get objects recursively, and it indicates that the subject of the command is the specified directory and its contents. +The `-Recurse` parameter directs PowerShell to get objects recursively, and it indicates that the subject of the command is the specified directory and its contents. The `-Force` parameter adds hidden files to the display. To use the `-Recurse` parameter on Windows PowerShell 2.0 and earlier versions of Windows PowerShell, the value use the `-Path` parameter must be a container. @@ -101,7 +101,7 @@ Import-Module Microsoft.PowerShell.Security Get-ChildItem -Path Cert:\* -Recurse -CodeSigningCert ``` -This command gets all of the certificates in the Windows PowerShell Cert: drive that have code-signing authority. +This command gets all of the certificates in the PowerShell Cert: drive that have code-signing authority. The first command imports the Microsoft.PowerShell.Security module into the session. This module includes the Certificate provider that creates the Cert: drive. @@ -196,7 +196,7 @@ Accept wildcard characters: False ### -Depth -This parameter, added in Powershell 5.0 enables you to control the depth of recursion. +This parameter, added in Windows Powershell 5.0 enables you to control the depth of recursion. You use both the `-Recurse` and the `-Depth` parameter to limit the recursion. ```yaml @@ -275,7 +275,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the `-Path` parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when retrieving the objects, rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when retrieving the objects, rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -373,7 +373,7 @@ Specifies a path to one or more locations. Unlike the `-Path` parameter, the value of the `-LiteralPath` parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Get-Content.md b/reference/6/Microsoft.PowerShell.Management/Get-Content.md index b9a5db4d7843..da229a8dbbf1 100644 --- a/reference/6/Microsoft.PowerShell.Management/Get-Content.md +++ b/reference/6/Microsoft.PowerShell.Management/Get-Content.md @@ -81,7 +81,7 @@ The command uses the *Tail* parameter and the *Head* alias of the *TotalCount* p ## PARAMETERS ### -Encoding -This parameter is not supported by any providers that are installed with Windows PowerShell. +This parameter is not supported by any providers that are installed with PowerShell. ```yaml Type: FileSystemCmdletProviderEncoding @@ -97,7 +97,7 @@ Accept wildcard characters: False ``` ### -Delimiter -This parameter is not supported by any providers that are installed with Windows PowerShell. +This parameter is not supported by any providers that are installed with PowerShell. ```yaml Type: String @@ -127,7 +127,7 @@ Accept wildcard characters: False ``` ### -Raw -This parameter is not supported by any providers that are installed with Windows PowerShell. +This parameter is not supported by any providers that are installed with PowerShell. ```yaml Type: SwitchParameter @@ -142,7 +142,7 @@ Accept wildcard characters: False ``` ### -Wait -This parameter is not supported by any providers that are installed with Windows PowerShell. +This parameter is not supported by any providers that are installed with PowerShell. ```yaml Type: SwitchParameter @@ -157,7 +157,7 @@ Accept wildcard characters: False ``` ### -Stream -This parameter is not supported by any providers that are installed with Windows PowerShell. +This parameter is not supported by any providers that are installed with PowerShell. ```yaml Type: String @@ -197,7 +197,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers that are installed with Windows PowerShell. +This parameter is not supported by any providers that are installed with PowerShell. ```yaml Type: PSCredential @@ -233,7 +233,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects, rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects, rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -270,7 +270,7 @@ Specifies the path to an item. Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Get-Item.md b/reference/6/Microsoft.PowerShell.Management/Get-Item.md index d675dc5e7c6b..402cae67e238 100644 --- a/reference/6/Microsoft.PowerShell.Management/Get-Item.md +++ b/reference/6/Microsoft.PowerShell.Management/Get-Item.md @@ -31,7 +31,7 @@ Get-Item -LiteralPath [-Filter ] [-Include ] [-Excl The **Get-Item** cmdlet gets the item at the specified location. It does not get the contents of the item at the location unless you use a wildcard character (*) to request all the contents of the item. -This cmdlet is used by Windows PowerShell providers to navigate through different types of data stores. +This cmdlet is used by PowerShell providers to navigate through different types of data stores. ## EXAMPLES @@ -84,7 +84,7 @@ PS C:\> Get-Item C:\* This command gets the items in the C: drive. The wildcard character (*) represents all the items in the container, not just the container. -In Windows PowerShell, use a single asterisk (*) to get contents, instead of the traditional *.*. +In PowerShell, use a single asterisk (*) to get contents, instead of the traditional *.*. The format is interpreted literally, so *.* would not retrieve directories or file names without a dot. ### Example 5: Get a property in the specified directory @@ -102,7 +102,7 @@ PS C:\> Get-Item hklm:\software\microsoft\powershell\1\shellids\microsoft.powers ``` This command shows the contents of the Microsoft.PowerShell registry key. -You can use this cmdlet with the Windows PowerShell Registry provider to get registry keys and subkeys, but you must use the **Get-ItemProperty** cmdlet to get the registry values and data. +You can use this cmdlet with the PowerShell Registry provider to get registry keys and subkeys, but you must use the **Get-ItemProperty** cmdlet to get the registry values and data. ### Example 7: Get items in a directory that have an exclusion ``` @@ -115,7 +115,7 @@ This command works only when the path includes a wildcard character (*) to speci ## PARAMETERS ### -Stream -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: String[] @@ -136,7 +136,7 @@ The default is the current user. Type a user-name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -174,7 +174,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects, rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects, rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -231,7 +231,7 @@ Specifies a path to the item. Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Get-ItemProperty.md b/reference/6/Microsoft.PowerShell.Management/Get-ItemProperty.md index 69feb71bf2da..8edadcf960fc 100644 --- a/reference/6/Microsoft.PowerShell.Management/Get-ItemProperty.md +++ b/reference/6/Microsoft.PowerShell.Management/Get-ItemProperty.md @@ -55,8 +55,8 @@ PS C:\> Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion ``` This command displays the value name and data of each of the registry entries contained in the CurrentVersion registry subkey. -Note that the command requires that there is a Windows PowerShell drive named HKLM: that is mapped to the HKEY_LOCAL_MACHINE hive of the registry. -A drive with that name and mapping is available in Windows PowerShell by default. +Note that the command requires that there is a PowerShell drive named HKLM: that is mapped to the HKEY_LOCAL_MACHINE hive of the registry. +A drive with that name and mapping is available in PowerShell by default. Alternatively, the path to this registry subkey can be specified by using the following alternative path that begins with the provider name followed by two colons: Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion. @@ -69,7 +69,7 @@ PS C:\> Get-ItemProperty -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion - This command gets the value name and data of the ProgramFilesDir registry entry in the CurrentVersion registry subkey. The command uses the *Path* parameter to specify the subkey and the Name parameter to specify the value name of the entry. -The command uses a back tick or grave accent (\`), the Windows PowerShell continuation character, to continue the command on the second line. +The command uses a back tick or grave accent (\`), the PowerShell continuation character, to continue the command on the second line. ### Example 5: Get the value names and data of registry entries in a registry key ``` @@ -115,7 +115,7 @@ ExecutionPolicy : RemoteSigned This example shows how to format the output of a **Get-ItemProperty** command in a list to make it easy to see the registry values and data and to make it easy to interpret the results. The first command uses the **Get-ItemProperty** cmdlet to get the registry entries in the Microsoft.PowerShell subkey. -This subkey stores options for the default shell for Windows PowerShell. +This subkey stores options for the default shell for PowerShell. The results are shown in the following sample output. The output shows that there are two registry entries, Path and ExecutionPolicy. @@ -127,7 +127,7 @@ The **Format-List** command uses the Property parameter with a value of * (all) The results are shown in the following sample output. The resulting display shows the Path and ExecutionPolicy registry entries, along with several less familiar properties of the registry key object. -The other properties, prefixed with PS, are properties of Windows PowerShell custom objects, such as the objects that represent the registry keys. +The other properties, prefixed with PS, are properties of PowerShell custom objects, such as the objects that represent the registry keys. ## PARAMETERS @@ -138,7 +138,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -172,7 +172,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -206,7 +206,7 @@ Specifies a path to the item property. The value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Get-ItemPropertyValue.md b/reference/6/Microsoft.PowerShell.Management/Get-ItemPropertyValue.md index 739f6e285fe7..ca0fe058671d 100644 --- a/reference/6/Microsoft.PowerShell.Management/Get-ItemPropertyValue.md +++ b/reference/6/Microsoft.PowerShell.Management/Get-ItemPropertyValue.md @@ -84,7 +84,7 @@ Specifies a user account that has permission to perform this action. The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you are prompted for a password. -This parameter is not supported by any providers that are installed with Windows PowerShell. +This parameter is not supported by any providers that are installed with PowerShell. ```yaml Type: PSCredential @@ -117,7 +117,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcard characters, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String diff --git a/reference/6/Microsoft.PowerShell.Management/Get-Location.md b/reference/6/Microsoft.PowerShell.Management/Get-Location.md index fc084feb0d7c..ba12c2040ac8 100644 --- a/reference/6/Microsoft.PowerShell.Management/Get-Location.md +++ b/reference/6/Microsoft.PowerShell.Management/Get-Location.md @@ -28,10 +28,10 @@ Get-Location [-Stack] [-StackName ] [-UseTransaction] [ Set-Location C:\Windows -The second command uses the **Set-Location** cmdlet to change the location to the HKLM:\Software\Microsoft registry key. When you change to a location in the HKLM: drive, Windows PowerShell retains your location in the C: drive. +The second command uses the **Set-Location** cmdlet to change the location to the HKLM:\Software\Microsoft registry key. When you change to a location in the HKLM: drive, PowerShell retains your location in the C: drive. PS C:\> PS C:\WINDOWS> Set-Location HKLM:\Software\Microsoft PS HKLM:\Software\Microsoft> @@ -76,12 +76,12 @@ Path C:\WINDOWS -The fifth command uses the **Set-Location** cmdlet to return to the C: drive. Even though the command does not specify a subdirectory, Windows PowerShell returns you to the saved location. +The fifth command uses the **Set-Location** cmdlet to return to the C: drive. Even though the command does not specify a subdirectory, PowerShell returns you to the saved location. PS C:\> PS HKCU:\Control Panel\Input Method> Set-Location C: PS C:\WINDOWS> -The sixth command uses the **Get-Location** cmdlet to find the current location in the drives supported by the Windows PowerShell registry provider. **Get-Location** returns the location of the most recently accessed registry drive, HKCU. +The sixth command uses the **Get-Location** cmdlet to find the current location in the drives supported by the PowerShell registry provider. **Get-Location** returns the location of the most recently accessed registry drive, HKCU. PS C:\> PS C:\WINDOWS> Get-Location -PSProvider registry @@ -104,7 +104,7 @@ Path HKLM:\Software\Microsoft ``` -This example demonstrates the use of **Get-Location** to display your current location in different Windows PowerShell drives. +This example demonstrates the use of **Get-Location** to display your current location in different PowerShell drives. ### Example 3: ``` @@ -144,17 +144,17 @@ C:\WINDOWS\system32 This example shows how to use the *Stack* and *StackName* parameters of **Get-Location** to list the locations in the current location stack and alternate location stacks. For more information about location stacks, see the Notes. -### Example 4: Customize the Windows PowerShell prompt +### Example 4: Customize the PowerShell prompt ``` PS C:\> function prompt { 'PowerShell: ' + (get-location) + '> '} PowerShell: C:\WINDOWS> ``` -This example shows how to customize the Windows PowerShell prompt. +This example shows how to customize the PowerShell prompt. The function that defines the prompt includes a **Get-Location** command, which is run whenever the prompt appears in the console. -The format of the default Windows PowerShell prompt is defined by a special function named prompt. +The format of the default PowerShell prompt is defined by a special function named prompt. You can change the prompt in your console by creating a new function named prompt. To see the current prompt function, type the following command: `Get-Content Function:prompt` @@ -169,7 +169,7 @@ The prompt ends with the string "\> ". ## PARAMETERS ### -PSDrive -Specifies the current location in the specified Windows PowerShell drive that this cmdlet gets in the operation. +Specifies the current location in the specified PowerShell drive that this cmdlet gets in the operation. For instance, if you are in the Certificate: drive, you can use this parameter to find your current location in the C: drive. @@ -186,11 +186,11 @@ Accept wildcard characters: False ``` ### -PSProvider -Specifies the current location in the drive supported by the Windows PowerShell provider that this cmdlet gets in the operation. +Specifies the current location in the drive supported by the PowerShell provider that this cmdlet gets in the operation. If the specified provider supports more than one drive, this cmdlet returns the location on the most recently accessed drive. -For example, if you are in the C: drive, you can use this parameter to find your current location in the drives of the Windows PowerShellRegistry provider. +For example, if you are in the C: drive, you can use this parameter to find your current location in the drives of the PowerShellRegistry provider. ```yaml Type: String[] @@ -286,12 +286,12 @@ If no parameters are specified, this cmdlet returns the **PathInfo** object for A stack is a last-in, first-out list in which only the most recently added item is accessible. You add items to a stack in the order that you use them, and then retrieve them for use in the reverse order. -Windows PowerShell lets you store provider locations in location stacks. -Windows PowerShell creates an unnamed default location stack and you can create multiple named location stacks. -If you do not specify a stack name, Windows PowerShell uses the current location stack. +PowerShell lets you store provider locations in location stacks. +PowerShell creates an unnamed default location stack and you can create multiple named location stacks. +If you do not specify a stack name, PowerShell uses the current location stack. By default, the unnamed default location is the current location stack, but you can use the **Set-Location** cmdlet to change the current location stack. - To manage location stacks, use the Windows PowerShellLocation cmdlets, as follows. + To manage location stacks, use the PowerShellLocation cmdlets, as follows. - To add a location to a location stack, use the Push-Location cmdlet. diff --git a/reference/6/Microsoft.PowerShell.Management/Get-PSDrive.md b/reference/6/Microsoft.PowerShell.Management/Get-PSDrive.md index 5d99abb671f2..0efb354287f4 100644 --- a/reference/6/Microsoft.PowerShell.Management/Get-PSDrive.md +++ b/reference/6/Microsoft.PowerShell.Management/Get-PSDrive.md @@ -32,15 +32,15 @@ You can get a particular drive or all drives in the session. This cmdlet gets the following types of drives: - Windows logical drives on the computer, including drives mapped to network shares. -- Drives exposed by Windows PowerShell providers (such as the Certificate:, Function:, and Alias: drives) and the HKLM: and HKCU: drives that are exposed by the Windows PowerShell Registry provider. +- Drives exposed by PowerShell providers (such as the Certificate:, Function:, and Alias: drives) and the HKLM: and HKCU: drives that are exposed by the PowerShell Registry provider. - Session-specified temporary drives and persistent mapped network drives that you create by using the New-PSDrive cmdlet. Beginning in Windows PowerShell 3.0, the *Persist* parameter of the **New-PSDrive** cmdlet can create mapped network drives that are saved on the local computer and are available in other sessions. For more information, see New-PSDrive. -Also, beginning in Windows PowerShell 3.0, when an external drive is connected to the computer, Windows PowerShell automatically adds a PSDrive to the file system that represents the new drive. -You do not need to restart Windows PowerShell. -Similarly, when an external drive is disconnected from the computer, Windows PowerShell automatically deletes the PSDrive that represents the removed drive. +Also, beginning in Windows PowerShell 3.0, when an external drive is connected to the computer, PowerShell automatically adds a PSDrive to the file system that represents the new drive. +You do not need to restart PowerShell. +Similarly, when an external drive is disconnected from the computer, PowerShell automatically deletes the PSDrive that represents the removed drive. ## EXAMPLES @@ -63,7 +63,7 @@ Variable Variable This command gets the drives in the current session. -The output shows the hard drive (C:), CD-ROM drive (D:), and the drives exposed by the Windows PowerShell providers (Alias:, Cert:, Env:, Function:, HKCU:, HKLM:, and Variable:). +The output shows the hard drive (C:), CD-ROM drive (D:), and the drives exposed by the PowerShell providers (Alias:, Cert:, Env:, Function:, HKCU:, HKLM:, and Variable:). ### Example 2: Get a drive on the computer ``` @@ -77,7 +77,7 @@ D 1211.06 123642.32 FileSystem D:\ This command gets the D: drive on the computer. Note that the drive letter in the command is not followed by a colon. -### Example 3: Get all the drives that are supported by the Windows PowerShell file system provider +### Example 3: Get all the drives that are supported by the PowerShell file system provider ``` PS C:\> Get-PSDrive -PSProvider FileSystem Name Used (GB) Free (GB) Provider Root @@ -88,10 +88,10 @@ D 1211.06 123642.32 FileSystem D:\ G 202.06 710.91 FileSystem \\Music\GratefulDead ``` -This command gets all of the drives that are supported by the Windows PowerShell FileSystem provider. +This command gets all of the drives that are supported by the PowerShell FileSystem provider. This includes fixed drives, logical partitions, mapped network drives, and temporary drives that you create by using the New-PSDrive cmdlet. -### Example 4: Check to see if a drive is in use as a Windows PowerShell drive name +### Example 4: Check to see if a drive is in use as a PowerShell drive name ```powershell if (Get-PSDrive X -ErrorAction SilentlyContinue) { Write-Host 'The X: drive is already in use.' @@ -100,7 +100,7 @@ if (Get-PSDrive X -ErrorAction SilentlyContinue) { } ``` -This command checks to see whether the X drive is already in use as a Windows PowerShell drive name. +This command checks to see whether the X drive is already in use as a PowerShell drive name. If it is not, the command uses the `New-PSDrive` cmdlet to create a temporary drive that is mapped to the HKLM:\SOFTWARE registry key. ### Example 5: Compare the types of files system drives @@ -147,7 +147,7 @@ G: \\Music\GratefulDead Connected OK ``` This example compares the types of file system drives that are displayed by **Get-PSDrive** to those displayed by using other methods. -This example demonstrates different ways to display drives in Windows PowerShell, and it shows that session-specific drives created by using the New-PSDrive cmdlet are accessible only in Windows PowerShell. +This example demonstrates different ways to display drives in PowerShell, and it shows that session-specific drives created by using the New-PSDrive cmdlet are accessible only in PowerShell. The first command uses **Get-PSDrive** to get all of the file system drives in the session. This includes the fixed drives (C: and D:), a mapped network drive (G:) that was created by using the *Persist* parameter of **New-PSDrive**, and a PowerShell drive (T:) that was created by using **New-PSDrive** without the *Persist* parameter. @@ -173,7 +173,7 @@ Specifies the name of the drive. The value of *LiteralName* is used exactly as it is typed. No characters are interpreted as wildcards. If the name includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] @@ -204,7 +204,7 @@ Accept wildcard characters: False ``` ### -PSProvider -Specifies, as a string array, the Windows PowerShell provider. +Specifies, as a string array, the PowerShell provider. This cmdlet gets only the drives supported by this provider. Type the name of a provider, such as FileSystem, Registry, or Certificate. diff --git a/reference/6/Microsoft.PowerShell.Management/Get-PSProvider.md b/reference/6/Microsoft.PowerShell.Management/Get-PSProvider.md index c718e2f1b645..00832310709b 100644 --- a/reference/6/Microsoft.PowerShell.Management/Get-PSProvider.md +++ b/reference/6/Microsoft.PowerShell.Management/Get-PSProvider.md @@ -11,7 +11,7 @@ title: Get-PSProvider # Get-PSProvider ## SYNOPSIS -Gets information about the specified Windows PowerShell provider. +Gets information about the specified PowerShell provider. ## SYNTAX @@ -20,11 +20,11 @@ Get-PSProvider [[-PSProvider] ] [] ``` ## DESCRIPTION -The **Get-PSProvider** cmdlet gets the Windows PowerShell providers in the current session. +The **Get-PSProvider** cmdlet gets the PowerShell providers in the current session. You can get a particular drive or all drives in the session. -Windows PowerShell providers let you access a variety of data stores as though they were file system drives. -For information about Windows PowerShell providers, see about_Providers. +PowerShell providers let you access a variety of data stores as though they were file system drives. +For information about PowerShell providers, see about_Providers. ## EXAMPLES @@ -33,14 +33,14 @@ For information about Windows PowerShell providers, see about_Providers. PS C:\> Get-PSProvider ``` -This command displays a list of all available Windows PowerShell providers. +This command displays a list of all available PowerShell providers. -### Example 2: Display a list of all Windows PowerShell providers that begin with specified letters +### Example 2: Display a list of all PowerShell providers that begin with specified letters ``` PS C:\> Get-PSProvider f*, r* | Format-List ``` -This command displays a list of all Windows PowerShell providers with names that begin with the letter f or r. +This command displays a list of all PowerShell providers with names that begin with the letter f or r. ### Example 3: Find snap-ins or module that added providers to your session ``` @@ -65,8 +65,8 @@ Name Capabilities Drives Certificate ShouldProcess {cert} ``` -These commands find the Windows PowerShell snap-ins or modules that added providers to your session. -All Windows PowerShell elements, including providers, originate in a snap-in or in a module. +These commands find the PowerShell snap-ins or modules that added providers to your session. +All PowerShell elements, including providers, originate in a snap-in or in a module. These commands use the PSSnapin and Module properties of the **ProviderInfo** object that **Get-PSProvider** returns. The values of these properties contain the name of the snap-in or module that adds the provider. @@ -93,7 +93,7 @@ The Home property value is optional, but for the FileSystem provider, it is defi ## PARAMETERS ### -PSProvider -Specifies the name or names of the Windows PowerShell providers about which this cmdlet gets information. +Specifies the name or names of the PowerShell providers about which this cmdlet gets information. ```yaml Type: String[] @@ -119,7 +119,7 @@ You can pipe one or more provider name strings to this cmdlet. ## OUTPUTS ### System.Management.Automation.ProviderInfo -This cmdlet returns objects that represent the Windows PowerShell providers in the session. +This cmdlet returns objects that represent the PowerShell providers in the session. ## NOTES diff --git a/reference/6/Microsoft.PowerShell.Management/Get-Process.md b/reference/6/Microsoft.PowerShell.Management/Get-Process.md index e3a843eca747..5eb376d96f63 100644 --- a/reference/6/Microsoft.PowerShell.Management/Get-Process.md +++ b/reference/6/Microsoft.PowerShell.Management/Get-Process.md @@ -101,7 +101,7 @@ The first command gets all the processes on the computer and then stores them in The second command uses the *InputObject* parameter to pass the process objects that are stored in the $A variable to the **Get-Process** cmdlet. The pipeline operator passes the objects to the **Format-Table** cmdlet, which formats the processes by using the Priority view. -The Priority view, and other views, are defined in the PS1XML format files in the Windows PowerShell home directory ($pshome). +The Priority view, and other views, are defined in the PS1XML format files in the PowerShell home directory ($pshome). ### Example 5: Add a property to the standard Get-Process output display ```powershell @@ -136,7 +136,7 @@ ProductVersion FileVersion FileName This command uses the *FileVersionInfo* parameter to get the version information for the PowerShell.exe file that is the main module for the PowerShell process. -To run this command with processes that you do not own on Windows Vista and later versions of Windows, you must open Windows PowerShell with the Run as administrator option. +To run this command with processes that you do not own on Windows Vista and later versions of Windows, you must open PowerShell with the Run as administrator option. ### Example 7: Get modules loaded with the specified process ``` @@ -146,7 +146,7 @@ PS C:\> Get-Process SQL* -Module This command uses the *Module* parameter to get the modules that have been loaded by the process. This command gets the modules for the processes that have names that begin with SQL. -To run this command on Windows Vista and later versions of Windows with processes that you do not own, you must start Windows PowerShell with the Run as administrator option. +To run this command on Windows Vista and later versions of Windows with processes that you do not own, you must start PowerShell with the Run as administrator option. ### Example 8: Find the owner of a process ```powershell @@ -200,7 +200,7 @@ To view all of the properties, pipe the results of a **Get-Process** command to ### -FileVersionInfo Indicates that this cmdlet gets the file version information for the program that runs in the process. -On Windows Vista and later versions of Windows, you must open Windows PowerShell with the Run as administrator option to use this parameter on processes that you do not own. +On Windows Vista and later versions of Windows, you must open PowerShell with the Run as administrator option to use this parameter on processes that you do not own. To get file version information for a process on a remote computer, use the Invoke-Command cmdlet. @@ -271,7 +271,7 @@ Accept wildcard characters: False ### -Module Indicates that this cmdlet gets the modules that have been loaded by the processes. -On Windows Vista and later versions of Windows, you must open Windows PowerShell with the Run as administrator option to use this parameter on processes that you do not own. +On Windows Vista and later versions of Windows, you must open PowerShell with the Run as administrator option to use this parameter on processes that you do not own. To get the modules that have been loaded by a process on a remote computer, use the **Invoke-Command** cmdlet. @@ -327,8 +327,8 @@ If you use the *Module* parameter, without the *FileVersionInfo* parameter, it r ## NOTES * You can also refer to this cmdlet by its built-in aliases, ps and gps. For more information, see about_Aliases. -* On computers that are running a 64-bit version of Windows, the 64-bit version of Windows PowerShell gets only 64-bit process modules and the 32-bit version of Windows PowerShell gets only 32-bit process modules. -* You can use the properties and methods of the Windows Management Instrumentation (WMI) Win32_Process object in Windows PowerShell. For information, see Get-WmiObject and the WMI SDK. +* On computers that are running a 64-bit version of Windows, the 64-bit version of PowerShell gets only 64-bit process modules and the 32-bit version of PowerShell gets only 32-bit process modules. +* You can use the properties and methods of the Windows Management Instrumentation (WMI) Win32_Process object in PowerShell. For information, see Get-WmiObject and the WMI SDK. * The default display of a process is a table that includes the following columns. For a description of all of the properties of process objects, see [Process Properties](https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.process#Properties) in the MSDN library. - Handles: The number of handles that the process has opened. diff --git a/reference/6/Microsoft.PowerShell.Management/Invoke-Item.md b/reference/6/Microsoft.PowerShell.Management/Invoke-Item.md index 7002852b7093..9d0a3f4bb347 100644 --- a/reference/6/Microsoft.PowerShell.Management/Invoke-Item.md +++ b/reference/6/Microsoft.PowerShell.Management/Invoke-Item.md @@ -30,7 +30,7 @@ Invoke-Item -LiteralPath [-Filter ] [-Include ] [-E ## DESCRIPTION The **Invoke-Item** cmdlet performs the default action on the specified item. For example, it runs an executable file or opens a document file in the application associated with the document file type. -The default action depends on the type of item and is determined by the Windows PowerShell provider that provides access to the data. +The default action depends on the type of item and is determined by the PowerShell provider that provides access to the data. ## EXAMPLES @@ -60,7 +60,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -96,7 +96,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when retrieving the objects rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when retrieving the objects rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -133,7 +133,7 @@ Specifies a path to the item. Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Join-Path.md b/reference/6/Microsoft.PowerShell.Management/Join-Path.md index 5603dd68e91f..ae2caf69ee89 100644 --- a/reference/6/Microsoft.PowerShell.Management/Join-Path.md +++ b/reference/6/Microsoft.PowerShell.Management/Join-Path.md @@ -63,7 +63,7 @@ This command displays the files and folders that are referenced by joining the C It displays the same files and folders as `Get-ChildItem`, but it displays the fully qualified path to each item. In this command, the `Path` and `ChildPath` optional parameter names are omitted. -### Example 4: Use Join-Path with the Windows PowerShell registry provider +### Example 4: Use Join-Path with the PowerShell registry provider ```powershell PS HKLM:\> Join-Path -Path System -ChildPath *ControlSet* -Resolve @@ -107,12 +107,12 @@ C:\Subdir D:\Subdir ``` -This command combines the roots of each Windows PowerShell file system drive in the console with the Subdir child path. +This command combines the roots of each PowerShell file system drive in the console with the Subdir child path. -The command uses the `Get-PSDrive` cmdlet to get the Windows PowerShell drives supported by the FileSystem provider. +The command uses the `Get-PSDrive` cmdlet to get the PowerShell drives supported by the FileSystem provider. The `ForEach-Object` statement selects only the Root property of the `PSDriveInfo` objects and combines it with the specified child path. -The output shows that the Windows PowerShell drives on the computer included a drive mapped to the C:\Program Files directory. +The output shows that the PowerShell drives on the computer included a drive mapped to the C:\Program Files directory. ### Example 7: Combine an indefinite number of paths @@ -175,7 +175,7 @@ Type a user name, such as User01 or Domain01\User01. Or, enter a `PSCredential` object, such as one generated by the `Get-Credential` cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -246,7 +246,7 @@ This cmdlet returns a string that contains the resulting path. ## NOTES -The cmdlets that contain the Path noun (the Path cmdlets) manipulate path names and return the names in a concise format that all Windows PowerShell providers can interpret. They are designed for use in programs and scripts where you want to display all or part of a path name in a particular format. Use them like you would use Dirname, Normpath, Realpath, Join, or other path manipulators. +The cmdlets that contain the Path noun (the Path cmdlets) manipulate path names and return the names in a concise format that all PowerShell providers can interpret. They are designed for use in programs and scripts where you want to display all or part of a path name in a particular format. Use them like you would use Dirname, Normpath, Realpath, Join, or other path manipulators. You can use the path cmdlets with several providers, including the `FileSystem`, `Registry`, and `Certificate` providers. diff --git a/reference/6/Microsoft.PowerShell.Management/Microsoft.PowerShell.Management.md b/reference/6/Microsoft.PowerShell.Management/Microsoft.PowerShell.Management.md index 12d877e9c784..6385a913f809 100644 --- a/reference/6/Microsoft.PowerShell.Management/Microsoft.PowerShell.Management.md +++ b/reference/6/Microsoft.PowerShell.Management/Microsoft.PowerShell.Management.md @@ -12,7 +12,7 @@ Module Name: Microsoft.PowerShell.Management # Microsoft.PowerShell.Management Module ## Description -This section contains the help topics for the cmdlets that are installed with Windows PowerShell Microsoft.PowerShell.Management module. The Management module contains cmdlets that help you manage Windows in Windows PowerShell. +This section contains the help topics for the cmdlets that are installed with PowerShell Microsoft.PowerShell.Management module. The Management module contains cmdlets that help you manage Windows in PowerShell. ## Microsoft.PowerShell.Management Cmdlets ### [Add-Content](Add-Content.md) @@ -32,7 +32,7 @@ Clears the value of a property but does not delete the property. ### [Convert-Path](Convert-Path.md) -Converts a path from a Windows PowerShell path to a Windows PowerShell provider path. +Converts a path from a PowerShell path to a PowerShell provider path. ### [Copy-Item](Copy-Item.md) @@ -84,7 +84,7 @@ Gets drives in the current session. ### [Get-PSProvider](Get-PSProvider.md) -Gets information about the specified Windows PowerShell provider. +Gets information about the specified PowerShell provider. ### [Get-Service](Get-Service.md) @@ -144,7 +144,7 @@ Deletes the property and its value from an item. ### [Remove-PSDrive](Remove-PSDrive.md) -Deletes temporary Windows PowerShell drives and disconnects mapped network drives. +Deletes temporary PowerShell drives and disconnects mapped network drives. ### [Rename-Computer](Rename-Computer.md) @@ -152,7 +152,7 @@ Renames a computer. ### [Rename-Item](Rename-Item.md) -Renames an item in a Windows PowerShell provider namespace. +Renames an item in a PowerShell provider namespace. ### [Rename-ItemProperty](Rename-ItemProperty.md) diff --git a/reference/6/Microsoft.PowerShell.Management/Move-Item.md b/reference/6/Microsoft.PowerShell.Management/Move-Item.md index 0f1dceafbe4b..7b7d36b6f2ae 100644 --- a/reference/6/Microsoft.PowerShell.Management/Move-Item.md +++ b/reference/6/Microsoft.PowerShell.Management/Move-Item.md @@ -112,7 +112,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -167,7 +167,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when the cmdlet gets the objects, rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -219,7 +219,7 @@ Specifies the path to the current location of the items. Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Move-ItemProperty.md b/reference/6/Microsoft.PowerShell.Management/Move-ItemProperty.md index 42f7bd6395d4..2a694af19e28 100644 --- a/reference/6/Microsoft.PowerShell.Management/Move-ItemProperty.md +++ b/reference/6/Microsoft.PowerShell.Management/Move-ItemProperty.md @@ -52,7 +52,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, you will be prompted for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -103,7 +103,7 @@ Accept wildcard characters: False Specifies a filter in the provider's format or language. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcards, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects rather than having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when this cmdlet gets the objects rather than having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -155,7 +155,7 @@ Specifies the path to the current location of the property. Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/New-Item.md b/reference/6/Microsoft.PowerShell.Management/New-Item.md index 0a1d7701d45d..83a598b2681f 100644 --- a/reference/6/Microsoft.PowerShell.Management/New-Item.md +++ b/reference/6/Microsoft.PowerShell.Management/New-Item.md @@ -60,16 +60,16 @@ The *ItemType* parameter specifies that the new item is a directory, not a file PS C:\> New-Item -Path $profile -ItemType "file" -Force ``` -This command creates a Windows PowerShell profile in the path that is specified by the $profile variable. +This command creates a PowerShell profile in the path that is specified by the $profile variable. -You can use profiles to customize Windows PowerShell. +You can use profiles to customize PowerShell. $Profile is an automatic (built-in) variable that stores the path and file name of the CurrentUser/CurrentHost profile. -By default, the profile does not exist, even though Windows PowerShell stores a path and file name for it. +By default, the profile does not exist, even though PowerShell stores a path and file name for it. In this command, the $profile variable represents the path of the file. *ItemType* parameter specifies that the command creates a file. The *Force* parameter lets you create a file in the profile path, even when the directories in the path do not exist. -Windows PowerShell creates them. +PowerShell creates them. After you use this command to create a profile, you can enter aliases, functions, and scripts in the profile to customize your shell. @@ -102,7 +102,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, this cmdlet prompts you for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential diff --git a/reference/6/Microsoft.PowerShell.Management/New-PSDrive.md b/reference/6/Microsoft.PowerShell.Management/New-PSDrive.md index 61c2d25bb99b..76313b22860c 100644 --- a/reference/6/Microsoft.PowerShell.Management/New-PSDrive.md +++ b/reference/6/Microsoft.PowerShell.Management/New-PSDrive.md @@ -23,27 +23,27 @@ New-PSDrive [-Name] [-PSProvider] [-Root] [-Descripti ## DESCRIPTION The **New-PSDrive** cmdlet creates temporary and persistent drives that are mapped to or associated with a location in a data store, such as a network drive, a directory on the local computer, or a registry key, and persistent Windows mapped network drives that are associated with a file system location on a remote computer. -Temporary drives exist only in the current Windows PowerShell session and in sessions that you create in the current session. -They can have any name that is valid in Windows PowerShell and can be mapped to any local or remote resource. -You can use temporary Windows PowerShell drives to access data in the associated data store, just as you would do with any mapped network drive. +Temporary drives exist only in the current PowerShell session and in sessions that you create in the current session. +They can have any name that is valid in PowerShell and can be mapped to any local or remote resource. +You can use temporary PowerShell drives to access data in the associated data store, just as you would do with any mapped network drive. You can change locations into the drive, by using Set-Location, **cd**, or **chdir**, and access the contents of the drive by using Get-Item, Get-ChildItem, or **dir**. -However, because temporary drives are known only to Windows PowerShell, you cannot access them by using File Explorer, Windows Management Instrumentation (WMI), Component Object Model (COM), or the Microsoft .NET Framework, or by using tools such as Net Use. +However, because temporary drives are known only to PowerShell, you cannot access them by using File Explorer, Windows Management Instrumentation (WMI), Component Object Model (COM), or the Microsoft .NET Framework, or by using tools such as Net Use. The following features are added to **New-PSDrive** in Windows PowerShell 3.0: - Mapped network drives. You can use the *Persist* parameter of **New-PSDrive** to create Windows mapped network drives. -Unlike temporary Windows PowerShell drives, Windows mapped network drives are not session-specific. +Unlike temporary PowerShell drives, Windows mapped network drives are not session-specific. They are saved in Windows and they can be managed by using standard Windows tools, such as File Explorer and Net Use. Mapped network drives must have a drive-letter name and be connected to a remote file system location. When your command is scoped locally (no dot-sourcing), the *Persist* parameter does not persist the creation of a **PSDrive** beyond the scope in which the command is running. If you are running **New-PSDrive** inside a script, and you want the drive to persist indefinitely, you must dot-source the script. For best results, to force a new drive to persist indefinitely, add the *Scope* parameter to your command, and set its value to Global. - External drives. -When an external drive is connected to the computer, Windows PowerShell automatically adds a **PSDrive** to the file system that represents the new drive. -You do not have to restart Windows PowerShell. -Similarly, when an external drive is disconnected from the computer, Windows PowerShell automatically deletes the **PSDrive** that represents the removed drive. +When an external drive is connected to the computer, PowerShell automatically adds a **PSDrive** to the file system that represents the new drive. +You do not have to restart PowerShell. +Similarly, when an external drive is disconnected from the computer, PowerShell automatically deletes the **PSDrive** that represents the removed drive. - Credentials for UNC Paths. When the value of the *Root* parameter is a UNC path, such as \\\\Server\Share, the credential specified in the value of the *Credential* parameter is used to create the **PSDrive**. Otherwise, *Credential* is not effective when you are creating new file system drives. @@ -59,9 +59,9 @@ Name Provider Root P FileSystem \\Server01\Public ``` -This command creates a temporary Windows PowerShell drive named P: that is mapped to the \\\\Server01\Public network share. +This command creates a temporary PowerShell drive named P: that is mapped to the \\\\Server01\Public network share. -It uses the *Name* parameter to specify a name for the drive, the *PSProvider* parameter to specify the Windows PowerShell FileSystem provider, and the *Root* parameter to specify the network share. +It uses the *Name* parameter to specify a name for the drive, the *PSProvider* parameter to specify the PowerShell FileSystem provider, and the *Root* parameter to specify the network share. When the command finishes, the contents of the \\\\Server01\Public share appear in the P: drive. To see them, type: `dir P:`. @@ -75,10 +75,10 @@ Name Provider Root MyDocs FileSystem C:\Documents and Settings\User01\My Documents ``` -This command creates a temporary Windows PowerShell drive that provides quick access to a local directory. +This command creates a temporary PowerShell drive that provides quick access to a local directory. It creates a drive named MyDocs: that is mapped to the "C:\Documents and Settings\User01\My Documents" directory on the local computer. -It uses *Name* to specify a name for the drive, *PSProvider* to specify the Windows PowerShell FileSystem provider, *Root* to specify the path of the My Documents folder, and the *Description* parameter to create a description of the drive. +It uses *Name* to specify a name for the drive, *PSProvider* to specify the PowerShell FileSystem provider, *Root* to specify the path of the My Documents folder, and the *Description* parameter to create a description of the drive. When the command finishes, the contents of the My Documents folder appear in the MyDocs: drive. To see them, type: `dir MyDocs:`. @@ -92,10 +92,10 @@ Name Provider Root MyCompany Registry HKEY_LOCAL_MACHINE\Software\MyCo... ``` -This command creates a temporary Windows PowerShell drive that provides quick access to a frequently checked registry key. +This command creates a temporary PowerShell drive that provides quick access to a frequently checked registry key. It creates a drive named MyCompany that is mapped to the HKLM\Software\MyCompany registry key. -It uses *Name* to specify a name for the drive, *PSProvider* to specify the Windows PowerShell Registry provider, and *Root* to specify the registry key. +It uses *Name* to specify a name for the drive, *PSProvider* to specify the PowerShell Registry provider, and *Root* to specify the registry key. When the command finishes, the contents of the MyCompany key appear in the MyCompany: drive. To see them, type: `dir MyCompany:`. @@ -118,11 +118,11 @@ It uses *Persist* to create a Windows mapped network drive that is saved on the The command uses *Name* to specify a letter name that Windows accepts and *Root* to specify a location on a remote computer. It uses *PSProvider* to specify the FileSystem provider. -The resulting drive can be viewed in other Windows PowerShell sessions on the local computer, in Windows Explorer, and in other tools, such as Net Use. +The resulting drive can be viewed in other PowerShell sessions on the local computer, in Windows Explorer, and in other tools, such as Net Use. ### Example 5: Create persistent and temporary drives ``` -The first command uses the **New-PSDrive** cmdlet to create a temporary Windows PowerShell drive called PSDrive: that is mapped to the \\Server01\Public network share. +The first command uses the **New-PSDrive** cmdlet to create a temporary PowerShell drive called PSDrive: that is mapped to the \\Server01\Public network share. PS C:\> New-PSDrive -Name "PSDrive" -PSProvider "FileSystem" -Root "\\Server01\Public" The second command uses the *Persist* parameter of **New-PSDrive** to create the X: mapped network drive, which is also mapped to the \\Server01\Public network share. @@ -150,7 +150,7 @@ GetHashCode Method System.Int32 GetHashCode() ... -However, a Net Use command, a Get-WmiObject command for the Win32_LogicalDisk class, and a **Get-WmiObject** command for the Win32_NetworkConnection class find only the persistent X: drive because Windows PowerShell temporary drives are known only to Windows PowerShell.If you close the Windows PowerShell session and then open a new one, the PSDrive: drive is gone, and the X: drive persists. Therefore, when deciding which method to use to map network drives, consider how you will use the drive, whether it has to be persistent, and whether the drive has to be visible to other Windows features. +However, a Net Use command, a Get-WmiObject command for the Win32_LogicalDisk class, and a **Get-WmiObject** command for the Win32_NetworkConnection class find only the persistent X: drive because PowerShell temporary drives are known only to PowerShell.If you close the PowerShell session and then open a new one, the PSDrive: drive is gone, and the X: drive persists. Therefore, when deciding which method to use to map network drives, consider how you will use the drive, whether it has to be persistent, and whether the drive has to be visible to other Windows features. PS C:\> Net Use Status Local Remote Network @@ -172,7 +172,7 @@ LocalName RemoteName ConnectionState X: \\products\public Disconnected Unavailable ``` -This example shows the difference between a persistent mapped network drive and a temporary Windows PowerShell drive that is mapped to the same network share. +This example shows the difference between a persistent mapped network drive and a temporary PowerShell drive that is mapped to the same network share. ## PARAMETERS @@ -184,7 +184,7 @@ Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** If you type a user name, this cmdlet prompts you for a password. Starting in Windows PowerShell 3.0, when the value of the *Root* parameter is a UNC path, you can use credentials to create file system drives. -This parameter is not supported by all Windows PowerShell providers. +This parameter is not supported by all PowerShell providers. ```yaml Type: PSCredential @@ -220,7 +220,7 @@ Accept wildcard characters: False ### -Name Specifies a name for the new drive. For persistent mapped network drives, type a drive letter. -For temporary Windows PowerShell drives, type any valid string; you are not limited to drive letters. +For temporary PowerShell drives, type any valid string; you are not limited to drive letters. ```yaml Type: String @@ -266,15 +266,15 @@ Accept wildcard characters: False ``` ### -PSProvider -Specifies the Windows PowerShell provider that supports drives of this kind. +Specifies the PowerShell provider that supports drives of this kind. -For example, if the drive is associated with a network share or file system directory, the Windows PowerShell provider is FileSystem. +For example, if the drive is associated with a network share or file system directory, the PowerShell provider is FileSystem. If the drive is associated with a registry key, the provider is Registry. -Temporary Windows PowerShell drives can be associated with any Windows PowerShell provider. +Temporary PowerShell drives can be associated with any PowerShell provider. Mapped network drives can be associated only with the FileSystem provider. -To see a list of the providers in your Windows PowerShell session, use the Get-PSProvider cmdlet. +To see a list of the providers in your PowerShell session, use the Get-PSProvider cmdlet. ```yaml Type: String @@ -289,11 +289,11 @@ Accept wildcard characters: False ``` ### -Root -Specifies the data store location to which a Windows PowerShell drive is mapped. +Specifies the data store location to which a PowerShell drive is mapped. For example, specify a network share, such as \\\\Server01\Public, a local directory, such as C:\Program Files, or a registry key, such as HKLM:\Software\Microsoft. -Temporary Windows PowerShell drives can be associated with a local or remote location on any supported provider drive. +Temporary PowerShell drives can be associated with a local or remote location on any supported provider drive. Mapped network drives can be associated only with a file system location on a remote computer. ```yaml diff --git a/reference/6/Microsoft.PowerShell.Management/New-Service.md b/reference/6/Microsoft.PowerShell.Management/New-Service.md index c35bc864fce7..6a3818d2d12c 100644 --- a/reference/6/Microsoft.PowerShell.Management/New-Service.md +++ b/reference/6/Microsoft.PowerShell.Management/New-Service.md @@ -228,7 +228,7 @@ You cannot pipe input to this cmdlet. This cmdlet returns an object that represents the new service. ## NOTES -* To run this cmdlet on Windows Vista and later versions of the Windows operating system, start Windows PowerShell by using the Run as administrator option. +* To run this cmdlet on Windows Vista and later versions of the Windows operating system, start PowerShell by using the Run as administrator option. ## RELATED LINKS diff --git a/reference/6/Microsoft.PowerShell.Management/Pop-Location.md b/reference/6/Microsoft.PowerShell.Management/Pop-Location.md index 82a2ce0f5c43..5b7c8477e183 100644 --- a/reference/6/Microsoft.PowerShell.Management/Pop-Location.md +++ b/reference/6/Microsoft.PowerShell.Management/Pop-Location.md @@ -50,12 +50,12 @@ PS HKLM:\Software\Microsoft\PowerShell> popd PS C:\> ``` -These commands use the **Push-Location** and **Pop-Location** cmdlets to move between locations supported by different Windows PowerShell providers. +These commands use the **Push-Location** and **Pop-Location** cmdlets to move between locations supported by different PowerShell providers. The commands use the **pushd** alias for **Push-Location** and the **popd** alias for **Pop-Location**. -The first command pushes the current file system location onto the stack and moves to the HKLM drive supported by the Windows PowerShell Registry provider. +The first command pushes the current file system location onto the stack and moves to the HKLM drive supported by the PowerShell Registry provider. -The second command pushes the registry location onto the stack and moves to a location supported by the Windows PowerShell certificate provider. +The second command pushes the registry location onto the stack and moves to a location supported by the PowerShell certificate provider. The last two commands pop those locations off the stack. The first **popd** command returns to the Registry drive, and the second command returns to the file system drive. @@ -83,7 +83,7 @@ Specifies the location stack from which the location is popped. Enter a location stack name. Without this parameter, **Pop-Location** pops a location from the current location stack. -By default, the current location stack is the unnamed default location stack that Windows PowerShell creates. +By default, the current location stack is the unnamed default location stack that PowerShell creates. To make a location stack the current location stack, use the *StackName* parameter of **Set-Location**. **Pop-Location** cannot pop a location from the unnamed default stack unless it is the current location stack. @@ -134,9 +134,9 @@ This cmdlet generates a **System.Management.Automation.PathInfo** object that re Otherwise, this cmdlet does not generate any output. ## NOTES -* A stack is a last-in, first-out list in which only the most recently added item can be accessed. You add items to a stack in the order that you use them, and then retrieve them for use in the reverse order. Windows PowerShell lets you store provider locations in location stacks. -* Windows PowerShell lets you store provider locations in location stacks. Windows PowerShell creates an unnamed default location stack and you can create multiple named location stacks. If you do not specify a stack name, Windows PowerShell uses the current location stack. By default, the unnamed default location is the current location stack, but you can use the Set-Location cmdlet to change the current location stack. -* To manage location stacks, use the Windows PowerShell**Location** cmdlets, as follows: +* A stack is a last-in, first-out list in which only the most recently added item can be accessed. You add items to a stack in the order that you use them, and then retrieve them for use in the reverse order. PowerShell lets you store provider locations in location stacks. +* PowerShell lets you store provider locations in location stacks. PowerShell creates an unnamed default location stack and you can create multiple named location stacks. If you do not specify a stack name, PowerShell uses the current location stack. By default, the unnamed default location is the current location stack, but you can use the Set-Location cmdlet to change the current location stack. +* To manage location stacks, use the PowerShell**Location** cmdlets, as follows: - To add a location to a location stack, use the **Push-Location** cmdlet. - To get a location from a location stack, use the **Pop-Location** cmdlet. diff --git a/reference/6/Microsoft.PowerShell.Management/Push-Location.md b/reference/6/Microsoft.PowerShell.Management/Push-Location.md index 1569b2c7fd9a..b9621779a695 100644 --- a/reference/6/Microsoft.PowerShell.Management/Push-Location.md +++ b/reference/6/Microsoft.PowerShell.Management/Push-Location.md @@ -47,7 +47,7 @@ PS C:\> Push-Location -Path "HKLM:\Software\Policies" -StackName RegFunction ``` This command pushes the current location onto the RegFunction stack and changes the current location to the HKLM:\Software\Policies location. -You can use the **Location** cmdlets in any Windows PowerShell drive (PSDrive). +You can use the **Location** cmdlets in any PowerShell drive (PSDrive). ### Example 3: Push the current location onto the default stack ``` @@ -86,7 +86,7 @@ Specifies the path of the new location. Unlike the *Path* parameter, the value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String @@ -140,7 +140,7 @@ Enter a location stack name. If the stack does not exist, **Push-Location** creates it. Without this parameter, **Push-Location** adds the location to the current location stack. -By default, the current location stack is the unnamed default location stack that Windows PowerShell creates. +By default, the current location stack is the unnamed default location stack that PowerShell creates. To make a location stack the current location stack, use the *StackName* parameter of the Set-Location cmdlet. For more information about location stacks, see the Notes. @@ -192,9 +192,9 @@ This cmdlet generates a **System.Management.Automation.PathInfo** object that re Otherwise, this cmdlet does not generate any output. ## NOTES -* A stack is a last-in, first-out list in which only the most recently added item can be accessed. You add items to a stack in the order that you use them, and then retrieve them for use in the reverse order. Windows PowerShell lets you store provider locations in location stacks. -* Windows PowerShell creates an unnamed default location stack and you can create multiple named location stacks. If you do not specify a stack name, Windows PowerShell uses the current location stack. By default, the unnamed default location is the current location stack, but you can use **Set-Location** to change the current location stack. -* To manage location stacks, use the Windows PowerShell **Location** cmdlets, as follows: +* A stack is a last-in, first-out list in which only the most recently added item can be accessed. You add items to a stack in the order that you use them, and then retrieve them for use in the reverse order. PowerShell lets you store provider locations in location stacks. +* PowerShell creates an unnamed default location stack and you can create multiple named location stacks. If you do not specify a stack name, PowerShell uses the current location stack. By default, the unnamed default location is the current location stack, but you can use **Set-Location** to change the current location stack. +* To manage location stacks, use the PowerShell **Location** cmdlets, as follows: - To add a location to a location stack, use the **Push-Location** cmdlet. - To get a location from a location stack, use the **Pop-Location** cmdlet. diff --git a/reference/6/Microsoft.PowerShell.Management/Remove-Item.md b/reference/6/Microsoft.PowerShell.Management/Remove-Item.md index 07dd70ca097a..baf3f8027dfb 100644 --- a/reference/6/Microsoft.PowerShell.Management/Remove-Item.md +++ b/reference/6/Microsoft.PowerShell.Management/Remove-Item.md @@ -160,7 +160,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, this cmdlet prompts you for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -196,7 +196,7 @@ Accept wildcard characters: False Specifies a filter in the format or language of the provider. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcard characters, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects, instead of having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects, instead of having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -252,7 +252,7 @@ Specifies a path of the items being removed. Unlike **Path**, the value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Remove-ItemProperty.md b/reference/6/Microsoft.PowerShell.Management/Remove-ItemProperty.md index a7567a868e5b..9a1b0d1d4cd3 100644 --- a/reference/6/Microsoft.PowerShell.Management/Remove-ItemProperty.md +++ b/reference/6/Microsoft.PowerShell.Management/Remove-ItemProperty.md @@ -81,7 +81,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, this cmdlet prompts you for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -117,7 +117,7 @@ Accept wildcard characters: False Specifies a filter in the format or language of the provider. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcard characters, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects instead of having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects instead of having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -171,7 +171,7 @@ Specifies a path of the item property. The value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] @@ -281,7 +281,7 @@ This cmdlet does not return any output. ## NOTES * You can also refer to **Remove-ItemProperty** by its built-in alias, **rp**. For more information, see about_Aliases. -* In the Windows PowerShell Registry provider, registry values are considered to be properties of a registry key or subkey. You can use the **ItemProperty** cmdlets to manage these values. +* In the PowerShell Registry provider, registry values are considered to be properties of a registry key or subkey. You can use the **ItemProperty** cmdlets to manage these values. * **Remove-ItemProperty** is designed to work with the data exposed by any provider. To list the providers available in your session, type `Get-PSProvider`. For more information, see about_Providers. ## RELATED LINKS diff --git a/reference/6/Microsoft.PowerShell.Management/Remove-PSDrive.md b/reference/6/Microsoft.PowerShell.Management/Remove-PSDrive.md index 55e41fd14705..38f744e0fb78 100644 --- a/reference/6/Microsoft.PowerShell.Management/Remove-PSDrive.md +++ b/reference/6/Microsoft.PowerShell.Management/Remove-PSDrive.md @@ -11,7 +11,7 @@ title: Remove-PSDrive # Remove-PSDrive ## SYNOPSIS -Deletes temporary Windows PowerShell drives and disconnects mapped network drives. +Deletes temporary PowerShell drives and disconnects mapped network drives. ## SYNTAX @@ -28,15 +28,15 @@ Remove-PSDrive [-LiteralName] [-PSProvider ] [-Scope Restart-Computer -ComputerName "Server01" -Wait -For PowerShell -Timeout 300 -Delay 2 ``` -This command restarts the Server01 remote computer and then waits up to 5 minutes (300 seconds) for Windows PowerShell to be available on the restarted computer before it continues. +This command restarts the Server01 remote computer and then waits up to 5 minutes (300 seconds) for PowerShell to be available on the restarted computer before it continues. The command uses the *Wait*, *For*, and *Timeout* parameters to specify the conditions of the wait. It uses the *Delay* parameter to reduce the interval between queries to the remote computer that determine whether it is restarted. @@ -118,7 +118,7 @@ These settings are designed for enterprises in which DCOM-based restarts fail be ### -AsJob Indicates that this cmdlet runs as a background job. -To use this parameter, the local and remote computers must be configured for remoting and, on Windows Vista and later versions of the Windows operating system, you must open Windows PowerShell by using the Run as administrator option. +To use this parameter, the local and remote computers must be configured for remoting and, on Windows Vista and later versions of the Windows operating system, you must open PowerShell by using the Run as administrator option. For more information, see [about_Remote_Requirements](../Microsoft.PowerShell.Core/About/about_Remote_Requirements.md). When you specify the *AsJob* parameter, the command immediately returns an object that represents the background job. @@ -127,7 +127,7 @@ The job is created on the local computer and the results from remote computers a To manage the job, use the **Job** cmdlets. To get the job results, use the Receive-Job cmdlet. -For more information about Windows PowerShell background jobs, see [about_Jobs](../Microsoft.PowerShell.Core/About/about_Jobs.md) and [about_Remote_Jobs](../Microsoft.PowerShell.Core/About/about_Remote_Jobs.md). +For more information about PowerShell background jobs, see [about_Jobs](../Microsoft.PowerShell.Core/About/about_Jobs.md) and [about_Remote_Jobs](../Microsoft.PowerShell.Core/About/about_Remote_Jobs.md). ```yaml Type: SwitchParameter @@ -148,7 +148,7 @@ The default is the local computer. Type the NETBIOS name, an IP address, or a fully qualified domain name of a remote computer. To specify the local computer, type the computer name, a dot (.), or localhost. -This parameter does not rely on Windows PowerShell remoting. +This parameter does not rely on PowerShell remoting. You can use the *ComputerName* parameter even if your computer is not configured to run remote commands. ```yaml @@ -182,7 +182,7 @@ Accept wildcard characters: False ``` ### -Delay -Determines how often, in seconds, Windows PowerShell queries the service that is specified by the *For* parameter to determine whether it is available after the computer is restarted. +Determines how often, in seconds, PowerShell queries the service that is specified by the *For* parameter to determine whether it is available after the computer is restarted. Specify a delay between queries, in seconds. The default value is 5 seconds. @@ -203,15 +203,15 @@ Accept wildcard characters: False ``` ### -For -Specifies the behavior of Windows PowerShell as it waits for the specified service or feature to become available after the computer restarts. +Specifies the behavior of PowerShell as it waits for the specified service or feature to become available after the computer restarts. This parameter is valid only with the *Wait* parameter. The acceptable values for this parameter are: - Default. -Waits for Windows PowerShell to restart. +Waits for PowerShell to restart. - PowerShell. -Can run commands in a Windows PowerShell remote session on the computer. +Can run commands in a PowerShell remote session on the computer. - WMI. Receives a reply to a Win32_ComputerSystem query for the computer. - WinRM. @@ -316,7 +316,7 @@ Accept wildcard characters: False ``` ### -Wait -Indicates that this cmdlet suppresses the Windows PowerShell prompt and blocks the pipeline until all of the computers have restarted. +Indicates that this cmdlet suppresses the PowerShell prompt and blocks the pipeline until all of the computers have restarted. You can use this parameter in a script to restart computers and then continue to process when the restart is finished. By default, *Wait* waits indefinitely for the computers to restart, but you can use *Timeout* to adjust the timing and the *For* and *Delay* parameters to wait for particular services to be available on the restarted computers. diff --git a/reference/6/Microsoft.PowerShell.Management/Set-Item.md b/reference/6/Microsoft.PowerShell.Management/Set-Item.md index 992dcd58a20c..8e6b5eec853d 100644 --- a/reference/6/Microsoft.PowerShell.Management/Set-Item.md +++ b/reference/6/Microsoft.PowerShell.Management/Set-Item.md @@ -72,7 +72,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, this cmdlet prompts for a password. -This parameter is not supported by any providers installed with parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -108,7 +108,7 @@ Accept wildcard characters: False Specifies a filter in the format or language of the provider. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcard characters, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects, instead of having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects, instead of having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -164,7 +164,7 @@ Specifies a path of the location of the new items. Unlike *Path*, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] @@ -292,7 +292,7 @@ Otherwise, this cmdlet does not generate any output. ## NOTES * You can also refer to **Set-Item** by its built-in alias, **si**. For more information, see about_Aliases. - **Set-Item** is not supported by the Windows PowerShell FileSystem provider. + **Set-Item** is not supported by the PowerShell FileSystem provider. To change the values of items in the file system, use the Set-Content cmdlet. In the Registry drives, HKLM: and HKCU:, **Set-Item** changes the data in the (Default) value of a registry key. diff --git a/reference/6/Microsoft.PowerShell.Management/Set-ItemProperty.md b/reference/6/Microsoft.PowerShell.Management/Set-ItemProperty.md index 087360dec10e..75904cf065d6 100644 --- a/reference/6/Microsoft.PowerShell.Management/Set-ItemProperty.md +++ b/reference/6/Microsoft.PowerShell.Management/Set-ItemProperty.md @@ -110,7 +110,7 @@ The third command changes the value of the **NoOfEmployees** entry to 824. You can also use the New-ItemProperty cmdlet to create the registry entry and its value and then use **Set-ItemProperty** to change the value. For more information about the HKLM: drive, type `Get-Help Get-PSDrive`. -For more information about how to use Windows PowerShell to manage the registry, type `Get-Help Registry`. +For more information about how to use PowerShell to manage the registry, type `Get-Help Registry`. ### Example 3: Modify an item by using the pipeline ``` @@ -134,7 +134,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, this cmdlet prompts you for a password. -This parameter is not supported by any providers installed with parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -167,7 +167,7 @@ Accept wildcard characters: False Specifies a filter in the format or language of the provider. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcard characters, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects instead of having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects instead of having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -234,7 +234,7 @@ Specifies a path of the item property. The value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Management/Set-Location.md b/reference/6/Microsoft.PowerShell.Management/Set-Location.md index 39bd82c881d2..f90c3f8da04a 100644 --- a/reference/6/Microsoft.PowerShell.Management/Set-Location.md +++ b/reference/6/Microsoft.PowerShell.Management/Set-Location.md @@ -58,7 +58,7 @@ PS Env:\> ``` This command sets the current location to the root of the Env: drive. -It uses the *PassThru* parameter to direct Windows PowerShell to return a **PathInfo** object that represents the Env: location. +It uses the *PassThru* parameter to direct PowerShell to return a **PathInfo** object that represents the Env: location. ### Example 3: Set location to the C: drive ``` @@ -84,7 +84,7 @@ Specifies a path of the location. The value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String @@ -187,13 +187,13 @@ Otherwise, this cmdlet does not generate any output. A stack is a last-in, first-out list in which only the most recently added item can be accessed. You add items to a stack in the order that you use them, and then retrieve them for use in the reverse order. -Windows PowerShell lets you store provider locations in location stacks. -Windows PowerShell creates an unnamed default location stack. +PowerShell lets you store provider locations in location stacks. +PowerShell creates an unnamed default location stack. You can create multiple named location stacks. -If you do not specify a stack name, Windows PowerShell uses the current location stack. +If you do not specify a stack name, PowerShell uses the current location stack. By default, the unnamed default location is the current location stack, but you can use the **Set-Location** cmdlet to change the current location stack. - To manage location stacks, use the Windows PowerShell Location cmdlets, as follows: + To manage location stacks, use the PowerShell Location cmdlets, as follows: - To add a location to a location stack, use the Push-Location cmdlet. - To get a location from a location stack, use the Pop-Location cmdlet. diff --git a/reference/6/Microsoft.PowerShell.Management/Split-Path.md b/reference/6/Microsoft.PowerShell.Management/Split-Path.md index ec10018c720a..cf3179ae1835 100644 --- a/reference/6/Microsoft.PowerShell.Management/Split-Path.md +++ b/reference/6/Microsoft.PowerShell.Management/Split-Path.md @@ -120,12 +120,12 @@ PS C:\> Set-Location (Split-Path -Path $profile) PS C:\Documents and Settings\User01\My Documents\WindowsPowerShell> ``` -This command changes your location to the folder that contains the Windows PowerShell profile. +This command changes your location to the folder that contains the PowerShell profile. The command in parentheses uses **Split-Path** to return only the parent of the path stored in the built-in $Profile variable. The *Parent* parameter is the default split location parameter. Therefore, you can omit it from the command. -The parentheses direct Windows PowerShell to run the command first. +The parentheses direct PowerShell to run the command first. This is a useful way to move to a folder that has a long path name. ### Example 6: Split a path by using the pipeline @@ -146,7 +146,7 @@ The default is the current user. Type a user name, such as User01 or Domain01\User01, or enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, this cmdlet prompts you for a password. -This parameter is not supported by any providers installed with parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -229,7 +229,7 @@ Specifies the paths to be split. Unlike *Path*, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] @@ -364,7 +364,7 @@ When you specify the *IsAbsolute* parameter, **Split-Path** returns a **Boolean* ## NOTES * The split location parameters (*Qualifier*, *Parent*, *Extension*, *Leaf*, *LeafBase*, and *NoQualifier*) are exclusive. You can use only one in each command. - The cmdlets that contain the **Path** noun (the **Path** cmdlets) work with path names and return the names in a concise format that all Windows PowerShell providers can interpret. + The cmdlets that contain the **Path** noun (the **Path** cmdlets) work with path names and return the names in a concise format that all PowerShell providers can interpret. They are designed for use in programs and scripts where you want to display all or part of a path name in a particular format. Use them in the way that you would use **Dirname**, **Normpath**, **Realpath**, **Join**, or other path manipulators. diff --git a/reference/6/Microsoft.PowerShell.Management/Start-Process.md b/reference/6/Microsoft.PowerShell.Management/Start-Process.md index 6fa62b5524b2..af3a38854eb1 100644 --- a/reference/6/Microsoft.PowerShell.Management/Start-Process.md +++ b/reference/6/Microsoft.PowerShell.Management/Start-Process.md @@ -71,12 +71,12 @@ PS C:\> Start-Process -FilePath "notepad" -Wait -WindowStyle Maximized This command starts the Notepad process. It maximizes the window and retains the window until the process completes. -### Example 5: Start Windows Powershell as an administrator +### Example 5: Start PowerShell as an administrator ``` PS C:\> Start-Process -FilePath "powershell" -Verb runAs ``` -This command starts Windows PowerShell by using the Run as administrator option. +This command starts PowerShell by using the Run as administrator option. ### Example 6: Using different verbs to start a process ``` @@ -111,7 +111,7 @@ The Open verb starts the process in a new console window. The fourth command starts a PowerShell process with the RunAs verb. The RunAs verb starts the process with permissions of a member of the Administrators group on the computer. -This is the same as starting Windows PowerShell by using the Run as administrator option. +This is the same as starting PowerShell by using the Run as administrator option. ### Example 7: Specifying arguments to the process ``` @@ -179,7 +179,7 @@ Accept wildcard characters: False ### -LoadUserProfile Indicates that this cmdlet loads the Windows user profile stored in the **HKEY_USERS** registry key for the current user. -This parameter does not affect the Windows PowerShell profiles. +This parameter does not affect the PowerShell profiles. For more information, see about_Profiles. ```yaml @@ -196,7 +196,7 @@ Accept wildcard characters: False ### -NoNewWindow Start the new process in the current console window. -By default Windows PowerShell opens a new window. +By default PowerShell opens a new window. You cannot use the *NoNewWindow* and *WindowStyle* parameters in the same command. diff --git a/reference/6/Microsoft.PowerShell.Management/Start-Service.md b/reference/6/Microsoft.PowerShell.Management/Start-Service.md index 90b4e932b586..6f8ef221541f 100644 --- a/reference/6/Microsoft.PowerShell.Management/Start-Service.md +++ b/reference/6/Microsoft.PowerShell.Management/Start-Service.md @@ -257,7 +257,7 @@ Otherwise, this cmdlet does not generate any output. * **Start-Service** can control services only if the current user has permission to do this. If a command does not work correctly, you might not have the required permissions. * To find the service names and display names of the services on your system, type `Get-Service`. The service names appear in the **Name** column, and the display names appear in the **DisplayName** column. * You can start only the services that have a start type of Manual or Automatic. You cannot start the services that have a start type of Disabled. If a **Start-Service** command fails with the message `Cannot start service \ on computer`, use Get-WmiObject to find the start type of the service and, if you have to, use the Set-Service cmdlet to change the start type of the service. -* Some services, such as Performance Logs and Alerts (SysmonLog) stop automatically if they have no work to do. When Windows PowerShell starts a service that stops itself almost immediately, it displays the following message: `Service \ start failed.` +* Some services, such as Performance Logs and Alerts (SysmonLog) stop automatically if they have no work to do. When PowerShell starts a service that stops itself almost immediately, it displays the following message: `Service \ start failed.` ## RELATED LINKS diff --git a/reference/6/Microsoft.PowerShell.Management/Stop-Computer.md b/reference/6/Microsoft.PowerShell.Management/Stop-Computer.md index e9552c66c3d6..a164b755d27d 100644 --- a/reference/6/Microsoft.PowerShell.Management/Stop-Computer.md +++ b/reference/6/Microsoft.PowerShell.Management/Stop-Computer.md @@ -28,7 +28,7 @@ It can also shut down the local computer. You can use the parameters of **Stop-Computer** to run the shutdown operations as a background job, to specify the authentication levels and alternate credentials, to limit the concurrent connections that are created to run the command, and to force an immediate shut down. -This cmdlet does not require Windows PowerShell remoting unless you use the *AsJob* parameter. +This cmdlet does not require PowerShell remoting unless you use the *AsJob* parameter. ## EXAMPLES @@ -95,7 +95,7 @@ It also uses the *ThrottleLimit* parameter to limit the command to 10 concurrent ### -AsJob Indicates that this cmdlet runs as a background job. -To use this parameter, the local and remote computers must be configured for remoting and, on Windows Vista and later versions of the Windows operating system, you must open Windows PowerShell by using the Run as administrator option. +To use this parameter, the local and remote computers must be configured for remoting and, on Windows Vista and later versions of the Windows operating system, you must open PowerShell by using the Run as administrator option. For more information, see about_Remote_Requirements. When you specify the *AsJob* parameter, the command immediately returns an object that represents the background job. @@ -103,7 +103,7 @@ You can continue to work in the session while the job finishes. The job is created on the local computer and the results from remote computers are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. -For more information about Windows PowerShell background jobs, see [about_Jobs](../Microsoft.PowerShell.Core/About/about_Jobs.md) and [about_Remote_Jobs](../Microsoft.PowerShell.Core/About/about_Remote_Jobs.md). +For more information about PowerShell background jobs, see [about_Jobs](../Microsoft.PowerShell.Core/About/about_Jobs.md) and [about_Remote_Jobs](../Microsoft.PowerShell.Core/About/about_Remote_Jobs.md). ```yaml Type: SwitchParameter @@ -124,7 +124,7 @@ The default is the local computer. Type the NETBIOS name, IP address, or fully qualified domain name of one or more computers in a comma-separated list. To specify the local computer, type the computer name or localhost. -This parameter does not rely on Windows PowerShell remoting. +This parameter does not rely on PowerShell remoting. You can use the *ComputerName* parameter even if your computer is not configured to run remote commands. ```yaml diff --git a/reference/6/Microsoft.PowerShell.Management/Stop-Process.md b/reference/6/Microsoft.PowerShell.Management/Stop-Process.md index 2de4a14f3bec..dbc09783dbe1 100644 --- a/reference/6/Microsoft.PowerShell.Management/Stop-Process.md +++ b/reference/6/Microsoft.PowerShell.Management/Stop-Process.md @@ -35,7 +35,7 @@ The **Stop-Process** cmdlet stops one or more running processes. You can specify a process by process name or process ID (PID), or pass a process object to **Stop-Process**. **Stop-Process** works only on processes running on the local computer. -On Windows Vista and later versions of the Windows operating system, to stop a process that is not owned by the current user, you must start Windows PowerShell by using the Run as administrator option. +On Windows Vista and later versions of the Windows operating system, to stop a process that is not owned by the current user, you must start PowerShell by using the Run as administrator option. Also, you are will not be prompted for confirmation unless you specify the *Confirm* parameter. ## EXAMPLES @@ -65,7 +65,7 @@ Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName This command stops a particular instance of the Notepad process. It uses the process ID, 3952, to identify the process. -The *Confirm* parameter directs Windows PowerShell to prompt you before it stops the process. +The *Confirm* parameter directs PowerShell to prompt you before it stops the process. Because the prompt includes the process namein addition to its ID, this is best practice. The *PassThru* parameter passes the process object to the formatter for display. Without this parameter, there would be no display after a **Stop-Process** command. @@ -117,7 +117,7 @@ The first command uses **Get-Process** to get the Lsass process. A pipeline operator sends the process to **Stop-Process** to stop it. As shown in the sample output, the first command fails with an Access denied message, because this process can be stopped only by a member of the Administrator group on the computer. -When Windows PowerShell is opened by using the Run as administrator option, and the command is repeated, Windows PowerShell prompts you for confirmation. +When PowerShell is opened by using the Run as administrator option, and the command is repeated, PowerShell prompts you for confirmation. The second command specifies *Force* to suppress the prompt. As a result, the process is stopped without confirmation. @@ -255,7 +255,7 @@ Otherwise, this cmdlet does not generate any output. ## NOTES * You can also refer to **Stop-Process** by its built-in aliases, **kill** and **spps**. For more information, see about_Aliases. -* You can also use the properties and methods of the Windows Management Instrumentation (WMI) **Win32_Process** object in Windows PowerShell. For more information, see **Get-WmiObject** and the WMI SDK. +* You can also use the properties and methods of the Windows Management Instrumentation (WMI) **Win32_Process** object in PowerShell. For more information, see **Get-WmiObject** and the WMI SDK. * When stopping processes, realize that stopping a process can stop process and services that depend on the process. In an extreme case, stopping a process can stop Windows. diff --git a/reference/6/Microsoft.PowerShell.Management/Test-Connection.md b/reference/6/Microsoft.PowerShell.Management/Test-Connection.md index 43ef64cf8e9e..de46e277e267 100644 --- a/reference/6/Microsoft.PowerShell.Management/Test-Connection.md +++ b/reference/6/Microsoft.PowerShell.Management/Test-Connection.md @@ -45,7 +45,7 @@ You can use this cmdlet to determine whether a particular computer can be contac You can use the parameters of **Test-Connection** to specify both the sending and receiving computers, to run the command as a background job, to set a time-out and number of pings, and to configure the connection and authentication. -Unlike the familiar **ping** command, **Test-Connection** returns a **Win32_PingStatus** object that you can investigate in Windows PowerShell. +Unlike the familiar **ping** command, **Test-Connection** returns a **Win32_PingStatus** object that you can investigate in PowerShell. You can use the *Quiet* parameter to force it to return only a **Boolean** value. ## EXAMPLES @@ -97,7 +97,7 @@ PS C:\> $job = Test-Connection -ComputerName (Get-Content "Servers.txt") -AsJob PS C:\> if ($job.JobStateInfo.State -ne "Running") {$Results = Receive-Job $job} ``` -This example shows how to run a **Test-Connection** command as a Windows PowerShell background job. +This example shows how to run a **Test-Connection** command as a PowerShell background job. The first command uses the **Test-Connection** cmdlet to ping many computers in an enterprise. The value of the *ComputerName* parameter is a Get-Content command that reads a list of computer names from the Servers.txt file. @@ -131,7 +131,7 @@ If the **Test-Connection** command returns a value of $True, the command uses th ### -AsJob Indicates that this cmdlet runs as a background job. -To use this parameter, the local and remote computers must be configured for remoting and, on Windows Vista and later versions of the Windows operating system, you must open Windows PowerShell by using the Run as administrator option. +To use this parameter, the local and remote computers must be configured for remoting and, on Windows Vista and later versions of the Windows operating system, you must open PowerShell by using the Run as administrator option. For more information, see about_Remote_Requirements. When you specify the *AsJob* parameter, the command immediately returns an object that represents the background job. @@ -139,7 +139,7 @@ You can continue to work in the session while the job finishes. The job is created on the local computer and the results from remote computers are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet. -For more information about Windows PowerShell background jobs, see [about_Jobs](../Microsoft.PowerShell.Core/About/about_Jobs.md) and [about_Remote_Jobs](../Microsoft.PowerShell.Core/About/about_Remote_Jobs.md). +For more information about PowerShell background jobs, see [about_Jobs](../Microsoft.PowerShell.Core/About/about_Jobs.md) and [about_Remote_Jobs](../Microsoft.PowerShell.Core/About/about_Remote_Jobs.md). ```yaml Type: SwitchParameter @@ -175,7 +175,7 @@ Type the computer names or type IP addresses in IPv4 or IPv6 format. Wildcard characters are not permitted. This parameter is required. -This parameter does not rely on Windows PowerShell remoting. +This parameter does not rely on PowerShell remoting. You can use the *ComputerName* parameter even if your computer is not configured to run remote commands. ```yaml diff --git a/reference/6/Microsoft.PowerShell.Management/Test-Path.md b/reference/6/Microsoft.PowerShell.Management/Test-Path.md index 9639e0e136e7..08ceb98e2132 100644 --- a/reference/6/Microsoft.PowerShell.Management/Test-Path.md +++ b/reference/6/Microsoft.PowerShell.Management/Test-Path.md @@ -51,7 +51,7 @@ PS C:\> Test-Path -Path $profile PS C:\> Test-Path -Path $profile -IsValid ``` -These commands test the path of the Windows PowerShell profile. +These commands test the path of the PowerShell profile. The first command determines whether all elements in the path exist. The second command determines whether the syntax of the path is correct. @@ -82,7 +82,7 @@ PS C:\> Test-Path -Path $profile -PathType leaf ``` This command checks whether the path stored in the $profile variable leads to a file. -In this case, because the Windows PowerShell profile is a .ps1 file, the cmdlet returns $True. +In this case, because the PowerShell profile is a .ps1 file, the cmdlet returns $True. ### Example 5: Check paths in the Registry ``` @@ -92,12 +92,12 @@ PS C:\> Test-Path -Path "HKLM:\Software\Microsoft\PowerShell\1\ShellIds\Microsof False ``` -These commands use **Test-Path** with the Windows PowerShell registry provider. +These commands use **Test-Path** with the PowerShell registry provider. The first command tests whether the registry path of the Microsoft.PowerShell registry key is correct on the system. -If Windows PowerShell is installed correctly, the cmdlet returns $True. +If PowerShell is installed correctly, the cmdlet returns $True. -**Test-Path** does not work correctly with all Windows PowerShell providers. +**Test-Path** does not work correctly with all PowerShell providers. For example, you can use **Test-Path** to test the path of a registry key, but if you use it to test the path of a registry entry, it always returns $False, even if the registry entry is present. ## PARAMETERS @@ -140,7 +140,7 @@ Type a user name, such as User01 or Domain01\User01. Or, enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet. If you type a user name, this cmdlet prompts you for a password. -This parameter is not supported by any providers installed with Windows PowerShell. +This parameter is not supported by any providers installed with PowerShell. ```yaml Type: PSCredential @@ -176,7 +176,7 @@ Accept wildcard characters: False Specifies a filter in the format or language of the provider. The value of this parameter qualifies the *Path* parameter. The syntax of the filter, including the use of wildcard characters, depends on the provider. -Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects instead of having Windows PowerShell filter the objects after they are retrieved. +Filters are more efficient than other parameters, because the provider applies them when it retrieves the objects instead of having PowerShell filter the objects after they are retrieved. ```yaml Type: String @@ -229,7 +229,7 @@ Specifies a path to be tested. Unlike *Path*, the value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] @@ -319,7 +319,7 @@ You can pipe a string that contains a path, but not a literal path, to this cmdl The cmdlet returns a **Boolean** value. ## NOTES -* The cmdlets that contain the **Path** noun (the **Path** cmdlets) work with path names and return the names in a concise format that all Windows PowerShell providers can interpret. They are designed for use in programs and scripts where you want to display all or part of a path name in a particular format. Use them as you would use **Dirname**, **Normpath**, **Realpath**, **Join**, or other path manipulators. +* The cmdlets that contain the **Path** noun (the **Path** cmdlets) work with path names and return the names in a concise format that all PowerShell providers can interpret. They are designed for use in programs and scripts where you want to display all or part of a path name in a particular format. Use them as you would use **Dirname**, **Normpath**, **Realpath**, **Join**, or other path manipulators. You can use the **Path** cmdlets with several providers, including the FileSystem, Registry, and Certificate providers. diff --git a/reference/6/Microsoft.PowerShell.Management/Wait-Process.md b/reference/6/Microsoft.PowerShell.Management/Wait-Process.md index e631cacd5199..737aa8259c6b 100644 --- a/reference/6/Microsoft.PowerShell.Management/Wait-Process.md +++ b/reference/6/Microsoft.PowerShell.Management/Wait-Process.md @@ -32,7 +32,7 @@ Wait-Process [[-Timeout] ] -InputObject [] ## DESCRIPTION The **Wait-Process** cmdlet waits for one or more running processes to be stopped before accepting input. -In the Windows PowerShell console, this cmdlet suppresses the command prompt until the processes are stopped. +In the PowerShell console, this cmdlet suppresses the command prompt until the processes are stopped. You can specify a process by process name or process ID (PID), or pipe a process object to **Wait-Process**. **Wait-Process** works only on processes running on the local computer.