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

8. (Optional) Configure email addresses:
During the Insight Management software installation process, you can specify one From and
at least one To email address for each operation class or use the same addresses for all classes.
The OO system properties screen displays all the classes of emails sent by IO. You can
reconfigure each of them to go to a different address (use a semicolon to separate multiple
recipient email addresses).
9. To save the modified property values before exiting OO, right-click System Properties in the
My Changes/Checkouts pane, and select Check In Tree.
Configuring for virtual machine provisioning
Verifying Microsoft Windows Sysprep
NOTE: Microsoft Windows Sysprep files are supported with encrypted passwords. See the HP
Matrix Operating Environment Infrastructure Orchestration User Guide for more information.
Matrix infrastructure orchestration relies on Windows Sysprep to enable customization of Microsoft
Windows virtual machines. Customization includes operations such as changing the hostname,
applying the Windows license key on first boot, and setting the IP address. To automate Windows
system deployments and apply the Windows license key automatically, you must edit the Matrix
OE-supplied Sysprep.inf file. This edit enables Matrix OE to provision new Windows systems
with no manual interaction. Without this edit, for example, a newly provisioned system may halt
during first boot waiting for a key.
Matrix infrastructure orchestration customizes the Windows OS for each Windows VM it provisions
by combining two sources of information and passing them to HP Insight Control virtual machine
management (VMM). VMM passes the information to ESX and Hyper-V for customization. This
information includes:
• Specific attributes from the service template such as hostname.
• Contents of the Matrix OE Sysprep.inf file, located at C:\Program Files\HP\Matrix
infrastructure orchestration\conf\sysprep\Sysprep_sample.inf.
An administrator creates the new sysprep.inf file and can edit sysprep files based on the
sample file to specify additional customizations for Windows virtual machines, such as the Windows
license key. You can then use these files while creating IO templates with corresponding Windows
virtual machines.
You should create one sysprep file for each version of Microsoft Windows, for example,
NOTE: Do not delete or rename the Sysprep_sample.inf file. These files are always .INF
files (and not .XML) for all versions of Windows.
1. Copy Sysprep_sample.inf to sysprep_w2k3_32bit.inf
2. Copy Sysprep_sample.inf to sysprep_w2k3_64bit.inf
3. Copy Sysprep_sample.inf to sysprep_w2k8.inf
4. Copy Sysprep_sample.inf to sysprep_w2k8r2.inf
5. Edit the product key and any other needed customization in the file.
6. To cause IO to automatically join new virtual machines to a Windows domain, add the domain
administrator credentials, in clear text, to the Sysprep.inf file. If the credentials are not
provided in the Sysprep.inf file, select None or Workgroup in the Edit Network dialog
box. After deployment completes, a domain administrator can manually join the system to the
domain.
When defining networks in IO, set the MS Domain Type to Domain in the Windows Settings tab
of the IO Edit Network dialog box.
86 Configuring Matrix infrastructure orchestration