HP Insight Control 7.3 Release Notes

Suggested action
The only way to force a logout of a user is to delete the user from the server provisioning appliance.
This will result in the user being logged out without having to restart the appliance. This is the
recommended action when a password has been compromised. Once deleted, the user can be
re-added.
Using domain credentials when adding an HP OneView appliance results in an "Access
unauthorized" warning
When adding an HP OneView appliance to the Insight Control server provisioning appliance,
specifying credentials with a domain will result in an Access unauthorized error.
Suggested action
When adding an HP OneView appliance, always specify a local user and not one with a domain.
Post-install network configuration does not work on Windows servers that have been added to a
domain
The post-installation network configuration process does not operate properly on Windows servers
that have been added to a domain.
Suggested action
Perform all network configuration tasks before adding the server to a domain.
Server provisioning appliance may be left unusable if shutdown ungracefully
If the appliance is shut down abruptly as a result of something like a power failure, storage
disconnection, or forced power off, on very rare occasions, the appliance disk may become
corrupted, and upon restart, will prompt for a password to manually run fsck. Unfortunately, the
supported mechanisms of getting the root password are not enabled at this early stage in the boot,
and hence the appliance is left unusable.
Suggested action
Revert to a previously created VM snapshot, if one is available. If not, create a new server
provisioning appliance from the original image and then restore a backup.
Major issues
NOTE: Red Hat Enterprise Linux (RHEL) 6.4 with KVM can be deployed through Matrix
infrastructure orchestration using Insight Control server provisioning. An item in the Insight Control
7.2 Update 2 Release Notes indicated that this OS could not be deployed by Matrix via Insight
Control server provisioning and suggested manual deployment. To ensure successful automated
deployment of RHEL 6.4 with KVM through Matrix infrastructure orchestration, see the HP Matrix
Operating Environment Release Notes for necessary actions (including modifications to the
kickstart file).
The Post-install Network Configuration may fail on Red Hat servers running NetworkManager
After executing the Configure Network action on a target server, the Post-Install Network
Configuration job may fail if the NetworkManager service is enabled and one of the NICs on the
target server is not active.
Suggested action
Add the following command in the %post section of the kickstart file to disable the
NetworkManager:
service.chkconfig NetworkManager off
Issues and suggested actions 15