| external help file | keywords | locale | Module Name | ms.date | online version | schema | title |
|---|---|---|---|---|---|---|---|
System.Management.Automation.dll-Help.xml |
powershell,cmdlet |
en-us |
Microsoft.PowerShell.Core |
06/09/2017 |
2.0.0 |
Invoke-History |
Runs commands from the session history.
Invoke-History [[-Id] <String>] [-WhatIf] [-Confirm] [<CommonParameters>]
The Invoke-History cmdlet runs commands from the session history. You can pass objects representing the commands from Get-History to Invoke-History, or you can identify commands in the current history by using their ID number. To find the identification number of a command, use the Get-History cmdlet.
Invoke-HistoryThis command runs the last, or most recent, command in the session history.
You can abbreviate this command as r, the alias for Invoke-History.
Invoke-History -Id 132This command runs the command in the session history with ID 132.
Because the name of the Id parameter is optional, you can abbreviate this command as the following: Invoke-History 132, ihy 132, or r 132.
Invoke-History -ID get-prThis command runs the most recent Get-Process command in the session history. When you type characters for the Id parameter, Invoke-History runs the first command that it finds that matches the pattern, starting with the most recent commands.
16..24 | ForEach {Invoke-History -Id $_ }This command runs commands 16 through 24. Because you can list only one ID value, the command uses the ForEach-Object cmdlet to run the Invoke-History command one time for each ID value.
Get-History -Id 255 -Count 7 | ForEach {Invoke-History -Id $_.Id}This command runs the 7 commands in the history that end with command 255 (typically 249 through 255). It uses the Get-History cmdlet to retrieve the commands. Because you can list only one ID value, the command uses the ForEach-Object cmdlet to run the Invoke-History command once for each ID value.
Specifies the ID of a command in the history. You can type the ID number of the command or the first few characters of the command.
If you type characters, Invoke-History matches the most recent commands first. If you omit this parameter, Invoke-History runs the last, or most recent, command. To find the ID number of a command, use the Get-History cmdlet.
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 0
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: FalsePrompts you for confirmation before running the cmdlet.
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: FalseShows what would happen if the cmdlet runs. The cmdlet is not run.
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: FalseThis cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).
You can pipe a history ID to this cmdlet.
This cmdlet does not generate any output, but output might be generated by the commands that Invoke-History runs.
-
The session history is a list of the commands entered during the session together with the ID. The session history represents the order of execution, the status, and the start and end times of the command. As you enter each command, PowerShell adds it to the history so that you can reuse it. For more information about the session history, see about_History.
-
You can also refer to
Invoke-Historyby its built-in aliases,randihy. For more information, see about_Aliases.