When Intellisig software discovery was added to the product in the ITCM r12.5 SP1 FP1 release, this introduced some changes in ContentUtility.exe for handling Intellisig content. If the ContentUtility.exe process is not used carefully, it could result in the corruption described above.
ContentUtility.exe can be invoked to export/import specific types of software content data based two configurations:
- The content_utility.xml file is used to configure the export and/or import operations.
- A series of command line switches are passed to the ContentUtility.exe process to configure the export and/or import operations.
The special characters are introduced in the export operation of the Content Utility when the following line is set in the XML file:
Or when the ContentUtility.exe is passed the following switch when invoked via CLI:
It is 100% expected to observe the special characters, '&%n&%', in the 'ca_software_signature' flat file generated by the ContentUtility export operation! Again, these characters will be written to the flat file when the intellisig detail option is specified.
In order to avoid corrupting your ca_software_signature table, the import operation MUST have a matching intellisig detail option set! Corruption is introduced in the following scenarios:
- When using the content_utility.xml file, specifying "<intellisig_detail>yes</intellisig_detail>"for the export operation, but specifying the opposite for the import operation, "<intellisig_detail>no</intellisig_detail>".
- When invoking ContentUtility.exe via CLI, specifying "/INTELLISIGDETAIL YES" for the export operation, but forgetting to specify " /INTELLISIGDETAIL YES" during the import operation. By default "/INTELLISIGDETAIL NO" is assumed by the ContentUtility.exe process if the switch is not explicitly specified.
- When using the content_utility.xml file, specifying "<intellisig_detail>yes</intellisig_detail>", but invoking the import operation via CLI, and not specifying the "/INTELLISIGDETAIL YES" switch.
In some scenarios, the export and import operations may not occur during the same execution of the ContentUtility.exe process. For example, one execution performs the export operation, and some other execution performs the import operation later. Careful consideration must be taken around the intellisig detail option to ensure ca_software_signature is not corrupted on import.