Introduction to Microsoft Hyper-V Automations

Download this manual as a PDF file

This section describes how to use the run book automation policies, run book actions, and custom action types found in the "Microsoft Hyper-V Automations" PowerPack. Installation of the "Windows PowerShell Automations" PowerPack is required before using the "Microsoft Hyper-V Automations" PowerPack.

What is the Microsoft Hyper-V Automations PowerPack?

The "Microsoft Hyper-V Automations" PowerPack includes:

  • A set of automation actions that run diagnostic commands on Hyper-V systems via PowerShell
  • A set of automation policies that tie events from monitoring PowerPacks to the automation actions
  • A dynamic device group for Hyper-V devices that is used to scope the automation policies

The run book actions in this PowerPack are executed on the SL1 All-In-One Appliance or Data Collector.

In addition to using the standard content, you can use the content in the "Microsoft Hyper-V Automations" PowerPack to create your own automation policies that include the pre-defined actions that run different sets of diagnostic commands.

The "Microsoft Hyper-V Automations" PowerPack uses the supplied “Execute PowerShell Request” custom action type included with the "Windows PowerShell Automations" PowerPack.

Prerequisites

Before installing the "Microsoft Hyper-V Automations" PowerPack, you must perform the following actions:

  • Install the "Microsoft: Hyper-V Server" PowerPack and configure it to monitor your Hyper-V device(s)
  • Install version 103 or later of the "Windows PowerShell Automations" PowerPack
  • Install version 102 or later of the "Datacenter Automation Utilities" PowerPack
  • Install the Diag-V plug-in on your Hyper-V server. The plug-in is available here: https://gallery.technet.microsoft.com/scriptcenter/Diag-V-A-Hyper-V-0fe983e4

Installing the Microsoft Hyper-V Automations PowerPack

Before completing the steps in this section, you must import and install the latest version of the "Microsoft Hyper-V Automations" PowerPack.

By default, installing a new version of a PowerPack overwrites all content from a previous version of that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent new PowerPacks from overwriting local changes for some commonly customized fields. For more information, see the section on Global Settings.

Ensure that you are running version 12.1.2 or later of SL1 before installing this PowerPack. For details on upgrading SL1, see the relevant SL1 Platform Release Notes.

To download and install the PowerPack:

  1. Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
  2. In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
  3. Click the Actions button and choose Import PowerPack. The Import PowerPack dialog box appears.
  4. Click [Browse] and navigate to the PowerPack file from step 1.
  5. Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.
  6. Click Install. The PowerPack is added to the PowerPacks page.

If you exit the PowerPack Installer modal without installing the imported PowerPack, the imported PowerPack will not appear in the PowerPacks page. However, the imported PowerPack will appear in the Imported PowerPacks modal. This page appears when you click the Actions menu and select Install PowerPack.

Creating a Credential for Hyper-V Automation

The "Microsoft Hyper-V Automations" PowerPack uses the same credential that you created for the "Windows PowerShell Automations" PowerPack. Refer to the Creating a Credential section in the PowerShell Automations manual for more information.

If you have the "Microsoft: Windows Server" PowerPack installed and configured, you may skip this section.

For more information about configuring credentials in SL1, see Credentials.

For more information about substitution variables, see Appendix A: Run Book Variables.