HP Insight Orchestration 6.3 User Guide

The computer restarted unexpectedly or encountered an unexpected error.
Windows installation cannot proceed. To install Windows, click OK to
restart the computer, and then restart the installation.
Possible cause
The environment is not completely configured.
The virtual machine used in the Insight Control virtual machine management template was not
powered off properly.
The vCenter or vSphere is not configured properly for successful customization.
The incorrect product key was specified for the operating system in the sysprep file.
The Hyper-V host is configured with a password that contains | or “ characters.
Action
For VMware ESX VMs, verify the source VM being used to create the template has the VMware
Tools installed and configured. For Linux VM guests, ensure the vmware-config-tools.pl
command was executed after installing the tools.
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 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 TemplateClone 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 IO 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 IO.
For VMware VMs, VMware vCenter Server must have Sysprep tools installed on the vCenter
management server in the VMware VirtualCenter\sysprep\svrOS folder. For Hyper-V,
Sysprep tools are required on the 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.
1. Select the Hyper-V host from the system list.
2. Edit the system credentials. Go to OptionsSecurityCredentialsSystem 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 IO service request.
Create Request fails with a virtual machine customization error.Issue
Possible cause
The environment is not completely configured
The virtual machine used in the VMM template was not powered off cleanly
Action
If the environment is not completely configured, requests might fail when executing the virtual
machine customization step. Issues can include missing the sysprep folder on the VI3 server,
insufficient licenses on the VI3 server, or attempting to customize a virtual machine with a guest
operating system that is not supported on the VI3 server. Verify that the environment is correctly
configured and be sure you are provisioning a supported guest operating system. For more
information on configuration, see HP Insight Software Installation and Configuration Guide
available at http://www.hp.com/go/insightcontrol/docs.
To power off the virtual machine cleanly before creating the VMM template, see “Creating Insight
Control virtual machine management (VMM) templates” (page 27).
94 Troubleshooting