HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

3. From the HP Server Automation (SA) “Devices” view, select the VMs.
4. Perform a “deactivate” and a “delete.”
New servers do not appear in the Unassigned pool
New servers do not appear in the infrastructure orchestration Unassigned pool.Issue
Resources are added to the Unassigned pool when infrastructure orchestration recognizes that they
are available and are licensed and configured correctly. By default, infrastructure orchestration
Possible cause
discovers and updates the available resources once an hour. Recently added resources are available
only in the infrastructure orchestration Unassigned pool after 1 to 2 hours (depending on the
discovery process of the other products, such as Insight Control virtual machine management, VCEM,
and Matrix OE).
Action
• From the Matrix OE management screen, select Tools→Logical Servers→Refresh to refresh Matrix
OE and activate the changes. From infrastructure orchestration screen, click on Servers tab and
then click Refresh to trigger a refresh of servers inventory.
• Perform a Systems Insight Manager Discovery. A server must be discovered at the Systems Insight
Manager level through the IP address discovery mechanism before it can be used in infrastructure
orchestration. VM Hosts must be registered with Insight Control virtual machine management.
• Ensure that servers are licensed for Matrix OE.
• Ensure that VMware ESX hosts have a full ESX license (not a base license).
“Could not retrieve mounted disk drive details” error when deploying a Hyper-V template
When customizing a Hyper-V VM, the error Could not retrieve mounted diskdrive
details is displayed.
Failure message
Insight Control virtual machine management requires that the boot disk for a Hyper-V VM must be
on the disk ide0:0.
Possible cause
Action
• Edit the template in SCVMM and change the boot disk to be in ide0:0, or
• Delete the virtual machine management template, change the original VM to set the boot disk
to ide0:0, then recreate the template.
Insight Control virtual machine management cannot manage a Hyper-V VM
A Hyper-V VM cannot be managed by virtual machine management.Failure message
After service creation, if a Hyper-V VM has single local disk in ide1:1 with the OS installed in
ide1:1, the VM is not managed by virtual machine management.
Possible cause
Action
• Edit the template in SCVMM and change the boot disk to be in ide0:0, or
• Delete the virtual machine management template, change the original VM to set the boot disk
to ide0:0, then recreate the template.
Service creation fails in the VM customization phase
Service creation fails in the VM customization phase.Issue
• Service creation fails when a virtual machine is created on a Hyper-V host.
• Service creation fails during the customization phase of deploying virtual machines. The VMware
fault fault.CustomizationPending.summary appears in the Insight Control virtual machine
management log files.
• Failure in customizing a Windows Server 2008 virtual machine. VM console has the following
error message:
Windows could not parse or process the unattend answer file for pass [specialize]. The settings
specified in the answer file cannot be applied. The error was detected while processing settings
Service creation 183