Insight Dynamics 6.1 Release Notes

Suggested action 1

1. Launch the Deployment Console.

2. Rename the Erase ProLiant Hardware job to a name that does not contain non-English

characters.

3. Retry the operation.

Suggested action 2 Specify a service name containing valid characters ([a-z] [A-Z] [0-9] [_] [-]

[space]).

Suggested action 3 Use the Insight Orchestration Operations Console to approve or reject

requests that contain Japanese characters.

Major issues

Physical server provisioning using Insight Control server deployment fails during final personalization

step when the CMS is configured with an automatic proxy configuration script in IE

Using Insight Orchestration for physical server deployments via HP Insight Control server

deployment fails during the final personalization step. This can occur when there is a problem

or delay communicating with the automatic configuration script configured in Microsoft Internet

Explorer. The problem is in Windows .NET, and the proxy configuration is shared between IE

and .NET.

The Insight Orchestration log for the failed deployments contains lines similar to the following:

ERROR com.hp.hpio.sbapi.tasks.CreatePhysicalServerTask.execute - Error

personalizing OS with host uuid: 38C77BED-9FAE-4886-8C06-0F536BA46507

com.hp.hpio.sbapi.exception.AresAdapterException: Deployment server did not

accept customization data.

The log for the connector software that drives Insight Control server deployment, C:\Program

Files\HP\Systems Insight Manager\logs\Alc1_0.0.log, shows that the operations

that perform the customizations are timing out.

Suggested action 1 Configure Internet Explorer with an explicit proxy server address and

appropriate exceptions instead of using an automatic configuration script. Check "bypass proxy

server for local addresses" if the server deployment server is on the CMS. Otherwise, make sure

to include the address of the server deployment server in the Exceptions field of the Advanced

options for configuring a proxy server.

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>

Using a remote CMS database with components that use ESA for storage provisioning and server

operations

See “Using a remote CMS database with components that use ESA for storage provisioning and

server operations ” (page 16) for information about an issue that may affect HP Insight

Orchestration.

HP Insight Orchestration 21