HP Insight Dynamics 6.0 Release notes

Suggested action 2 Provide a .NET configuration file for the application that communicates

with Insight Control server deployment so that it will not use the system default proxy. Create

the file C:\Program Files\HP\Systems Insight Manager\bin\

alc-rdpaccess.config with the following content:

<system.net>

</defaultProxy>

</system.net>

</configuration>

System properties reset to default values after manual upgrade of HP Operations Orchestration

Manually upgrading HP Operations Orchestration from version 7.20 to 7.51 is required after an

upgrade of HP Insight Orchestration 1.0 (available on the Insight Software DVD 3.10) to Insight

Orchestration 6.0 (available on the Insight Software 6.0 DVD).

After the manual upgrade completes, all of the system properties required for integration with

Insight Orchestration are reset to default values. This prevents Operations Orchestration from

working properly with Insight Orchestration.

Suggested action Before upgrading Operations Orchestration, access Operations Orchestration

Central on the CMS, and navigate to the System Properties folder. Note the values of the following

properties:

HpioApprovalRecipients HpioManualStorageProvisioningRecipients

HpioApprovalSender HpioManualStorageProvisioningSender

HpioCmsIp HpioNotificationRecipients

HpioConfDir HpioNotificationSender

HpioDebug HpioServiceActionRecipients

HpioDefaultPort HpioServiceActionSender

HpioManualOsDeploymentRecipients HpioSmtpHost

HpioManualOsDeploymentSender HpioSmtpPort

After the upgrade of Operations Orchestration is complete, open Operations Orchestration

Central and replace the default system properties with the values previously noted.

Minor issues

Pointing a remote Operations Orchestration Studio installation to Operations Orchestration

Central installed on a CMS

A “Failed Login” error message is displayed when you try to log in to Operations Orchestration

Studio 7.51 pointing to a remote repository (for example, Operations Orchestration Central 7.51

on the CMS).

Suggested action Make a backup of the rc_keystore file on the CMS. Then copy the

rc_keystore file installed on the CMS

(OO-studio-installation-path-on-CMS\conf\rc_keystore) to the same path on the

remote Operations Orchestration Studio system.

Request completion delays with large number of concurrent provisioning requests

Start logical server requests and operating system deployment requests are processed in

first-in-first-out (FIFO) order. If the CMS is handling a large number of concurrent requests, start

logical server requests are queued after other operating system deployment requests are

completed, causing service request completion delays.

22 Issues and suggested actions