OSIM: How to switch between ENU and NLS variant of the SD Agent
Article ID: 111683
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
How to switch between the ENU and NLS variants of the ITCM Software Delivery Agent (SD Agent), for use with OSIM deployments.
Environment
Client Automation (ITCM) -- any version.
Resolution
When both the ENU and NLS agent packages are staged on the Scalability Server, the Boot Server plugin (by review of the code), will favor the ENU edition of the agent. At the time of this documents publication, an enhancement story [S166320] was added to the ITCM feature backlog for improving this situation in the future.
For now, the following workarounds should be considered:
1- Unstage the ENU only package, making it only possible for the NLS (non-language specific) package to be available for OSIM (or vice versa).
2- Let OSIM deploy the ENU package, and push the NLS variant after the OS image is deployed.
For now, the following workarounds should be considered:
1- Unstage the ENU only package, making it only possible for the NLS (non-language specific) package to be available for OSIM (or vice versa).
2- Let OSIM deploy the ENU package, and push the NLS variant after the OS image is deployed.
Feedback
Yes
No
Powered by
