Version 101 of the Microsoft Hyper-V Automation PowerPack introduces automation policies and automation actions for collecting diagnostic data from Microsoft Hyper-V systems. This is the first GA version of this PowerPack.
- Minimum Required SL1 Version: 8.10.0
Before You Install
Ensure that you are running version 8.10.0 or later of SL1 before installing " Microsoft Hyper-V Automation" PowerPack version 101.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
The following PowerPacks are prerequisites:
- Datacenter Automation Utilitiesv102 or later
- Microsoft: Hyper-V Serverv100 or later
- Windows PowerShell Automations v103 or later
To use this PowerPack, you must install the Diag-V module on your Hyper-V server(s). Refer to the user manual for instructions on how to install Diag-V.
Installation or Upgrade Process
To install version 101 of the Microsoft Hyper-V Automation PowerPack, perform the following steps:
- See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the 8.10.0 or later release.
- Familiarize yourself with the Known Issues for this release.
- Download the Microsoft Hyper-V Automation version 101 PowerPack to a local computer.
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. Import the Microsoft Hyper-V Automation version 101 PowerPack. For details on importing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
- Click the button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
- See the Run Book Automation manual for instructions on using Action Type contained in the new PowerPack.
See the Microsoft Automation PowerPacks manual for instructions on using the new PowerPack.
Features
This release includes the following features:
-
Enriches SL1 events for Hyper-V by automatically running diagnostic commands via remote PowerShell and adding the output to the SL1 event log or an associated incident.
- Four Automation Policies that connect events from the Microsoft: Hyper-V Server PowerPack with the included automation actions.
- Five automation actions that use the “Execute Remote PowerShell Request” action type to collect diagnostic data from Microsoft Hyper-V systems.
- A device group for Hyper-V devices that is used to scope the automation policies.
Enhancements and Issue Addressed
The following enhancements and addressed issues are included this release of the " Microsoft Hyper-V Automation" PowerPack:
- A new device group, "Microsoft Hyper-V Automation", has been added to the PowerPack.
- Two new automation policies have been added that connect events from the Microsoft: Windows Server PowerPack to Hyper-V automation actions:
- Hyper-V: CPU & Memory Diagnostic Commands
- Hyper-V: Disk & Storage Diagnostic Commands
- The "Get-VMReplicationStatus" cmdlet is not supported on all Hyper-V systems. The following changes have been made to separate this cmdlet into a separate automation action:
- A new automation action, “Hyper-V Guest Replication Diagnostic Command”, has been added, which runs the “Get-VMReplicationStatus” cmdlet.
- This cmdlet has been removed from the "Hyper-V Guest Storage and Replication Diagnostic Commands" automation action.
- The “Hyper-V Guest Storage and Replication Diagnostic Commands” automation action has been renamed “Hyper-V Guest Storage Diagnostic Commands”
- The "Hyper-V: Guests Below Threshold Diagnostic Commands" automation policy has been updated to include the new "Hyper-V Guest Replication Diagnostic Command" automation action.
- The "Hyper-V Log Collection" automation action has been updated to be compatible with the latest version of Diag-V.
- The "Format Table" cmdlet has been added to most automation actions to improve output formatting.
- The "Automation Utilities: Calculate Memory Size for Each Action" automation action has been added to all automation policies.
Known Issues
This release has no known issues.