ActiveXperts Network Monitor ships with a large collection of PowerShell scripts and VBScript scripts to monitor and manage a network.
Use ActiveXperts Netork Monitor to monitor your virtualization servers, domains, computers and devices. It runs on a single Windows server, without agents required on the monitored systems. It has many built-in checks and also allows administrators to create custom checks using PowerShell, VBScript, WMI and SSH.
Invoke-History - Powershell 1.0 CmdLet
Microsoft Windows PowerShell is a command-line shell and scripting tool based on the Microsoft .NET Framework. It is designed for system administrators, engineers and developers to control and automate the administration of Windows and applications.
More than hundred command-line tools (so called "cmdlets") can be used to perform system administration tasks and Windows Management Instrumentation (WMI). These cmdlets are easy to use, with standard naming conventions and common parameters, and standard tools for piping, sorting, filtering, and formatting data and objects.
Invoke-History
Description ActiveXperts Network Monitor ships with a large collection of PowerShell scripts and VBScript scripts to monitor and manage a network.
Use ActiveXperts Netork Monitor to monitor your virtualization servers, domains, computers and devices. It runs on a single Windows server, without agents required on the monitored systems. It has many built-in checks and also allows administrators to create custom checks using PowerShell, VBScript, WMI and SSH. Usage Options -iD The ID number or the first few characters of a command from the session history. -whatIf Describe but dont actually execute the command. -confirm Prompt for confirmation before executing the command. CommonParameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutVariable. Example(s) Run the last (most recent) command: PS C:\>r Run the most recent get- command in the session history: PS C:\>invoke-history get- Run commands 5 - 15 and 17: (separate multiple IDs with commas) PS C:\>invoke-history (5..15), 17