ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Client Automation - OSconfig.XML not update during upgrade

book

Article ID: 141144

calendar_today

Updated On:

Products

CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Software Delivery CA Client Automation - Remote Control

Issue/Introduction

After an upgrade the file C:\Program Files (x86)\CA\DSM\Agent\OSConfig.xml is not updated.

Cause

A fix including the file OSConfig.xml has been applied before upgrade.

OSConfig.xml file is not updated because its "creation date" is lower than "Modified Date".

 
MSI detects this file as an updated file and does not overwrite it.
 
When it is not OK we could see this in MSI log :
MSI (s) (70:44) [13:54:26:842]: File: C:\Program Files (x86)\CA\DSM\Agent\OSConfig.xml; Won't Overwrite; Won't patch; Existing file is unversioned but modified
 
 
When it is OK we could see this in MSI log :
MSI (s) (4C:F8) [18:45:35:184]: File: C:\Program Files (x86)\CA\DSM\Agent\OSConfig.xml; Overwrite; Won't patch; Existing file is unversioned and unmodified - hash doesn't match source file
 

Environment

Client Automation - All Versions

Resolution

Execute following command prior the upgrade  :

powershell.exe -ExecutionPolicy ByPass -Command "$(Get-Item 'C:\Program Files (x86)\CA\DSM\Agent\OSConfig.xml').creationtime=$(Get-Item 'C:\Program Files (x86)\CA\DSM\Agent\OSConfig.xml').lastwritetime"

 

This command sets the creationtime of file C:\Program Files (x86)\CA\DSM\Agent\OSConfig.xml same as lastwritetime.


And then new file OSConfig.xml will be copied during upgrade.

 

Attachments

Powered by Wolken Software