Advanced - VM Lifecycle Management - Administrator - Hyper-V

Table of Contents

Automatically Install File System Agent on New Virtual Machines

You can use a workflow to automatically install the File System Agent on your users' newly created virtual machines. When the File System Agent installation is complete, the user receives an e-mail that says the installation succeeded or failed. To configure this option, you must first deploy the workflow, and then set the alert.

Prerequisite

Downloading and Installing the Workflow

  1. Download the VM Package Deployment workflow from Software Store and install it on the CommServe computer.

    For instructions, see Download Workflows from Software Store.

  2. In the CommCell Browser, click Workflows.
  3. On the Workflows tab, right-click VM Package Deployment, and then click All Tasks | Deploy.

    The Deploy Workflow dialog box appears.

  4. In the Workflow Engine list, select the CommServe computer name, and then click OK.

Creating the Alert

  1. On the CommCell Console ribbon, click the Home tab, and then click Alert.
  2. Click Add.

    The Add Alert Wizard appears.

  3. On the General Information page, create a name and specify the alert category.
    1. In the Display Name box, type a name for the alert.
    2. In the Category list, click Operation.
    3. In the Type list, click Event View Events.
    4. Click Next.
  4. On the Entities Selection page, click the CommServe computer name, and then click Next.
  5. On the Threshold and Notification Criteria Selection page, specify the event code.
    1. Next to Event Code, select equals to, and then type 19:1610 in the box.
    2. Click Next.
  6. On the Notification Types Selection page, set the workflow type.
    1. Click the Workflow tab.
    2. On the Regular tab, next to jobId, in the Value cell, select <JOB ID>.
    3. Click Next.
  7. On the Summary page, click Finish.

    When the workflow completes, an e-mail is sent to the user who created the virtual machine.

Assigning Ownership to an Existing Virtual Machine

If you need to share ownership of an existing virtual machine (VM) with other users, then you must assign the Administrative Management capability to those users. First, create a user group that includes only the users who need to share ownership of the VM. Then, associate that user group with the client computer group associated with the Hyper-V client.

Before You Begin

Create a User Group that includes only the user or users who need to share ownership of an existing VM. For instructions, see Creating a New User Group.

About This Task

The Client Computer Group associated with the Hyper-V client is automatically created when you refresh Hyper-V hosts during the Hyper-V client creation operation.

Procedure

  1. In the CommCell Browser, expand Client Computer Groups.
  2. Right-click the Hyper-V Client Computer Group, and then click Properties.
  3. In the Client Group dialog box, click the Security tab.
  4. In the Available Groups list, select the name of the user group that includes the users who need ownership, and then click the right arrow button [>].
  5. In the Associated Groups list, select the user group that you just added, and then click Owner Capabilities.
  6. In the Client Owner Capabilities dialog box, in the Available Capabilities list, select Administrative Management, and then click Include.
  7. Click OK.
  8. Click OK.

    The users in the user group now share ownership of the VM.

Managing Virtual Machines Created without a VM Lifecycle Policy

You must have the Administrative Management capability to be able to do operations on the virtual machine.

To display virtual machines in the CommCell Console, see Displaying Backed Up Virtual Machines in the CommCell Console.

  1. In the CommCell Browser, go to Client Computers.
  2. Right-click a client or virtual machine and select Properties.
  3. On the Security tab:
    1. Enter the user name in the Client Owners box or a user group name in the User Groups box. 

      You can enter an Active Directory name in the form <domain_name>\<user_name>, an Active Directory user group in the form <domain_name>\<group_name>, or a CommCell user or group name.

    2. Click Client Owner Capabilities.
    3. Select from the Available Capabilities list, click Include to assign those capabilities for all client owners, and click OK.
  4. Click OK.

Customization Service

To use Windows templates for Microsoft Hyper-V virtual machines, you must install a customization service.

Prerequisite

Installing Customization Service for Windows Templates

  1. Log into Software Store and download CVcustomizeVM for WinX64.

    For instructions on accessing Software Store and downloading files, see Software Store.

  2. On each Windows template, paste CVcustomizeVM.exe into C:\windows\system32.
  3. To install the customization service, open Command Line and run the following command:

    CVCustomizeVM –install

Installing Customization Service for Linux Templates

  1. Log into Software Store and download CVcustomizeVM to each Linux virtual machine.

    For instructions on accessing Software Store and downloading files, see Software Store.

  2. To install the customization service, open Command Line on the virtual machine where the file was downloaded and run the following command:

    CVCustomizeVM –install

Setting the Deletion Date for Expired Virtual Machines

By default, expired virtual machines are automatically deleted after 5 days. However, you can specify the number of days after which the virtual machine is deleted with an Additional Setting.

  1. Open the CommCell Console.
  2. From the CommCell Browser, expand Client Computers.
  3. Right-click the <CommServe Client>, and then click Properties.
  4. Click Advanced.
  5. Click the Additional Settings tab.
  6. Click Add.
  7. In the Name box, type nVMDeletionGraceDays.
  8. From the Category list, select EventManager.
  9. From the Type list, select INTEGER.
  10. In the Value box, type the number of days that you want to wait before automatically deleting expired virtual machines. To never delete expired virtual machines, type 0.
  11. Click OK.