HP Insight Orchestration 6.3 User Guide

following steps can be followed to disable the installation of Insight Management WBEM providers.
Insight Management SNMP agents continue to provide management capabilities when WBEM
providers are not installed.
1. Edit the install.cmd file, found under <Insight Software installation folder>\
rdp\deployment server\hpfeatures\hpagents-ws\components folder, and remove
the following two lines.
call :installsc wbem%PROCESSOR_ARCHITECTURE%
if %cpresult% geq 1 set /a cpresults=cpresults+1
2. Save the file.
The new service requests will no longer attempt to install Insight Management WBEM providers.
A request with a future start date stays at 10% (Progress field), with status of Reserved (rather than
Scheduled).
Issue
The request is scheduled, but its status is not updated.Possible cause
Do one of the following.Action
Wait until the selected start date; the request will start provisioning automatically.
Cancel the request, then resubmit it.
NOTE: Use this option if you anticipate changing the lease period before the service is
provisioned.
Restart Insight Orchestration, which will update the request status.
Physical server provisioning using Insight Control server deployment fails during the final
personalization step when the CMS is configured with an automatic proxy configuration script in
IE.
Issue
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
Possible cause
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-48868C060F536BA46507
com.hp.hpio.sbapi.exception.AresAdapterException: Deployment server did
not accept customization data.
The log file for the connector software that drives Insight Control server deployment (..\Program
Files\HP\Systems Insight Manager\logs\Alc1_0.0.log), shows that the operations
which perform the customizations are timing out.
Do one of the following:Action
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.
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 ..\Program
Files\HP\Systems Insight Manager\bin\alc-rdpaccess.config with the following
content:
<configuration>
<system.net>
<defaultProxy>
<proxy usesystemdefault = "false" />
</defaultProxy>
</system.net>
</configuration>
90 Troubleshooting