HP Matrix Operating Environment 7.0 Release Notes

For details on using Matrix OE with Microsoft Windows systems not running OpenSSH, see the
HP Insight Dynamics 6.0 software without OpenSSH on HP ProLiant and Integrity Servers Running
Microsoft Windows white paper, available at the following website:
Matrix OE Information Library
Patch required to provision Hyper-V linked clone VM guests using HP Server
Automation
If you are using HP Server Automation (SA) 9.0 or 9.10 on Red Hat Enterprise Linux 6 or SUSE
Linux Enterprise Server 10 platforms and you want to provision Hyper-V linked clone VM guests,
install the following version-specific core patches and hotfixes for each SA version.
For SA 9.0, download and install:
• SA 9.05 core patch from http://support.openview.hp.com/selfsolve/patches
• “Linked Clone errors for RHEL6 and Above” hot fix from https://quixy.deu.hp.com/hotfix/
index.php?HOTFIX_PROJECT=server_automation
For SA 9.1, download and install:
• SA 9.11 core patch from http://support.openview.hp.com/selfsolve/patches
• “Linked Clone errors for RHEL6 and Above” hot fix from https://quixy.deu.hp.com/hotfix/
index.php?HOTFIX_PROJECT=server_automation
Patch required for proper management of Microsoft Windows Server 2008 with
Hyper-V systems
A patch from Microsoft is required for managing Microsoft Windows Server 2008 with Hyper-V
systems. Patches are installed on the Hyper-V hosts, and after you do so, you must install or update
Hyper-V Integration Services from the updated host to each VM guest. Do this as a precaution
because not all patches affect Integration Services on the guests.
Microsoft Windows Server 2008 SP2 with Hyper-V requires you to install the following patch that
fixes the hang in host servers with many simultaneous virtual machine operations. The patch is
located at http://support.microsoft.com/kb/980081.
See the Managing Microsoft Windows Server 2008 Hyper-V with HP Insight Software technology
brief for more information about other patches that might be required for later editions of Microsoft
Windows Server 2008 (R2):
Matrix OE Information Library
VM kernel port name used for management traffic must be “Management Network”
In VMware ESXi, the default name of the Virtual Machine (VM) kernel port used for management
traffic is “Management Network”. Do not modify this name in the vCenter client user interface. If
this name is modified, the following will result.
• When trying to activate a logical server, the ESXi hosts appear as Rejected Target hosts with
an error that the hosts are not part of vCenter, or that virtual machine management is unable
to get vCenter information for the VM Host.
• The association between the host and vCenter does not appear in Systems Insight Manager.
Suggested action
Modify the Network Label of the VMKernel port used for management traffic to “Management
Network” by performing the following steps.
1. Log into the vCenter using the vCenter client.
2. Select the Hosts and Clusters view from the menu View→Inventory.
3. Select the ESXi server from the tree displayed in the left pane.
12 Description