HP Insight Orchestration 6.3 User Guide

• Contents of the Insight Orchestration sysprep.inf file, located at ..\Program Files\
HP\Insight Orchestration\conf\sysprep\Sysprep_sample.inf.
An Insight Orchestration administrator can edit sysprep files based on the sample file to
specify additional customizations for Windows virtual machines.
To enable customization on:
• VMware vCenter 4.0, install the Microsoft Sysprep tools on the vCenter management server
in the folder C:\Documents and Settings\All Users\Application
Data\VMware\VMware VirtualCenter\sysprep\svrOS .
Where <OS> is the Windows guest operating system and can be 2003, 2003-64, 2008, or
2008-64. The “All Users” (and potentially other portions) of the path may vary depending on
your Windows installation and upgrade history on the vCenter server.
• Microsoft Hyper-V:
To support Windows 2003 VM guests, install the Microsoft Sysprep tools on the CMS in
the HP folder ..\Program Files\HP\Insight Control virtual machine
management\Sysprep\2003.
◦
◦ No modification is required to support only Windows 2008 VM guests.
See “Virtual service creation” (page 91) for troubleshooting information about modifying
the sysprep.inf file to allow a Windows 2008 virtual machine guest to join an Active
Directory domain.
For more information, see the VMware vCenter and Installing the Microsoft Sysprep Tools article
in the VMware Infrastructure 3 Online Library.
Configuring an environment for physical provisioning
For physical provisioning to perform correctly, set the following attributes in the ..\Program
Files\HP\Insight Orchestration\conf\hpio.properties file.
• Set physical.max.concurrent.requests=10 to limit the number of concurrent physical
logical servers provisioned. If you set the attribute to a value greater than 10, physical logical
server provisioning might fail.
• Set npiv.integrity.enabled=true to enable multi-initiator N-Port ID Virtualization
(m-NPIV) support.
m-NPIV is supported on Integrity server blades using the QLogic FC controller with the HP-UX
11i v3 Update 8 (March 2011) and later release.
Physical provisioning requires:
• Available VC Domain groups in Virtual Connect Enterprise Manager (VCEM)
• Configuring server deployment platforms including Insight Control server deployment, Ignite-UX,
or HP Server Automation
• Creating SAN-backed storage
• Creating job folders (this is specific to Insight Control server deployment; see “Configuring
Ignite-UX” (page 23) and “Configuring HP Server Automation” (page 24))
Verifying VC Domain groups
Insight Orchestration requires virtual domain groups. To create a virtual domain group or verify
an existing group, see the HP Virtual Connect Enterprise Manager User Guide at HP Insight
Dynamics Information Library.
30 Configuration