Skip to content
CA Client Automation - 14.0
Documentation powered by DocOps

New Features and Enhancements of 14.0.2

Last update October 10, 2017

For a list of supported platforms and product integration, see Compatibility Matrix.

CA Client Automation Release 14.0.2 provides the following new features and enhancements:

Enhanced Support for OSIM Boot Server Move with Scalability Server

CA Client Automation allows you to move Scalability Server from one Domain Manager to another. Now, OSIM targets where Agent is installed and having OSIM job status as Current is moved to the new Domain Manager. The relationship between Boot Server and target is maintained on the new Domain Manager. For more information, see Agent and Scalability Servers Move Operations

Cleanup of OSIM Residual Files and Folders After the Installation of Operation System by CA Client Automation

CA Client Automation allows you to deploy Operating Systems. OSIM leaves many files and folders to the target system after the Operating System is installed using the previous versions of CA Client Automation. Some of these files might contain encrypted password. Now, all the files and folders are automatically deleted as a part of Operating System deployment. This boot parameter “CleanupOSIMFiles” can control this behavior, which is by default set to “Yes”. If you want to retain these residual files and folders, set this parameter to “No” before deploying the Operating System. For more information about the parameters, see Boot Parameter Settings.

Support for UEFI Boot Inventory for Windows and Linux Agent

CA Client Automation Agents used to collect System and legacy BIOS boot mode inventory. Now on Windows and Linux systems (booted in UEFI/BIOS mode), the Agent collects information about whether the system is booted in legacy BIOS mode or UEFI mode and UEFI Version also. New inventory attributes are added under the System Bios inventory. 

Improved Supportability 

Automated Inventory Recovery

On CA Client Automation agents, except for the first time, the collected inventory that is sent to the manager is always the delta inventory.  A configuration policy option is provided to the administrators to send the collected inventory in full after a specified number of agents that are run from agent. If a network packet loss occurs during inventory data transmissions, the next full inventory transmission ensures that the previously lost inventory is available on the manager.  This policy option is available under the DSM, Agent, Asset Management, Collect full inventory path after specified number of agent runs. The default value is 0, which indicates that the option is disabled.

Agent Version Column

A new column is added in Client Automation Explorer to show the Agent Common Version under All Computers, Computer Groups. This attribute shows the common agent version that the Agent reports.

Default Engine Settings

Default value of the Number of Files the engine will collect during one collect cycle parameter in Engine properties changed from 10000 to 1000.

Simplified Master Image Update

From CA Client Automation 14.0 SP2 onwards, you can customize the installation or upgrade process. In the previous versions of CA Client Automation, methods did not exist to patch the solution during the installation. Previously, we used one of the following methods to patch the solution during the installation:

  • By obtaining a master image fix
  • By installing the patch after the completion of installation: This method assumes that the patch is not required for the product to function. Also in many environments, perform other custom actions after the installation.

To solve these difficulties, CA Client Automation now supports the capability to perform post-installation tasks as part of the installation or upgrade process.

This process can be evoked as follows:

Installation Using DVD in Windows:

  1. Create a directory as TestFixes in the DVD_ROOT.
  2. Create a batch file as InstallTestFixes.bat in the TestFixes directory.
  3. Copy the test fixes and Applyptf executable to the TestFixes directory and write the logic to invoke applyptf command silently.
    When setup.exe is invoked to launch the Windows installer and if InstallTestFixes.bat exists, the command is run.
    For example,

     <DVD Root>\TestFixes\installTestFixes.bat

Installation Or Upgrade Using Software Delivery or DM Deployment in Windows:

  1. Create a directory as TestFixes in the required role, that is, agentAM, AgentSD, and so on.
  2. Create a batch file as InstallTestFixes.bat in the TestFixes directory.
  3. Copy the test fixes and Applyptf executable to the TestFixes directory and write the logic to invoke applyptf command silently.
  4. Register the packages.
  5. When deployment happens, the Deploywrapper executable goes to the TestFixes directory. If InstallTestFixes.bat file exists, the same is launched.
    For example,

     <DVD Root>\WindowsProductFiles_x86\AgentAM\TestFixes\installTestFixes.bat

Installation Using DVD in Unix Or Linux:

  1. Create a directory as TestFixes in the <DVDRoot>/<platform>ProductFiles_x86 >/<Package Name> or <DVD Root>/<OS Productfiles> directory.
  2. Create a shell script as InstallTestFixes.sh in the TestFixes directory.
  3. Copy the test fixes and Applyptf executable to the TestFixes directory and write the logic to invoke applyptf command silently.
    If InstallTestFixes.sh file exists, the installer invokes the same at the end of the installation. Installer expects the TestFixes directory availability in the current directory or parent directory with the installdsm.sh file.
    Current directory takes precedence over the parent directory. If TestFixes is available in the current directory, the same is executed. Otherwise, the parent directory is verified.
    For example,

    <DVDRoot>\LinuxProductFiles_x86\agent\TestFixes\installTestFixes.sh or <DVD Root>\LinuxProductFiles_x86\TestFixes\installTestFixes.sh.

Installation or Upgrade Using Software Delivery or DM Deployment in Unix or Linux

  1. Register the packages from the customized DVD using dsmpush.
  2. Follow the steps 1 through 3 mentioned in the procedure Installation Using DVD in Unix or Linux to patch the DVD.
  3. At the end of the installation, installer looks for TestFixes/InstallTestFixes.sh in the package folder.
    For example,

    agent\TestFixes\installTestFixes.sh

InstallTestFixes.bat file

Was this helpful?

Please log in to post comments.