Invoke-History

 

Additional Resources for Invoke-History

 

Re-running a Previous Command

http://www.microsoft.com/technet/scriptcenter/topics/msh/cmdlets/invoke-history.mspx

 

 

SYNOPSIS

Runs commands from the session history.

 

SYNTAX

Invoke-History [[-iD] <string>] [-whatIf] [-confirm] [<CommonParameters>]

 

DETAILED DESCRIPTION

The Invoke-History cmdlet runs commands from the session history. You can pass objects representing the commands from Get-History to Invoke-History, or identify commands in the current history by using their ID number. To find the identification number of a command, use Get-History.

 

PARAMETERS

 

-iD <string>

Identifies 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 (most recent) command. The parameter name ("-id") is optional. To find the ID number of a command, use Get-History.

 

Required?

false

Position?

1

Default value

Previously executed pipeline

Accept pipeline input?  

true (ByPropertyName)

Accept wildcard characters? 

false

 

-whatIf

Describes what would happen if you executed the command without actually executing the command.

 

Required?

false

Position?

named

Default value

 

Accept pipeline input?  

false

Accept wildcard characters? 

false

 

-confirm

Prompts you for confirmation before executing the command.

 

Required?

false

Position?

named

Default value

 

Accept pipeline input?  

false

Accept wildcard characters? 

false

 

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, and -OutVariable. For more information, type, "get-help about_commonparameters".

 

INPUT TYPE

HistoryInfo Object

 

NOTES

 

For more information, type "Get-Help Invoke-History -detailed". For technical information, type "Get-Help Invoke-History -full".

 

The session history is a list of the commands entered during the session, along with the ID, which represents the order of execution, the status, and start and end times of the command. As you enter each command, Windows PowerShell adds it to the history so that you can reuse it.

 

For more information about the session history, type "get-help about_history".

 

When specifying multiple values for a parameter, use commas to separate the values. For example, "<parameter-name> <value1>, <value2>".

 

You can also refer to Invoke-History by its built-in aliases, "r" and "ihy". For more information, see About_Alias.

 

EXAMPLE 1

 

invoke-history

 

This command runs the last (most recent) command in the session history. You can abbreviate this command as "r" (think "repeat" or "rerun"), the alias for Invoke-History.

 

EXAMPLE 2

 

invoke-history -id 132

 

This 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 "Invoke-History 132", "ihy 132" or "r 132".

 

EXAMPLE 3

 

invoke-history get-pr

 

This 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, beginning with the most recent commands. This command uses the ID parameter, but omits the optional parameter name.

 

EXAMPLE 4

 

invoke-history (16..24), 27

 

This command runs commands 16 - 24 and 27. You can list multiple IDs and ID ranges separated by commas.

 

EXAMPLE 5

 

get-history -id 255 -count 7 | invoke-history

 

This command runs the 7 commands in the history that end with command 255 (typically 249 - 255). It uses the Get-Historycmdlet to retrieve the commands. The pipeline operator (|) passes the commands to Invoke-History, which executes them.

 

RELATED LINKS

Get-History

Add-History

 

 

 

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.