HP Matrix Operating Environment 7.1 Release Notes

After the upgrade, you can power on and deactivate the logical server, if desired.
Check logical server management upgrade log file
When Matrix OE logical server management is upgraded, the pre-upgrade task completes even
if there are exceptions or missing objects.
Suggested action
After the upgrade is complete, check for important upgrade messages at ../Program Files/
HP/Virtual Server Environment/logs/vselog.lsm.log, and make any changes as
necessary.
Reconfigure deployment servers after upgrade from 6.0 and 6.1
During an upgrade from Insight Dynamics 6.0 or 6.1 to Matrix OE 7.1, deployment server
configuration data is not migrated.
Upgrades to Matrix OE 7.1 from Insight Dynamics 6.2 and higher are not affected.
Suggested action
After the upgrade is complete, reconfigure deployment servers (HP Server Automation, Insight
Control server deployment, and Ignite-UX) before attempting to create a provisioning service in
infrastructure orchestration.
Changing the CMS password
Systems Insight Manager includes a CMS reconfigure tool that allows you to make common
reconfiguration changes to your CMS, including realigning the Insight Management service account
credentials with the CMS operating system password after the operating system password is
changed.
In earlier releases, manual steps were required for the Insight Management components to recognize
a CMS password change and properly operate, which are detailed in the Changing the Insight
Software 6.0, 6.1 or 6.2 CMS password white paper. This white paper does not apply to Matrix
OE 7.1.
See the HP SIM 7.1 User Guide at www.hp.com/go/foundationmgmt/docs for information about
using the CMS reconfigure tool.
Enabling template access restrictions
HP Matrix Operating Environment infrastructure orchestration supports template access restrictions
on a per user basis. This feature is disabled by default. If you do not modify the properties file, all
users will see all templates.
To enable template access restrictions for users not in an organization, edit the C:\Program
Files\HP\Matrix infrastructure orchestration\conf\hpio.properties file,
and set template.access.restricted=true. After access restrictions are enabled, only
users assigned to a template are able to see and use the template.
NOTE: Irrespective of this setting, all users in an organization have access to all templates
assigned to the organization. Template access controls for individual users in an organization are
not supported.
Installation 11