HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

• Verify the source VM being used to create the template has been stopped or paused (not
suspended) before creating the template.
• Verify the source VM being used to create the template has been properly shut down before
creating the template. When guests are not gracefully shutdown or halted it can cause
customization phases to fail.
• Verify that the product key (and any other configuration option) being used in the HPIO
sysprep file functions with the VM by performing the following test. In vCenter or vSphere:
◦ Locate the original VM that was used to create the Insight Control virtual machine
management template that is experiencing the failure.
◦ Right-click the VM, and select Template→Clone to Template. This action creates a vSphere
template of the VM.
◦ Create a new VM from this vSphere template in vSphere. During the VM creation wizard,
select the option to customize the VM and input the requested customization parameters.
◦ If this VM customization process fails, deployment in infrastructure orchestration will not
be successful. Correct the vSphere customization issues, and create a new Insight Control
virtual machine management template from the functional VM. Proceed with deployments
from infrastructure orchestration.
• For VMware VMs, VMware vCenter Server must have Sysprep tools installed on the vCenter
management server in the VMware VirtualCenter\sysprep\svrOS folder. For Microsoft
Hyper-V, Microsoft Sysprep tools are required on the HP CMS in the Insight Control virtual
machine management sysprep folder.
• Change the password on the Hyper-V host to something that does not contain | or “ characters.
Select the Hyper-V host from the system list.1.
2. Edit the system credentials. Go to Options→Security→Credentials→System
Credentials…and select the Hyper-V host from the list.
3. Change the sign-in credentials and save the new credentials. Wait a few minutes for the
host to complete re-identification.
4. Start the Matrix infrastructure orchestration service request.
• Verify the Windows sysprep files have been added:
For Hyper-V VMs running Windows, go to the CMS and copy the sysprep files to C:\
Program Files\HP\Insight Control virtual machine management\
Sysprep\2003.
◦
◦ For VMware ESX VMs running Windows, go to the system which has Virtual Center
installed and copy the sysprep files to the following paths:
– Virtual Center 4.x and 5.x: C:\Documents and Settings\All Users\
Application Data\VMware\VMware VirtualCenter\sysprep\svr2003
For more information about customization or configuration, see the HP Matrix Operating Environment
Infrastructure Orchestration User Guide at http://www.hp.com/go/matrixoe/docs.
NOTE: The HPIO C:\Program Files\HP\Matrix infrastructure orchestration\
conf\Sysprep.inf file must be edited to specify additional customizations for Windows virtual
machines. Without this edit, a newly provisioned system halts during first boot waiting for a key.
For details, see HP Matrix Operating Environment Infrastructure Orchestration User Guide at http://
www.hp.com/go/matrixoe/docs.
Provisioned VMs fail due to improper VM host hardware configuration
Issue
Troubleshooting procedures 147