Home Print Show Topic URL Previous Next
IT Management Suite
Client Management Suite
Server Management Suite
Deployment Solution
Asset Management Suite

About creating an INI file for custom inventory

ITMS 6.x Migration

(Windows only)

The task of creating an INI file is a step in the process for manually migrating your custom inventory script files.

See Manually migrating custom inventory script files

In version 6.x, there are several INI files that control the inventory processes that run on client computers.

These INI files contain batch type commands, similar to the following:

aexauditpls.exe /hidden /output xml
aexcustinv.exe /in .\AeXCustInvStd.cit /out AeXCustInvStd.nsi
aexsnplus.exe /output xml
aexnsinvcollector.exe /hidden /nsctransport /v default /useguid

To run 6.x custom inventory in the 7.5 environment, you need similar INI or batch files to execute the desired command lines. These files need to be in the same directory as the source CIT or XML files. By default, this directory is C:\Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Inventory\Custom Inventory 6.1.

A sample INI file AeXInvSoln.ini is included in this directory by default.

You can include all desired custom inventory script files in a single INI file and have a single software resource, package, command line, and task. However, you may prefer to create multiple INI files: one for each custom inventory or set of custom inventory processes. Then each INI file contains a software resource, package, command line, and task for each custom inventory script file.

Typically, the updated INI file should do nothing more than run one or more aexcustinv.exe command lines, followed by aexnsinvcollector.exe as the last command in the file. However, it may also be necessary to include custom commands or programs in the INI file. In this scenario, it may be necessary to run a third-party or custom application to collect data, create output data, and have custom inventory gather that data and report it to Notification Server. The INI file is essentially a batch file that the client agent executes. Consequently, it is possible to include other pertinent commands in the INI file.

Following is an example of how an INI file for a custom inventory task can look:

aexcustinv.exe /in .\win32_useraccount.xml /out win32_useraccount.nsi
aexnsinvcollector.exe /hidden /nsctransport /v default /useguid

A good practice is to keep the source XML file name and the NSI output file name identical.