When you create or edit a stand-alone inventory package, you can configure the its options. You define the type of inventory gathered, where to store the data, and other options. You can view the properties of a package from the main Stand-alone Inventory Packages page.
When configuring where to store the inventory data, you select an option based on what access target computers have to the Notification Server computer.
The option Show progress causes a dialog box to open on the computer that is running the package. The dialog displays the data classes that are gathered and then where the data is posted after the inventory is completed.
After running on the target computer
The option Keep the inventory cached for future comparisons keeps the inventory data cached so that you can compare the inventory data in the future. Inventory data comparisons are performed using command-line switches.
This option lets you configure where the inventory data is stored after it is gathered.
You can choose from the following options:
If target computers can communicate with the Notification Server computer using HTTP (port 80 open) or HTTPS (port 443 open), you can use this option. When the package is run, the inventory data is automatically sent to the Notification Server computer.
The URL that is used is displayed on the page.
You can store the data on the local computer, on a share, or on the Notification Server computer. When the package is run, the inventory data is automatically saved on that share. Inventory data files are stored with an NSE extension.
If target computers can access a shared folder on the Notification Server computer, you can store it directly to a share on the server.
The Notification Server computer share to use with this option is:
If the target computer cannot access the Notification Server computer, you can store the inventory data on the local computer. You can also store it on another computer that is not the Notification Server computer. You must then manually copy the files to the Notification Server computer.
You may have to use this option for the following situations:
Computers that are not regularly attached to the network
Computers that are outside the intranet that the Notification Server computer is on.
You can specify a share or a path on the local computer. If you specify a local path, that folder is created on each target computer. For example, C:\Inventory_Data
Inventory data files are stored with an NSE extension.
You can also use environment variables when specifying the path to folder. For example: \\IntermediateShare\%computername%
If stand-alone inventory fails to post the NSEs to the specified target (an HTTP or HTTPS location or a folder), it deletes the NSE, NSI, and BAK files from the folders %programfiles%\Altiris\NSI and %programfiles%\Altiris\Inventory\Outbox. When the stand-alone inventory runs next time, it recreates the inventory. The NSI and Outbox folders are removed if they are empty. This procedure is done to make sure stand-alone inventory reports correct inventory to the Notification Server computer even if users are running stand-alone inventory packages with the /SendChangedInventory command-line switch.
You can configure advanced settings for running a stand-alone inventory package.