The hyperv provisioning adapter job deploys the hyperv.policy with the job. This policy contains the facts and constraints that the hyperv provisioning adapter job uses for checking whether the Hyper-V server host is registered to the Orchestration Server, and whether that host is up and running. By default, the optimal values are preset for the configuration of the job and joblets in the policy. We strongly recommend that you do not edit this policy.
The following additional configuration information is included in this section:
Section 6.3.1, Ensuring that the Orchestration Server Discovers Hyper-V VMs
Section 6.3.2, Configuring the Provisioning Adapter to Discover iSCSI Target Repositories
Section 6.3.3, Configuring the Provisioning Adapter for Sysprep
Section 6.3.4, Enabling a Remote Console Session for a Hyper-V VM
Section 6.3.5, Configuring Hyper-V Linux VMs to Enable Visibility of Added vDisks
For information about troubleshooting the hyperv provisioning adapter job, see Troubleshooting Hyper-V VM Provisioning Operations
in the NetIQ Cloud Manager 2.1.5 Troubleshooting Reference.
If you create a VM in your Hyper-V environment, but the path to that VM was not configured as the default path in the Hyper-V Manager, the Orchestration Server does not discover the VM until you edit the preferred path for the discovered repository where the VM resides. You can also create a new repository in the Orchestration Console with the preferred path to the Hyper-V VM.
If you are managing Windows VMs in a Hyper-V environment (clustered or non-clustered), the hyperv provisioning adapter must be configured to discover iSCSI target repositories in that environment if the VM is in a location other than C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks.
To configure the provisioning adapter for this use case:
In the Explorer tree of the Orchestration Console, select the group to expand the list of Repository Objects, select , then select the storage object associated to the Hyper-V cluster to open the admin view.
In the Info/Groups page of the admin view, find the field (the repository.preferredpath fact).
In the field, change the value to the path where the VM resides.
Remember that this field considers the information in the field (that is repository.location).
This is the location where the Orchestration Server searches for VM files for use in cloning and moving.Generally, it is a path like this:
C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
Click the icon to save the new configuration.
NOTE:If your Hyper-V environment is a Cluster Storage Volumes (CSV) environment, the VMs on the CSVs are automatically discovered by the hyperv provisioning adapter as separate repositories. Executing the action on these repositories discovers the VMs residing there.
As with other VMs provisioned by the Orchestration Server, sysprep does not work on Hyper-V Windows VMs until you set a value for the Admin Password fact (resource.provisioner.autoprep.sysprep.GuiUnattended.AdminPassword.value). For information about this fact, see Admin Password
in the NetIQ Cloud Manager 2.1.5 Orchestration Installation Guide.
If you invoke the VNC console for a Hyper-V VM (referred to as a “workload”) from the Cloud Manager Web Client, the VNC console does not launch.
Installing the Orchestration Agent on the VM and executing the action lets you launch a VNC session from Cloud Manager to the Hyper-V “workload” desktop.
To install the agent to the VM:
In Explorer tree of the Orchestration Console, select the VM that you want to observe in a remote session, then right-click and select .
Right-click the now idle VM, then select .
Right-click the VM, then select .
When the VM appears online again in the list of resources, right-click the VM again and select .
If you plan to add an additional vDisk to the Hyper-V Linux VM at some point, you need to further configure the VM so that the vDisk is visible. To do this, you need to install Microsoft Linux Integration Components for Linux. See the Microsoft downloads site for more information.