CA Client Automation - 14.0

English

Known Issues and Troubleshooting

The
CA Client Automation
 14.0 release contains the following issues and their work arounds:
cla140
The
CA Client Automation
 14.0 release contains the following issues and their work arounds:
CA Patch Manger "Need Patch" Reports Are Not Executing Correctly
Symptom
Reports like “Need Patch and Have*” and “Need Patch, but Don’t have*” that are related to CA Patch Manger shows empty data.
Solution
Prepare and run the queries on the database directly.
Job Output of Software Job Fails for Large Data
Symptom
The job output of a software job more than 2 MB fails to populate in Internet Explorer.
Solution
If job output is more than 2 MB, use other browsers.
Custom Rollup Signatures Not Replicating from Enterprise to Domain Managers
Symptom
If CA Patch Manager is configured to run on Enterprise Manager, the signatures for rollups that are customized through CA Patch Manager are not replicating from Enterprise Manager to Domain Managers. The signature discovery of custom rollups is affected.
Solution
None
Cannot Access Help Files by Pressing F1 Key on Some User Interfaces
Symptom
If the F1 key is pressed for help files in some user interfaces, I am not redirected to Techdocs Content.
Solution
Open Techdocs  (
CA Client Automation
) directly and search for required information.
Cannot Run Commands on Windows 10 After
CA Client Automation
 Installation
Symptom
CA Client Automation
 commands cannot run from the command prompt on Windows 10 after installation.
Solution
Open the command prompt with "Run as administrator" or log out and log in again. You can also restart the system.
Windows 10 OSIM Installation With Language Pack Fails
Symptom
Windows 10 OS image is created with language packs. When a Windows 10 OS installation job is submitted, OS installation fails after copying OS files. An error message is displayed as:
Windows could not applied unattended settings during pass [OfflineServicing]
Solution
If you want to install an offline Language Pack with the OS image, follow these steps:
To add language packs to the Windows 10 OS Image, use Assessment and Deployment Kit 10.0 (Windows ADK for Windows 10) or above which contains Deployment Image Servicing and Management (DISM) tool version 10.0 and above.
  1. Mount Install.wim from Windows 10 original source media or install.wim file that belongs to the already created OSIM Windows 10 OS image "sources" folder. This folder is available under CA\DSM\Server\SDBS\var\managedpc\images\<Win10 Image Name>\<Win10 Image Name>.
    Dism /Mount-Image /ImageFile:<Path to install.wim>\install.wim /index:1 /MountDir:<Path to Offline folder>
  2. Add your language pack.
    Dism /Image:<Path to Offline folder> /ScratchDir:%temp% /Add-Package /PackagePath:<Language pack Path>\<Language Pack cab file1> /PackagePath:<Language pack Path>\<Language Pack cab file2> ....
    Ensure that the scratch directory is at least 1 GB for adding language packs.
  3. (
    Optional)
    Execute the following command to list the languages in the offline image.
    Dism /Image:<Path to Offline folder> /Get-Intl
  4. Unmount Install.wim committing changes.
    Dism /unmount-wim /mountdir:<Path to Offline folder> /Commit
  5. Now create OSIM OS image using this updated Windows 10 source media which contains updated install.wim and follow further normal OSIM Deployment process. If you use install.wim file that belongs to the already created OSIM Windows 10 OS image "sources" folder available under "CA\DSM\Server\SDBS\var\managedpc\images\<Win10 Image Name>\<Win10 Image Name>", follow the normal OSIM Deployment process.