Updates from: 09/10/2021 03:18:21
Service Microsoft Docs article Related commit history on GitHub Change details
ISE New Isesnippet (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/ISE/New-IseSnippet.md
is created, but an error message appears when Windows PowerShell tries to add th
snippet to the session. To use the new snippet (and other unsigned user-created snippets), change the execution policy, and then restart Windows PowerShell ISE.
-For more information about Windows PowerShell execution policies, see about_Execution_Policies.
+For more information about Windows PowerShell execution policies, see [about_Execution_Policies](../Microsoft.PowerShell.Core/About/about_Execution_Policies.md).
- To change a snippet, edit the snippet file. You can edit snippet files in the Script pane of Windows PowerShell ISE.
Microsoft.PowerShell.Core About Logging (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Logging.md
stopping the engine and providers, and executing PowerShell commands.
> Windows PowerShell versions 3.0, 4.0, 5.0, and 5.1 include **EventLog** > cmdlets for the Windows event logs. In those versions, to display the list of > **EventLog** cmdlets type: `Get-Command -Noun EventLog`. For more
-> information, see the cmdlet documentation and about_EventLogs for your
+> information, see the cmdlet documentation and [about_EventLogs](about_Eventlogs.md) for your
> version of Windows PowerShell. ## Viewing the PowerShell event log entries on Windows
Microsoft.PowerShell.Core About Pssnapins (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_PSSnapins.md
your session, you can use the export file only when you need the snap-ins.
To add the Add-PsSnapin command to your Windows PowerShell profile, open your profile, paste or type the command, and then save the profile. For more
-information, see about_Profiles.
+information, see [about_Profiles](about_Profiles.md).
To save the snap-ins from a session in console file (.psc1), use the Export-Console cmdlet. For example, to save the snap-ins in the current
information, see [about_EventLogs](about_EventLogs.md).
## KEYWORDS
-about_Snapins, about_Snap_ins, about_Snap-ins
+about_Snapins
+about_Snap_ins
+about_Snap-ins
Microsoft.PowerShell.Core About Remote (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Remote.md
remote computer where it terminates the remote command.
configurations, security issues, and other frequently asked questions, see [PowerShell Remoting FAQ](/powershell/scripting/learn/remoting/powershell-remoting-faq). -- For help in resolving remoting errors, see about_Remote_Troubleshooting.
+- For help in resolving remoting errors, see [about_Remote_Troubleshooting](about_Remote_Troubleshooting.md).
- For information about PSSessions and persistent connections, see [about_PSSessions](about_PSSessions.md).
Microsoft.PowerShell.Core About Remote Jobs (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Jobs.md
methods.
You can start an interactive session with a remote computer and then start a job during the interactive session. For more information about interactive
-sessions, see about_Remote, and see `Enter-PSSession`.
+sessions, see [about_Remote](about_Remote.md), and see `Enter-PSSession`.
The procedure for starting a job in an interactive session is almost identical to the procedure for starting a background job on the local computer. However,
Microsoft.PowerShell.Core About Scripts (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Scripts.md
C:\PS> $profileName
Microsoft.PowerShellISE_profile.ps1 ```
-For more information about scope, see about_Scopes.
+For more information about scope, see [about_Scopes](about_Scopes.md).
## Scripts in modules
Microsoft.PowerShell.Core About Windows Powershell ISE (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Windows_PowerShell_ISE.md
Windows PowerShell ISE introduces two new features in Windows PowerShell 4.0.
- Windows PowerShell ISE now supports both Windows PowerShell Workflow debugging and remote script debugging. For more Information, see
- about_Debuggers.
+ [about_Debuggers](about_Debuggers.md).
- IntelliSense support has been added for Windows PowerShell Desired State Configuration providers and configurations.
are in any Windows PowerShell host program. However, the items in your Windows
PowerShell console profiles are not available in Windows PowerShell ISE. Instructions for moving and reconfiguring your profiles are available in
-Windows PowerShell ISE Help and in about_Profiles.
+Windows PowerShell ISE Help and in [about_Profiles](about_Profiles.md).
## NOTES
Microsoft.PowerShell.Core Add Pssnapin (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/Add-PSSnapin.md
This cmdlet returns a PSSnapInInfo object that represents the snap-in if you spe
[How to Create a Windows PowerShell Snap-in](/powershell/scripting/developer/cmdlet/how-to-create-a-windows-powershell-snap-in). - `Add-PSSnapin` adds the snap-in only to the current session. To add the snap-in to all Windows PowerShell sessions, add it to your Windows PowerShell profile. For more information, see
- about_Profiles.
+ [about_Profiles](About/about_Profiles.md).
- You can add any snap-in that has been registered using the Microsoft .NET Framework install utility. For more information, see [How to Register Cmdlets, Providers, and Host Applications](/previous-versions//ms714644(v=vs.85)).
Microsoft.PowerShell.Core Export Console (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/Export-Console.md
You can use this cmdlet to save the snap-ins for use in future sessions.
To add the snap-ins in the .psc1 console file to a session, start Windows PowerShell (Powershell.exe) at the command line by using Cmd.exe or another Windows PowerShell session, and then use the *PSConsoleFile* parameter of Powershell.exe to specify the console file.
-For more information about Windows PowerShell snap-ins, see about_PSSnapins.
+For more information about Windows PowerShell snap-ins, see [about_PSSnapins](About/about_PSSnapins.md).
## EXAMPLES
It is also required when you use the *NoClobber* parameter to prevent the curren
If you omit this parameter, **Export-Console** overwrites the console file that was used most recently in this session. The path of the most recently used console file is stored in the value of the $ConsoleFileName automatic variable.
-For more information, see about_Automatic_Variables.
+For more information, see [about_Automatic_Variables](About/about_Automatic_Variables.md).
```yaml Type: System.String
This cmdlet creates a file that contains the exported aliases.
`powershell.exe -PsConsoleFile \<ConsoleFile\>.psc1` You can also save Windows PowerShell snap-ins for future sessions by adding an Add-PSSnapin command to your Windows PowerShell profile.
-For more information, see about_Profiles.
+For more information, see [about_Profiles](About/about_Profiles.md).
## RELATED LINKS
Microsoft.PowerShell.Core Stop Job (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/Stop-Job.md
The second command uses a pipeline operator to send the job in the `$j` variable
command uses the **PassThru** parameter to direct `Stop-Job` to return a job object. The job object display confirms that the state of the job is Stopped.
-For more information about remote background jobs, see about_Remote_Jobs.
+For more information about remote background jobs, see [about_Remote_Jobs](About/about_Remote_Jobs.md).
## PARAMETERS
Microsoft.PowerShell.Management Clear Item (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Clear-Item.md
Accept wildcard characters: True
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Clear Itemproperty (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Clear-ItemProperty.md
Accept wildcard characters: True
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Otherwise, this cmdlet does not generate any output.
You can use `Clear-ItemProperty` to delete the data in registry values without deleting the value. If the data type of the value is Binary or DWORD, clearing the data sets the value to zero. Otherwise, the value is empty.
-The `Clear-ItemProperty` cmdlet 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.
+The `Clear-ItemProperty` cmdlet 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](../Microsoft.PowerShell.Core/About/about_Providers.md).
## RELATED LINKS
Microsoft.PowerShell.Management Complete Transaction (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Complete-Transaction.md
When you commit a transaction, the commands in the transaction are finalized and
If the transaction includes multiple subscribers, to commit the transaction, you must enter one **Complete-Transaction** command for every Start-Transaction command. The **Complete-Transaction** cmdlet is one of a set of cmdlets that support the transactions feature in Windows PowerShell.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
## EXAMPLES
Microsoft.PowerShell.Management Convert Path (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Convert-Path.md
Accept wildcard characters: False
### -UseTransaction Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_transactions.
+For more information, see [about_transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Copy Itemproperty (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Copy-ItemProperty.md
Accept wildcard characters: False
### -UseTransaction Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Otherwise, this cmdlet does not generate any output.
## NOTES
-This cmdlet 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.
+This cmdlet 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](../Microsoft.PowerShell.Core/About/about_Providers.md).
## RELATED LINKS
Microsoft.PowerShell.Management Debug Process (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Debug-Process.md
The command uses the `$PID` automatic variable, which contains the process ID of
PowerShell process. Then, it uses a pipeline operator (`|`) to send the process ID to the `Debug-Process` cmdlet.
-For more information about the `$PID` automatic variable, see about_Automatic_Variables.
+For more information about the `$PID` automatic variable, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
### Example 7: Attach a debugger to the specified process on multiple computers
Microsoft.PowerShell.Management Get Itempropertyvalue (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Get-ItemPropertyValue.md
Accept wildcard characters: False
### -UseTransaction Includes the command in the active transaction. This parameter is valid only when a transaction is
-in progress. For more information, see about_Transactions.
+in progress. For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Get Location (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Get-Location.md
Accept wildcard characters: False
### -UseTransaction Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_transactions.
+For more information, see [about_transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Get Service (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Get-Service.md
This cmdlet returns objects that represent the services on the computer.
## NOTES
-You can also refer to **Get-Service** by its built-in alias, "gsv". For more information, see about_Aliases.
+You can also refer to **Get-Service** by its built-in alias, "gsv". For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md).
This cmdlet can display services only when the current user has permission to see them. If this cmdlet does not display services, you might not have permission to see them.
Microsoft.PowerShell.Management Get Transaction (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Get-Transaction.md
If you start one or more independent transactions (by using the Independent para
When all active transactions have either been rolled back or committed, this cmdlet shows the transaction that was most recently active in the session. This cmdlet is one of a set of cmdlets that support the transactions feature in Windows PowerShell.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
## EXAMPLES
Microsoft.PowerShell.Management Invoke Item (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Invoke-Item.md
Accept wildcard characters: False
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_transactions.
+For more information, see [about_transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
However, output might be generated by the item that it invokes.
## NOTES
-This cmdlet 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.
+This cmdlet 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](../Microsoft.PowerShell.Core/About/about_Providers.md).
## RELATED LINKS
Microsoft.PowerShell.Management Invoke Wmimethod (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Invoke-WmiMethod.md
use the Receive-Job cmdlet.
To use this parameter with remote computers, the local and remote computers must be configured for remoting. Additionally, you must start Windows PowerShell by using the Run as administrator option
-in Windows Vista and later versions of Windows. For more information, see about_Remote_Requirements.
+in Windows Vista and later versions of Windows. For more information, see [about_Remote_Requirements](../Microsoft.PowerShell.Core/About/about_Remote_Requirements.md).
-For more information about Windows PowerShell background jobs, see about_Jobs and about_Remote_Jobs.
+For more information about Windows PowerShell background jobs, see [about_Jobs](../Microsoft.PowerShell.Core/About/about_Jobs.md) and about_Remote_Jobs.
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Move Item (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Move-Item.md
Accept wildcard characters: True
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Move Itemproperty (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Move-ItemProperty.md
Accept wildcard characters: True
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management New Itemproperty (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/New-ItemProperty.md
Accept wildcard characters: False
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Register Wmievent (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Register-WmiEvent.md
When you use the **Action** parameter, `Register-WmiEvent` returns a background
the event action. You can use the **Job** cmdlets, such as `Get-Job` and `Receive-Job`, to manage the event job.
-For more information, see about_Jobs.
+For more information, see [about_Jobs](../Microsoft.PowerShell.Core/About/about_Jobs.md).
### Example 4: Register for events on a remote computer
event is raised instead of sending the event to the event queue. Enclose the com
The value of **Action** can include the `$Event`, `$EventSubscriber`, `$Sender`, `$EventArgs`, and `$Args` automatic variables, which provide information about the event to the **Action** script
-block. For more information, see about_Automatic_Variables.
+block. For more information, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
When you specify an action, `Register-WmiEvent` returns an event job object that represents that action. You can use the cmdlets that contain the **Job** noun (the **Job** cmdlets) to manage the
Microsoft.PowerShell.Management Remove Itemproperty (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Remove-ItemProperty.md
Accept wildcard characters: True
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
This cmdlet does not return any output.
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.
+`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](../Microsoft.PowerShell.Core/About/about_Providers.md).
## RELATED LINKS
Microsoft.PowerShell.Management Remove Psdrive (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Remove-PSDrive.md
Accept wildcard characters: False
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Remove Wmiobject (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Remove-WmiObject.md
To get the job results, use the Receive-Job cmdlet.
To use this parameter for remote computers, the local and remote computers must be configured for remoting. Start Windows PowerShell by using the Run as administrator option.
-For more information, see about_Remote_Requirements.
+For more information, see [about_Remote_Requirements](../Microsoft.PowerShell.Core/About/about_Remote_Requirements.md).
-For more information about Windows PowerShell background jobs, see about_Jobs and about_Remote_Jobs.
+For more information about Windows PowerShell background jobs, see [about_Jobs](../Microsoft.PowerShell.Core/About/about_Jobs.md) and about_Remote_Jobs.
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Reset Computermachinepassword (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Reset-ComputerMachinePassword.md
PS C:\> Invoke-Command -ComputerName "Server01" -ScriptBlock {Reset-ComputerMach
This command uses the Invoke-Command cmdlet to run a **Reset-ComputerMachinePassword** command on the Server01 remote computer.
-For more information about remote commands in Windows PowerShell, see about_Remote and **Invoke-Command**.
+For more information about remote commands in Windows PowerShell, see [about_Remote](../Microsoft.PowerShell.Core/About/about_Remote.md) and **Invoke-Command**.
## PARAMETERS
Microsoft.PowerShell.Management Resolve Path (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Resolve-Path.md
Accept wildcard characters: False
### -UseTransaction Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_transactions.
+For more information, see [about_transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Set Location (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Set-Location.md
Accept wildcard characters: False
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Set Wmiinstance (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Set-WmiInstance.md
To get the job results, use the Receive-Job cmdlet.
To use this parameter together with remote computers, the local and remote computers must be configured for remoting. Additionally, you must start Windows PowerShell by using the Run as administrator option in Windows Vista and later versions of the Windows operating system.
-For more information, see about_Remote_Requirements.
+For more information, see [about_Remote_Requirements](../Microsoft.PowerShell.Core/About/about_Remote_Requirements.md).
-For more information about Windows PowerShell background jobs, see about_Jobs and about_Remote_Jobs.
+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).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Management Split Path (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Split-Path.md
Accept wildcard characters: False
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
These include the FileSystem, Registry, and Certificate providers.
**Split-Path** 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.
+For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
## RELATED LINKS
Microsoft.PowerShell.Management Start Transaction (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Start-Transaction.md
Only one transaction can be active at a time.
If you start a new, independent transaction while a transaction is in progress, the new transaction becomes the active transaction, and you must commit or roll back the new transaction before you make any changes to the original transaction. **Start-Transaction** cmdlet is one of a set of cmdlets that support the transactions feature in Windows PowerShell.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
## EXAMPLES
Microsoft.PowerShell.Management Stop Process (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Stop-Process.md
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 refer to **Stop-Process** by its built-in aliases, **kill** and **spps**. For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md).
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-CimInstance` and the WMI SDK.
Microsoft.PowerShell.Management Test Computersecurechannel (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Test-ComputerSecureChannel.md
VERBOSE: "The secure channel between 'SERVER01' and 'net.fabrikam.com' is alive
``` This command uses the *Verbose* common parameter to request detailed messages about the operation.
-For more information about *Verbose*, see about_CommonParameters.
+For more information about *Verbose*, see [about_CommonParameters](../Microsoft.PowerShell.Core/About/about_CommonParameters.md).
### Example 5: Test a connection before you run a script
Microsoft.PowerShell.Management Test Path (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Test-Path.md
whether the syntax of the path is correct. In this case, the path is `$False`, b
correct `$True`. These commands use `$profile`, the automatic variable that points to the location for the profile, even if the profile does not exist.
-For more information about automatic variables, see about_Automatic_Variables.
+For more information about automatic variables, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
### Example 3: Check whether there are any files besides a specified type
Microsoft.PowerShell.Management Undo Transaction (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Undo-Transaction.md
By default, transactions are rolled back automatically if any command in the tra
However, transactions can be started by using a different rollback preference and you can use this cmdlet to roll back the active transaction at any time. The **Undo-Transaction** cmdlet is one of a set of cmdlets that support the transactions feature in Windows PowerShell.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
## EXAMPLES
Microsoft.PowerShell.Management Use Transaction (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Management/Use-Transaction.md
The script block can contain only transaction-enabled .NET Framework objects, su
The *UseTransaction* parameter, which is optional for most cmdlets, is required when you use this cmdlet. **Use-Transaction** is one of a set of cmdlets that support the transactions feature in Windows PowerShell.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
## EXAMPLES
Accept wildcard characters: False
### -UseTransaction Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_transactions.
+For more information, see [about_transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Security Get Acl (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Security/Get-Acl.md
Accept wildcard characters: False
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Security Set Acl (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Security/Set-Acl.md
Accept wildcard characters: False
Includes the command in the active transaction. This parameter is valid only when a transaction is in progress.
-For more information, see about_Transactions.
+For more information, see [about_Transactions](../Microsoft.PowerShell.Core/About/about_Transactions.md).
```yaml Type: System.Management.Automation.SwitchParameter
Microsoft.PowerShell.Utility Clear Variable (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Utility/Clear-Variable.md
The acceptable values for this parameter are:
You can also use a number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent). Local is the default.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Otherwise, this cmdlet does not generate any output.
It does not create a variable with a null value. You can also refer to **Clear-Variable** by its built-in alias, clv.
-For more information, see about_Aliases.
+For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md).
*
Microsoft.PowerShell.Utility Convertto Xml (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Utility/ConvertTo-Xml.md
For example, if the object's properties also contain objects, to save an XML rep
properties of the contained objects, you must specify a depth of 2. The default value can be overridden for the object type in the Types.ps1xml files. For more
-information, see about_Types.ps1xml.
+information, see [about_Types.ps1xml](../Microsoft.PowerShell.Core/About/about_Types.ps1xml.md).
```yaml Type: System.Int32
Microsoft.PowerShell.Utility Export Alias (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Utility/Export-Alias.md
It uses the **As** parameter with a value of Script to generate a file that cont
The second command adds the aliases in the Alias.ps1 file to the CurrentUser-CurrentHost profile. The path to the profile is saved in the `$Profile` variable. The command uses the `Get-Content` cmdlet to get the aliases from the Alias.ps1 file and the `Add-Content` cmdlet to add them to the profile.
-For more information, see about_Profiles.
+For more information, see [about_Profiles](../Microsoft.PowerShell.Core/About/about_Profiles.md).
The third and fourth commands add the aliases in the Alias.ps1 file to a remote session on the Server01 computer. The third command uses the `New-PSSession` cmdlet to create the session.
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes where 0 is the current scope and 1 is its parent) The default value is Local.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Utility Get Alias (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Utility/Get-Alias.md
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent) Local is the default.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Utility Import Alias (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Utility/Import-Alias.md
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent) The default is Local.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
PSScheduledJob Add Jobtrigger (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Add-JobTrigger.md
To create job triggers for the value of the *Trigger* parameter, use the New-Job
**Add-JobTrigger** is one of a collection of job scheduling cmdlets in the **PSScheduledJob** module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Disable Jobtrigger (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Disable-JobTrigger.md
If you disable a scheduled job or disable all job triggers of a scheduled job, y
**Disable-ScheduledJob** is one of a collection of job scheduling cmdlets in the **PSScheduledJob** module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Disable Scheduledjob (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Disable-ScheduledJob.md
To re-enable the scheduled job, use the Enable-ScheduledJob cmdlet.
**Disable-ScheduledJob** is one of a collection of job scheduling cmdlets in the **PSScheduledJob** module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Enable Jobtrigger (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Enable-JobTrigger.md
To enable a job trigger, the **Enable-JobTrigger** cmdlet sets the Enabled prope
**Enable-ScheduledJob** is one of a collection of job scheduling cmdlets in the **PSScheduledJob** module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Enable Scheduledjob (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Enable-ScheduledJob.md
To enable a scheduled job, the **Enable-ScheduledJob** cmdlet sets the Enabled p
**Enabled-ScheduledJob** is one of a collection of job scheduling cmdlets in the **PSScheduledJob** module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Get Jobtrigger (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Get-JobTrigger.md
You can identify the scheduled jobs by their names or identification numbers, or
**Get-JobTrigger** is one of a collection of job scheduling cmdlets in the PSScheduledJob module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Get Scheduledjob (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Get-ScheduledJob.md
You can use the parameters of **Get-ScheduledJob** to get scheduled jobs by ID o
**Get-ScheduledJob** is one of a collection of job scheduling cmdlets in the **PSScheduledJob** module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
You cannot pipe input to **Get-ScheduledJob**.
## NOTES
-* Each scheduled job is saved in a subdirectory of the $home\AppData\Local\Microsoft\Windows\PowerShell\ScheduledJobs directory on the local computer. The subdirectory is named for the scheduled job and contains the XML file for the scheduled job and records of its execution history. For more information about scheduled jobs on disk, see about_Scheduled_Jobs_Advanced.
+* Each scheduled job is saved in a subdirectory of the $home\AppData\Local\Microsoft\Windows\PowerShell\ScheduledJobs directory on the local computer. The subdirectory is named for the scheduled job and contains the XML file for the scheduled job and records of its execution history. For more information about scheduled jobs on disk, see [about_Scheduled_Jobs_Advanced](About/about_Scheduled_Jobs_Advanced.md).
* Scheduled jobs that you create in Windows PowerShell appear in Task Scheduler in the Task Scheduler Library\Microsoft\Windows\PowerShell\ScheduledJobs folder. You can use Task Scheduler to view and edit the scheduled job. * You can use Task Scheduler, the SchTasks.exe command-line tool, and the Task Scheduler cmdlets to manage scheduled jobs that you create with the Scheduled Job cmdlets. However, you cannot use the Scheduled Job cmdlets to manage tasks that you create in Task Scheduler.
PSScheduledJob Get Scheduledjoboption (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Get-ScheduledJobOption.md
You can identify scheduled jobs by their names or identification numbers, or by
**Get-ScheduledJobOption** is one of a collection of job scheduling cmdlets in the PSScheduledJob module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob New Jobtrigger (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/New-JobTrigger.md
These options, which have the same valid and default values as the corresponding
**New-JobTrigger** is one of a collection of job scheduling cmdlets in the PSScheduledJob module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob New Scheduledjoboption (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/New-ScheduledJobOption.md
Scheduled jobs run only when all conditions set for their execution are satisfie
**New-ScheduledJobOption** is one of a collection of job scheduling cmdlets in the PSScheduledJob module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Remove Jobtrigger (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Remove-JobTrigger.md
By default, **Remove-JobTrigger** deletes all job triggers of a scheduled job.
**Remove-JobTrigger** is one of a collection of job scheduling cmdlets in the PSScheduledJob module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Set Jobtrigger (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Set-JobTrigger.md
All other properties of the original job trigger are retained.
**Set-JobTrigger** is one of a collection of job scheduling cmdlets in the PSScheduledJob module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Set Scheduledjob (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Set-ScheduledJob.md
The *Trigger* parameter is optional, so you can add triggers when you create the
**Set-ScheduledJob** is one of a collection of job scheduling cmdlets in the PSScheduledJob module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
The command uses the Get-ScheduledJob cmdlet to get the BackupArchive scheduled
A pipeline operator (|) sends the job to the **Set-ScheduledJob** cmdlet to change it. The **Set-ScheduledJob** cmdlet uses the *ClearExecutionHistory* parameter to delete the execution history and saved results.
-For more information about the execution history and saved job results of scheduled jobs, see about_Scheduled_Jobs.
+For more information about the execution history and saved job results of scheduled jobs, see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
### Example 3: Change scheduled jobs on a remote computer
PSScheduledJob Set Scheduledjoboption (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Set-ScheduledJobOption.md
These options to not apply when you use the Start-Job cmdlet to start a schedule
**Set-ScheduledJobOption** is one of a collection of job scheduling cmdlets in the PSScheduledJob module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSScheduledJob Unregister Scheduledjob (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSScheduledJob/Unregister-ScheduledJob.md
You can use the parameters of **Unregister-ScheduledJob** to delete scheduled jo
**Unregister-ScheduledJob** is one of a collection of job scheduling cmdlets in the PSScheduledJob module that is included in Windows PowerShell. For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module.
-Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see about_Scheduled_Jobs.
+Import the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
This cmdlet was introduced in Windows PowerShell 3.0.
PSWorkflow About Activitycommonparameters (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSWorkflow/About/about_ActivityCommonParameters.md
unique to activities.
For information about the workflow common parameters, see about_WorkflowCommonParameters. For information about the Windows PowerShell
-common parameters, see about_CommonParameters.
+common parameters, see [about_CommonParameters](../../Microsoft.PowerShell.Core/About/about_CommonParameters.md).
### LIST OF ACTIVITY COMMON PARAMETERS
PSWorkflow About Parallel (5.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSWorkflow/About/about_Parallel.md
workflow Test-Workflow
Running commands in parallel is very efficient and reduces the time it takes to complete a workflow significantly.
-To run selected commands in a Parallel script block in sequential order, use the Sequence keyword. For more information, see about_Sequence.
+To run selected commands in a Parallel script block in sequential order, use the Sequence keyword. For more information, see [about_Sequence](about_Sequence.md).
To run a Parallel script block on items in a collection, use the ForEach or ForEach -Parallel keywords.
Microsoft.PowerShell.Core About Remote (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Remote.md
remote computer where it terminates the remote command.
configurations, security issues, and other frequently asked questions, see [PowerShell Remoting FAQ](/powershell/scripting/learn/remoting/powershell-remoting-faq). -- For help in resolving remoting errors, see about_Remote_Troubleshooting.
+- For help in resolving remoting errors, see [about_Remote_Troubleshooting](about_Remote_Troubleshooting.md).
- For information about PSSessions and persistent connections, see [about_PSSessions](about_PSSessions.md).
Microsoft.PowerShell.Core About Remote Jobs (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Jobs.md
methods.
You can start an interactive session with a remote computer and then start a job during the interactive session. For more information about interactive
-sessions, see about_Remote, and see `Enter-PSSession`.
+sessions, see [about_Remote](about_Remote.md), and see `Enter-PSSession`.
The procedure for starting a job in an interactive session is almost identical to the procedure for starting a background job on the local computer. However,
Microsoft.PowerShell.Core About Scripts (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Scripts.md
C:\PS> $profileName
Microsoft.PowerShellISE_profile.ps1 ```
-For more information about scope, see about_Scopes.
+For more information about scope, see [about_Scopes](about_Scopes.md).
## Scripts in modules
Microsoft.PowerShell.Core Stop Job (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/Stop-Job.md
The second command uses a pipeline operator to send the job in the `$j` variable
command uses the **PassThru** parameter to direct `Stop-Job` to return a job object. The job object display confirms that the state of the job is Stopped.
-For more information about remote background jobs, see about_Remote_Jobs.
+For more information about remote background jobs, see [about_Remote_Jobs](About/about_Remote_Jobs.md).
## PARAMETERS
Microsoft.PowerShell.Management Debug Process (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Management/Debug-Process.md
The command uses the `$PID` automatic variable, which contains the process ID of
PowerShell process. Then, it uses a pipeline operator (`|`) to send the process ID to the `Debug-Process` cmdlet.
-For more information about the `$PID` automatic variable, see about_Automatic_Variables.
+For more information about the `$PID` automatic variable, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
### Example 7: Attach a debugger to a process that uses the InputObject parameter
Microsoft.PowerShell.Management Split Path (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Management/Split-Path.md
These include the FileSystem, Registry, and Certificate providers.
**Split-Path** 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.
+For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
## RELATED LINKS
Microsoft.PowerShell.Management Stop Process (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Management/Stop-Process.md
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 refer to **Stop-Process** by its built-in aliases, **kill** and **spps**. For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md).
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-CimInstance` and the WMI SDK.
Microsoft.PowerShell.Management Test Path (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Management/Test-Path.md
whether the syntax of the path is correct. In this case, the path is `$False`, b
correct `$True`. These commands use `$profile`, the automatic variable that points to the location for the profile, even if the profile does not exist.
-For more information about automatic variables, see about_Automatic_Variables.
+For more information about automatic variables, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
### Example 3: Check whether there are any files besides a specified type
Microsoft.PowerShell.Utility Clear Variable (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Utility/Clear-Variable.md
The acceptable values for this parameter are:
You can also use a number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent). Local is the default.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Otherwise, this cmdlet does not generate any output.
It does not create a variable with a null value. You can also refer to **Clear-Variable** by its built-in alias, clv.
-For more information, see about_Aliases.
+For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md).
*
Microsoft.PowerShell.Utility Convertto Xml (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Utility/ConvertTo-Xml.md
For example, if the object's properties also contain objects, to save an XML rep
properties of the contained objects, you must specify a depth of 2. The default value can be overridden for the object type in the Types.ps1xml files. For more
-information, see about_Types.ps1xml.
+information, see [about_Types.ps1xml](../Microsoft.PowerShell.Core/About/about_Types.ps1xml.md).
```yaml Type: System.Int32
Microsoft.PowerShell.Utility Export Alias (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Utility/Export-Alias.md
It uses the **As** parameter with a value of Script to generate a file that cont
The second command adds the aliases in the Alias.ps1 file to the CurrentUser-CurrentHost profile. The path to the profile is saved in the `$Profile` variable. The command uses the `Get-Content` cmdlet to get the aliases from the Alias.ps1 file and the `Add-Content` cmdlet to add them to the profile.
-For more information, see about_Profiles.
+For more information, see [about_Profiles](../Microsoft.PowerShell.Core/About/about_Profiles.md).
The third and fourth commands add the aliases in the Alias.ps1 file to a remote session on the Server01 computer. The third command uses the `New-PSSession` cmdlet to create the session.
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes where 0 is the current scope and 1 is its parent) The default value is Local.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Utility Get Alias (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Utility/Get-Alias.md
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent) Local is the default.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Utility Import Alias (7.0) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Utility/Import-Alias.md
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent) The default is Local.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Core About Remote (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Remote.md
remote computer where it terminates the remote command.
configurations, security issues, and other frequently asked questions, see [PowerShell Remoting FAQ](/powershell/scripting/learn/remoting/powershell-remoting-faq). -- For help in resolving remoting errors, see about_Remote_Troubleshooting.
+- For help in resolving remoting errors, see [about_Remote_Troubleshooting](about_Remote_Troubleshooting.md).
- For information about PSSessions and persistent connections, see [about_PSSessions](about_PSSessions.md).
Microsoft.PowerShell.Core About Remote Jobs (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Jobs.md
methods.
You can start an interactive session with a remote computer and then start a job during the interactive session. For more information about interactive
-sessions, see about_Remote, and see `Enter-PSSession`.
+sessions, see [about_Remote](about_Remote.md), and see `Enter-PSSession`.
The procedure for starting a job in an interactive session is almost identical to the procedure for starting a background job on the local computer. However,
Microsoft.PowerShell.Core About Scripts (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Scripts.md
C:\PS> $profileName
Microsoft.PowerShellISE_profile.ps1 ```
-For more information about scope, see about_Scopes.
+For more information about scope, see [about_Scopes](about_Scopes.md).
## Scripts in modules
Microsoft.PowerShell.Core Stop Job (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/Stop-Job.md
The second command uses a pipeline operator to send the job in the `$j` variable
command uses the **PassThru** parameter to direct `Stop-Job` to return a job object. The job object display confirms that the state of the job is Stopped.
-For more information about remote background jobs, see about_Remote_Jobs.
+For more information about remote background jobs, see [about_Remote_Jobs](About/about_Remote_Jobs.md).
## PARAMETERS
Microsoft.PowerShell.Management Debug Process (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Management/Debug-Process.md
The command uses the `$PID` automatic variable, which contains the process ID of
PowerShell process. Then, it uses a pipeline operator (`|`) to send the process ID to the `Debug-Process` cmdlet.
-For more information about the `$PID` automatic variable, see about_Automatic_Variables.
+For more information about the `$PID` automatic variable, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
### Example 7: Attach a debugger to a process that uses the InputObject parameter
Microsoft.PowerShell.Management Split Path (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Management/Split-Path.md
When you specify the **IsAbsolute** parameter, `Split-Path` returns a **Boolean*
Registry, and Certificate providers. - `Split-Path` 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.
+ available in your session, type `Get-PSProvider`. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
## RELATED LINKS
Microsoft.PowerShell.Management Stop Process (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Management/Stop-Process.md
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 refer to **Stop-Process** by its built-in aliases, **kill** and **spps**. For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md).
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-CimInstance` and the WMI SDK.
Microsoft.PowerShell.Management Test Path (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Management/Test-Path.md
whether the syntax of the path is correct. In this case, the path is `$False`, b
correct `$True`. These commands use `$profile`, the automatic variable that points to the location for the profile, even if the profile does not exist.
-For more information about automatic variables, see about_Automatic_Variables.
+For more information about automatic variables, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
### Example 3: Check whether there are any files besides a specified type
Microsoft.PowerShell.Utility Clear Variable (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Clear-Variable.md
The acceptable values for this parameter are:
You can also use a number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent). Local is the default.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Otherwise, this cmdlet does not generate any output.
It does not create a variable with a null value. You can also refer to **Clear-Variable** by its built-in alias, clv.
-For more information, see about_Aliases.
+For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md).
*
Microsoft.PowerShell.Utility Convertto Xml (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/ConvertTo-Xml.md
For example, if the object's properties also contain objects, to save an XML rep
properties of the contained objects, you must specify a depth of 2. The default value can be overridden for the object type in the Types.ps1xml files. For more
-information, see about_Types.ps1xml.
+information, see [about_Types.ps1xml](../Microsoft.PowerShell.Core/About/about_Types.ps1xml.md).
```yaml Type: System.Int32
Microsoft.PowerShell.Utility Export Alias (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Export-Alias.md
It uses the **As** parameter with a value of Script to generate a file that cont
The second command adds the aliases in the Alias.ps1 file to the CurrentUser-CurrentHost profile. The path to the profile is saved in the `$Profile` variable. The command uses the `Get-Content` cmdlet to get the aliases from the Alias.ps1 file and the `Add-Content` cmdlet to add them to the profile.
-For more information, see about_Profiles.
+For more information, see [about_Profiles](../Microsoft.PowerShell.Core/About/about_Profiles.md).
The third and fourth commands add the aliases in the Alias.ps1 file to a remote session on the Server01 computer. The third command uses the `New-PSSession` cmdlet to create the session.
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes where 0 is the current scope and 1 is its parent) The default value is Local.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Utility Get Alias (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Get-Alias.md
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent) Local is the default.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Utility Import Alias (7.1) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Utility/Import-Alias.md
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent) The default is Local.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Core About Remote (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Remote.md
remote computer where it terminates the remote command.
configurations, security issues, and other frequently asked questions, see [PowerShell Remoting FAQ](/powershell/scripting/learn/remoting/powershell-remoting-faq). -- For help in resolving remoting errors, see about_Remote_Troubleshooting.
+- For help in resolving remoting errors, see [about_Remote_Troubleshooting](about_Remote_Troubleshooting.md).
- For information about PSSessions and persistent connections, see [about_PSSessions](about_PSSessions.md).
Microsoft.PowerShell.Core About Remote Jobs (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Remote_Jobs.md
methods.
You can start an interactive session with a remote computer and then start a job during the interactive session. For more information about interactive
-sessions, see about_Remote, and see `Enter-PSSession`.
+sessions, see [about_Remote](about_Remote.md), and see `Enter-PSSession`.
The procedure for starting a job in an interactive session is almost identical to the procedure for starting a background job on the local computer. However,
Microsoft.PowerShell.Core About Scripts (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Scripts.md
C:\PS> $profileName
Microsoft.PowerShellISE_profile.ps1 ```
-For more information about scope, see about_Scopes.
+For more information about scope, see [about_Scopes](about_Scopes.md).
## Scripts in modules
Microsoft.PowerShell.Core Stop Job (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/Stop-Job.md
The second command uses a pipeline operator to send the job in the `$j` variable
command uses the **PassThru** parameter to direct `Stop-Job` to return a job object. The job object display confirms that the state of the job is Stopped.
-For more information about remote background jobs, see about_Remote_Jobs.
+For more information about remote background jobs, see [about_Remote_Jobs](About/about_Remote_Jobs.md).
## PARAMETERS
Microsoft.PowerShell.Management Debug Process (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Management/Debug-Process.md
The command uses the `$PID` automatic variable, which contains the process ID of
PowerShell process. Then, it uses a pipeline operator (`|`) to send the process ID to the `Debug-Process` cmdlet.
-For more information about the `$PID` automatic variable, see about_Automatic_Variables.
+For more information about the `$PID` automatic variable, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
### Example 7: Attach a debugger to a process that uses the InputObject parameter
Microsoft.PowerShell.Management Split Path (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Management/Split-Path.md
When you specify the **IsAbsolute** parameter, `Split-Path` returns a **Boolean*
Registry, and Certificate providers. - `Split-Path` 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.
+ available in your session, type `Get-PSProvider`. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
## RELATED LINKS
Microsoft.PowerShell.Management Stop Process (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Management/Stop-Process.md
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 refer to **Stop-Process** by its built-in aliases, **kill** and **spps**. For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md).
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-CimInstance` and the WMI SDK.
Microsoft.PowerShell.Management Test Path (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Management/Test-Path.md
whether the syntax of the path is correct. In this case, the path is `$False`, b
correct `$True`. These commands use `$profile`, the automatic variable that points to the location for the profile, even if the profile does not exist.
-For more information about automatic variables, see about_Automatic_Variables.
+For more information about automatic variables, see [about_Automatic_Variables](../Microsoft.PowerShell.Core/About/about_Automatic_Variables.md).
### Example 3: Check whether there are any files besides a specified type
Microsoft.PowerShell.Utility Clear Variable (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Clear-Variable.md
The acceptable values for this parameter are:
You can also use a number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent). Local is the default.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Otherwise, this cmdlet does not generate any output.
It does not create a variable with a null value. You can also refer to **Clear-Variable** by its built-in alias, clv.
-For more information, see about_Aliases.
+For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md).
*
Microsoft.PowerShell.Utility Convertto Xml (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/ConvertTo-Xml.md
For example, if the object's properties also contain objects, to save an XML rep
properties of the contained objects, you must specify a depth of 2. The default value can be overridden for the object type in the Types.ps1xml files. For more
-information, see about_Types.ps1xml.
+information, see [about_Types.ps1xml](../Microsoft.PowerShell.Core/About/about_Types.ps1xml.md).
```yaml Type: System.Int32
Microsoft.PowerShell.Utility Export Alias (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Export-Alias.md
It uses the **As** parameter with a value of Script to generate a file that cont
The second command adds the aliases in the Alias.ps1 file to the CurrentUser-CurrentHost profile. The path to the profile is saved in the `$Profile` variable. The command uses the `Get-Content` cmdlet to get the aliases from the Alias.ps1 file and the `Add-Content` cmdlet to add them to the profile.
-For more information, see about_Profiles.
+For more information, see [about_Profiles](../Microsoft.PowerShell.Core/About/about_Profiles.md).
The third and fourth commands add the aliases in the Alias.ps1 file to a remote session on the Server01 computer. The third command uses the `New-PSSession` cmdlet to create the session.
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes where 0 is the current scope and 1 is its parent) The default value is Local.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Utility Get Alias (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Get-Alias.md
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent) Local is the default.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String
Microsoft.PowerShell.Utility Import Alias (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Utility/Import-Alias.md
The acceptable values for this parameter are:
- A number relative to the current scope (0 through the number of scopes, where 0 is the current scope and 1 is its parent) The default is Local.
-For more information, see about_Scopes.
+For more information, see [about_Scopes](../Microsoft.PowerShell.Core/About/about_Scopes.md).
```yaml Type: System.String