Agent is not installed during OSIM process, OSIM state stuck at Installing.

book

Article ID: 35454

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager

Issue/Introduction

Problem

A PC is built via Operating System Installation Management (OSIM) and the parameter "InstallAgent=yes" is defined. The operating system is successfully installed but the agent is not installed.

When reviewing the status of the OSIM job in DSM Explorer it is stuck at "Installing" and does not move to "Current"

Environment: 

  • Boot Server is running on Scalability Server

Cause:

  • The bootserver copies the agent install binaries from the Local Software Delivery library to the sxpsetup-11 share (...........\CA\DSM\Server\SDBS\var\managedpc\agents).
  • When the SDMPCSERVER process starts up it examines the local SD library and looks for the latest version of the ENU software delivery agent package. When it finds this it copies it to the sxpsetup-11 share.
  • When the Boot server is on the Scalability Server It cannot find the agent package unless it has first been staged to the Software Library on the Scalability Server.
  • When "InstallAgent=yes" The change of state from "Installing" to "Current" only occurs once the agent has successfully been registered and collected by the engine. As the agent could not install the state does not change

 

Resolution

  • Stage the ENU Software Delivery Agent package to the Scalability Servers' Software Library

Environment

Release: UASIT.99000-12.9-Asset Intelligence
Component: