Client Automation 12.9 Readme

1.0 Welcome

Welcome to the CA Client Automation Release 12.9 readme. This readme contains supported operating environments, documentation changes, accessibility features, and known issues.

The readme is supplementary to the Release 12.9 documentation. Client Automation Release Notes contains information that is required to install, configure, and use the functionalities included in this release.

2.0 Hardware Specifications and Requirements

The following tables provide the minimum recommended hardware specifications and requirements for this release.

Actual hardware requirements depend on the system load on the system, including the frequency and amount of data collected and transferred and the number of operations.

2.1 Enterprise Manager Specifications

A DSM enterprise manager requires (at a minimum) the following hardware configuration:

2.2 Domain Manager Specifications

A DSM domain manager requires (at a minimum) the following hardware configuration:

2.3 Scalability Server Specifications

A DSM scalability server requires (at a minimum) the following hardware configuration:

Note: These minimums apply to all supported Windows, RedHat, and SuSE operating environments.

2.4 Agent Specifications

A DSM agent requires (at a minimum) the following hardware configuration:

Note: These minimums apply to all supported agent environments.

2.5 DSM Explorer Specifications

The DSM Explorer requires (at a minimum) the following hardware configuration:

Note: These minimums apply only to supported Windows operating environments.

2.6 Specifications for an SQL Server MDB on Windows

A Microsoft SQL Server management database (MDB) on Windows requires (at a minimum) the following hardware configuration:

2.7 Specifications for an Oracle MDB

Installing more than one Oracle MDB instance requires (at a minimum) the following hardware configuration:

3.0 Known Issues and Troubleshooting

This section describes the known issues, limitations, and solutions for this release.

3.1 Client Automation Manager Installation Fails with SQL Server 2012 SP1

Symptom:

When I install Client Automation manager on a system with SQL Server 2012 SP1 installed, the ITCM installation fails with the following error:

Installation of 'CA Secure Socket Adapter failed'
Return Code1618

Solution:

This error is due to an issue on SQL Server 2012 SP1, msiexec.exe processes run after installation of SQL Server 2012 SP1. When you install Client Automation manager; as another MSI installer is in progress, the installation fails with the error 1618.

Microsoft has posted a description of the bug and a link to the patch (KB2793634). For example, https://support.microsoft.com/kb/2793634. Also, you can download the fix from Microsoft Downloads section. For example, http://www.microsoft.com/en-us/download/details.aspx?id=36215.

3.2 OS Deployment Fails While Using Centralized NFS Share for Client Automation OSIM

Symptom:

When I use Client Automation OSIM to deploy SLES 11.x, OpenSuSE 12.x, Oracle Enterprise Linux, and XenServer 6.x operating systems using the centralized NFS share, operating system installation hangs at the target machine.

Solution:

You can fix this issue in the following manner:

• Use CD/DVD option for creating the OS Images of the mentioned operating systems instead of the centralized NFS server.

3.3 Client Automation Domain Manager Installation Fails

Symptom:

Client Automation domain manager installation on Windows, Oracle MDB fails, only when ITAM 12.9 is already installed.

Solution:

Follow these steps:

1. Rename the folder jre under the path \Program Files\CA\SC\Mdb\Windows\ as jre_OLD.
2. Copy the JRE folder under the path \WindowsProductFiles_x86\JRE from DVD to C:\Program Files\CA\SC\Mdb\Windows\
3. Start the ITCM installation.
4. After the installation completes, perform the following steps:
   • Rename the folder jre as jre_1.7
   • Rename the folder jre_OLD as jre.

Note: When you do not install ITAM, install Client Automation and then ITAM to avoid these manual steps.

3.4 Location Awareness Rule Evaluation

Caf restart triggers Location Awareness rule evaluation when the hidden comstore parameter disable_la_on_all_registers is set to 0 and caf restart does not trigger Location Awareness rule evaluation when the hidden comstore parameter disable_la_on_all_registers is set to 1.

You can create the parameter on the agent machine with the following command:

ccnfcmda -cmd setparametervalue -ps itrm/agent/solutions/generic/LocationAware -pn disable_la_on_all_registers -v 1

3.5 IP Address Range for Location Awareness Evaluation

Symptom:

Location Awareness evaluation does not include the boundary values of IP address range.

Solution:

Define the expected IP address range with the preceding and succeeding values in both starting and ending directions respectively. For example, if you want an IP address range of 10.10.10.1-10.10.10.10, specify the range 10.10.10.0-10.10.10.11.

3.6 DMM: Recent Document Settings and DMM Share Access

Recent Document Settings

Client Automation delivers a new recent document settings option for all Client Automation-supported MS-Office applications. You can now select the recent document settings. This option works only if files are available at the same location as before migration. Otherwise, when you click the recent document, it displays a standard system error.

Configure DMM Share Access:

When the DMM network share runs on Windows Server 2008 or higher, the DMM Apply procedure execution fails with a runtime error on some of the target machines during the restoration phase.

Follow one of these steps:

• Use a DMM network share that runs on Windows Server 2003 SP2.
• Use a DMM network share that runs on Windows Server 2008 SP2 or Windows Server 2008 R2, with SMB 2.0 disabled as follows:
  1. Open Regedit.
  2. Navigate to HKLM, System, CurrentControlSet, Services, LanmanServer, Parameters.
  3. Add a DWORD key with the name smb2 and set the value to 0.
  4. Restart the server.

3.7 Change in SD Deployment Behavior in DSM GUI When Using Specific Computer Group, Software Group or Procedure Group

When a particular Computer Group, Software Group or Procedure group is selected, the options to Deploy Software Packages, Deploy SW Group and Deploy procedure Group respectively, are hidden if no selection is made in the right-hand pane of the selected entity.

3.8 Error with Owned Inventory Links

Symptom:

When I open Client Automation WAC, Console, Computer and Users, All computers, Host, Inventory tab, Owned inventory, and click any of the following links:

• Generic components
• Specific components
• Legal Info and
• Cost Info

I get the following error:

Error: The SELECT permission was denied on the object 'arg_rel_asset_cfg_gen', database 'mdb', schema 'dbo'.

Solution:

The error is due to a problem with user ca_itrm permissions. You can fix this issue by applying the patch RO65886 available at support.ca.com.

3.9 Creating a Package on Windows 8 Fails

Symptom:

When I run SXP Packager to create a package on Windows 8, I get the following error message:

Error 007 The following file could not be copied:
C:\autoexec.bat to C:\Program Files\CA\DSM\bin\Save\001\asc0001.sav

Solution:

You can fix this issue in the following manner:

• Delete the DSM\bin\Save folder before creating a package.
• Verify that .NET framework 3.5 is installed and enabled.

For more information, see Prerequisites for SXP Packager on Windows 8 in Client Automation Packager Admin Guide.

3.10 Creating a Package on Windows 2008 x64 Fails

Symptom:

When I run SXP Packager to create new package on Windows 2008 x64, I get the following error message:

GetLink.exe has stopped working.

Solution:

You can fix this issue in the following manner:

1. Go to Microsoft Download Center.
2. Download and Install Microsoft Visual C++ 2010 Redistributable Package (x64).

For more information, see Microsoft documentation.

3.11 WAC Change of Browser Locale

When you change the locale on the browser, logout and relogin to WAC for better functionality.

3.12 caf status cfProcessManager Shows Alert Collector Process Information as Empty

If you did not install Alert Collector, the command output must not show an entry for Alert Collector.

However, on Windows computers, the caf status cfprocessmanager command shows the Alert Collector process information as empty even if Alert Collector is not installed.

3.13 Setup Could Not Configure Automated Migration Feature

Symptom:

When you install or upgrade to newer release of Client Automation, if you select the Automated Migration option, the following warning message is displayed:

Setup could not configure Automated Migration feature. Please follow the steps described in troubleshooting document to configure it manually.

As a result of this warning, although the installation or upgrade is successful, you do not see the Automated Migration option in DSM Web Console.

Solution:

Perform the following manual steps to resolve this issue.

Follow these steps:

1. Access the following URL on the DSM manager that you installed or upgraded.

   http://<hostname>/axis/services

   • hostname

     Specifies the fully qualified domain name of the host computer. For a cluster setup, use the cluster name as host name. If the action fails while using cluster name, use the node name and re-execute the same commands.

   A list of all Web Services API deployed appears. Look for the services automationService and assessmentService. If these services are listed, contact CA Technical Support for further assistance. If the services are not listed, perform the following steps to deploy the automation services:

2. Execute the following command in the command line of the DSM manager computer:

   Set classpath=<PATH>\axis.jar;<PATH>\axis-ant.jar;<PATH>\commons-discovery.jar;<PATH>\commons-logging.jar;<PATH>\jaxrpc.jar;<PATH>\log4j-1.2.8.jar;<PATH>\saaj.jar;<PATH>\wsdl4j-1.6.2.jar;<PATH>\activation.jar;<PATH>\mailapi.jar;

   • PATH

     Specifies the location of the jar files. The jar files are located in < DSM_INSTALLED_FOLDER >\Web Console\webapps\wac\WEB-INF\lib.

   The command sets the class path environment variable.

3. Execute the following command:

   "<DSM_INSTALLED_FOLDER>\SC\JRE\1.7.0_17\bin\java" org.apache.axis.client.AdminClient "<AUTOHOME>\AutomationService_wsdd\deploy.wsdd" -l http://<hostname>/axis/services/automationService

   • DSM_INSTALLED_FOLDER

     Displays the path where ITCM is installed.

   • AUTOHOME

     Specifies the Automation Services Folder path. Environment variable AUTOHOME refers to the Automation Services Folder path.

4. Execute the following command:

   "<DSM_INSTALLED_FOLDER>\SC\JRE\1.7.0_17\bin\java" org.apache.axis.client.AdminClient "<AUTOHOME>\AssessmentService_wsdd\deploy.wsdd" -l http://<hostname>/axis/services/assessmentService

   The command deploys the automation services.

5. Restart tomcat.
6. Log in to Web Console and verify that the Automated Migration option is now visible.

3.14 DTS Transfer Fails If Agent Is Running on Kubuntu OS

Symptom:

When software delivery download method is set to DTS-Nos-less on Kubuntu operating system, software package transfer fails with the following error:

DTS status: File transfer has been interrupted

Solution:

To resolve this isuse, uninstall the DSM Agent and install using one of the following methods:

• Install using DM deployment infrastructure
• Install using the installer GUI

4.0 Third-party License Agreements

The license agreements for this release are available in Bookshelf\Release Information\Third-Party License Agreements.

5.0 Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

• Online and telephone contact information for technical assistance and customer services
• Information about user communities and forums
• Product and documentation downloads
• CA Support policies and guidelines
• Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

Copyright © 2014 CA Technologies. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.