Customizing Symantec Altiris Connector For Altiris Patch Management

Document created by yeola02 Employee on Sep 2, 2014
Version 1Show Document
  • View in full screen mode

CA SAM 12.9

Symantec Altiris 7.1

 

Out of the box, CA provides a standard Symantec Altiris connector located in the CA SAM 12.9 install media:

 

..\CA SAM\htdocs\docs\connectors\standard\symantec\altiris\7.1

400_symantec_altiris_devices.xml

500_symantec_altiris_usage_raw.xml

 

You may find that you only use the Patch Management component of Altiris. The OOTB connectors will not work in this case. The altiris connector 400*.xml is trying to build a joint with tables: vHWProcessor, Inv_AeX_AC_Identification, Inv_HW_computer_System, Inv_HW_Logical_Device etc, but in Patch Management these tables do not exist. You may see these error messages in your logs:

 

Errors occurred:

                query #1 failed; error: asp_db->x_query(): failed. error: query error:

code: 208, message: #1: SQLSTATE: 42S02; code: 208; message: [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name 'Inv_HW_computer_System'.

 

Here, we have the two customized xml files attached. They would be useful if you only utilize the Patch Managment part of Altiris 7.1

Outcomes