Altiris™ Inventory Solution 7.0 SP1 Release Notes

Article:DOC1875  |  Created: 2009-08-05  |  Updated: 2009-10-07  |  Article URL
Article Type


Build number 7.0.1104

Obtaining and analyzing accurate inventory data is an important part of managing and securing your network. Inventory Solution lets you gather inventory data about computers, users, operating systems, and installed software applications in your environment. Inventory policies are easily configured and managed using a central Web console. After you have gathered inventory data, you can analyze the inventory data using pre-defined or custom reports.

Inventory Solution 7.0 SP2 is now available. See article 49315.

This product is part of the following suites:

  • Altiris™ Client Management Suite from Symantec
    For release notes, see knowledgebase article 48420.
  • Altiris™ Server Management Suite from Symantec
    For release notes, see knowledgebase article 48733.

Inventory Pack for Servers:

Altiris Inventory Pack for Servers is a separate product with a separate license that gathers server-based inventory data from servers. It runs on top of Inventory Solution and uses the same Inventory plug-ins architecture, policies, tasks, and stand-alone packages.

For more information see KB article 48821.

This document contains the following topics:

Back to top

New features

The new features of this release are as follows:

Support for additional platforms

Red Hat Enterprise Linux 5.2 and 5.3 are now supported.

Enhanced Inventory policies

Most inventory functions are now performed using policies rather than tasks. In an effort to make inventory gathering easier, the following predefined policies are installed:

  • Collect Full Inventory (enabled by default to run weekly)
  • Collect Delta Hardware Inventory
  • Collect Delta Software Inventory

These are similar to the default policies of 7.0, but the new policies are no longer based on Inventory tasks. The settings that you used to configure in an Inventory task are now set in the policy. For example, the types of data classes that you gather, the schedule, and the advanced options of scan settings and run options are now set in the policy.

Inventory policies have the following changes:

  • You can easily schedule a policy to gather inventory daily, weekly, monthly, or on a custom schedule.
  • In the Advanced settings, the Software Scan Settings tab has been renamed to File Properties Scan Settings.
  • In the Advanced settings Run Options tab, there is a new option to “Report detailed file inventory immediately”. This option is selected by default. This option will gather detailed file inventory when this policy is run. If you unselect this option, only basic file information is gathered at first, and then a second task, the Detailed File Inventory Task will be gather detailed file inventory.
  • In the Advanced setting File Properties Scan Settings tab, additional folders are excluded by default. You should review this to make sure that you gather the information that you are expecting.

Inventory policies now have the following settings that were in 7.0 inventory tasks:

  • You select the kind of inventory that you want to gather: Hardware and operating system, Software, File Properties
  • Advanced options
  • The Advanced options now has a Data Classes tab for selecting the inventory that you want to gather.

You can still create and use Inventory tasks, but in most cases, you will want to limit them to automated tasks used in a workflow. You will want to phase out custom tasks over time.

Because you will primarily use Inventory policies rather than tasks, the Inventory Task Wizard has been removed. Also, The Inventory Task viewer and Inventory Client Task Viewers have been removed. In Inventory Solution 7.0, these viewers were used for creating, modifying, deleting, and viewing the status of Inventory tasks. Inventory Solution 7.0 SP1 focuses more on Inventory policies than on Inventory tasks. You can create, edit, delete, and view the status of inventory policies from the Inventory home page. The task viewers were no longer required and have been removed.

Improved software inventory functionality

The methods for gathering information on the software programs that are installed on Windows-based computers have been enhanced.

  • For Windows-based computers, SP1 Inventory policies now expose the ability gather inventory about installed software applications through the Add or Remove Programs list.
  • When you gather software file properties inventory, by default, the detailed file information is now reported immediately. This is a new option in the SP1 Inventory policies. In 7.0, only basic file information was gathered at first, and then a second task, the Detailed File Inventory Task had to be run. You can still gather detailed software inventory using this two-phased approach if you disable the “Report detailed file inventory” option.
  • You can now have the software inventory data that you gather be integrated with the Software Catalog. The Software Catalog now has a new Software Catalog Data Provider which includes a database containing tens of thousands of known applications. The software programs that are identified through software inventory can be matched to applications in the Software Catalog Data Provider using the new Software Catalog Data Provider Inventory task. This helps ensure accurate software inventory data. The database of known applications will be updated on a regular basis and can be installed using the Symantec Installation Manager. You can also learn more by viewing the Software Catalog Data Provider User's Guide by clicking Help > Documentation Library in the console.
Improved Inventory home page

The Inventory Quick Start has had the Run an Inventory (launch the Wizard) options removed

The Inventory Task Status Web part has been replaced with the Inventory Policy Status Web part. From here, you can do the following:

  • View all Inventory collecting policies, including their targets, schedule, and status (NA means the policy has never been run)
  • Turn a policy on or off
  • Create a new policy
  • Edit a policy
New Report

There is a new software inventory report called Virtualized Software Inventory. This reports applications that are virtual software applications from Software Virtualization Solution whether the layer is active or not.

Enhanced report functionality

Inventory Solution reports now supports security scoping. Depending on the user's privliges, they can only see the resources that they have rights to.

Easier to read "Virtual Software Packages Windows" data class column name

To make it more readable, the "Active" column of "Virtual Software Packages Windows" data class has now been renamed to "Status of layer". It now reports the values "Active" and "Inactive" instead of the previous "True" and "False".

Back to top

Installation and upgrade

Supported platforms

You can gather inventory on target computers running the following platforms:

  • Windows 2000 Professional
  • Windows 2000 Datacenter Server
  • Windows 2003 Web Edition
  • Windows 2003 Standard Edition
  • Windows Server 2003 Enterprise/Datacenter Edition (x86, x64)
  • Windows XP Professional Edition (x86, x64)
  • Windows XP Tablet PC Edition
  • Windows Vista Business/Enterprise/Ultimate Edition (x86, x64)
  • Windows Server 2008 Datacenter/Web/Standard (x86, x64)
  • Mac OS X 10.3.9 - 10.5.x (PPC, x86)
  • Mac OS X Server 10.3.9 - 10.5.x (PPC, x86)
  • Solaris 9 (Sparc)
  • Solaris 10 (x86, x64, Sparc)
  • Red Hat Enterprise Linux 3, 4, 5 (x86, x64)
  • SUSE Linux Enterprise Server 9, 10 (x86, x64)
  • SUSE Linux Enterprise Desktop 10 (x86, x64)
  • VMware ESX 3.0.1, 3.0.2, 3.5

Tested models

This version has been tested on the following Sun models:

  • ULTRA 5
  • ULTRA 10
  • ULTRA 60
  • ULTRA 250
  • Sun-BLADE-100
  • Sun-BLADE-1000
  • Sun-Enterprise-T5220
  • Sun-Enterprise-T5120
  • Sun-Enterprise-220R
  • Sun-T5240
  • Sun-Ultra-5-UPA-PCI
  • Sun-Ultra-10-UPA-PCI
  • Sun-Ultra-60-UPA-PCI
  • Sun-Netra-T1
  • Sun-Netra-T2  
  • Sun-Fire-280R
  • Sun-Fire-T2000
  • Sun-Fire-V20z
  • Sun-Fire-V240
  • Sun-Fire-V250
  • Sun-Fire-V440
  • Sun-Fire-V890
  • Sun-Fire-X4100
  • Sun-Fire-X4150
  • Sun Fire X4200
  • Sun-Fire-X4450
  • Sun-Fire-X4500
  • Sun-Fire-880
  • Sun Fire V40z
  • Sun Fire V490


The following is required for this release:

  • Symantec Management Platform 7.0 SP2 Hotfix 2. See knowledgebase article 49039.

New installation

You can install this product by using the Symantec Installation Manager. You can download the installation files directly to your server or you can create offline installation packages.
For more information, see the Symantec Management Platform Installation Guide (see knowledgebase article 45732).


You can upgrade this product from 6x versions if you run the Symantec Installation Manager on a Notification Server 6x computer. To upgrade from the 6x version, you must first upgrade your 6x Notification Server to Symantec Management Platform 7.0 or later. During the Notification Server upgrade process, you can select to upgrade to the latest version of this product.
For more information, see the Symantec Management Platform Installation Guide (see knowledgebase article 45732).

For upgrade instructions for Inventory Solution 6.x, see 46410

For information about the inventory data that is migrated from 6x, see 49197.

Migration from 7.0

Status of 7.0 tasks and polices -- When you upgrade from 7.0 to 7.0 SP1, the following occurs:

  • The default policies from 7.0 are deleted and replaced with the new SP1 predefined policies.
  • Any legacy 7.0 policies that you created are maintained and can be viewed or modified. The configuration page is modified for SP1 and includes elements of the legacy 7.0 tasks and the new policy pages. 
  • Any default tasks from 7.0 or tasks that you created in 7.0 are maintained. However, they are moved to a “Legacy Tasks” folder (located under Jobs and Tasks > System Jobs and Tasks > Discovery and Inventory > Inventory). You may want to verify that legacy task schedules will not conflict with the new SP1 policies. Some of your own legacy 7.0 policies may depend on legacy 7.0 tasks. You may want to phase out legacy Inventory tasks and use the new SP1 policies.

Installation and Upgrade issues

The following issues are known issues related to installing and upgrading this product. If additional information about an issue is available, click the Article ID link.

Issue Article ID Internal ID
Modified default functionality from installation

When Inventory Solution is installed, none of the Inventory plug-in installation policies are enabled. If you are installing Inventory 7x for the first time, you must manually enable the policies to install the Inventory and Metering Plug-ins. Otherwise you will not gather any inventory data from client computers. If you are upgrading for 7.0, the existing plug-ins will continue to gather inventory, but as soon as possible, you should enable the Inventory and Metering Plug-in Upgrade policies to upgrade the plug-in on managed computers.

Custom Inventory

If you want to continue using the custom inventory scripts that you have for Inventory Solution 6.x, you must do the following:

  1. Back up all the custom inventory scripts that you use with Inventory Solution for Windows 6.1 SP2.
  2. Back up all the stand-alone inventory packages that you had created/customized for gathering the custom inventory.
  3. Back up all the .ini files from NSCap\bin\Win32\X86and bin\Win32\X86\Inventory Solution that invokes the AeXCustInv.exe. These .ini files are specified as a command-line parameter to AeXInvSoln.exe on the “Go To Program” page > Command line” for the inventory tasks.
  4. Back up the NSCap\bin\Win32\X86\AeXPkgEditor.exe.

      If you don’t back up these things and you perform an upgrade, the upgrade will remove them, and you will not be able to use the 6.x custom inventory agent with Inventory Solution 7.0

      See How to use the Custom Inventory from Inventory Solution for Windows 6.1 SP2 with Inventory Solution 7.0.

    Option for creating new Application Metering Policy is not available after upgrading from 7.0 to 7.0.SP1

    For creating new Application Metering Policy you go to Manage > Policies > Software, right-click the Application Metering and click New > Application metering policy. But when you have upgraded from Inventory Solution 7.0 to 7.0.SP1the Application metering policy option is not displayed.

    Note: When you install the Inventory Solution for the first time, the Application Metering Policy option is present.

    Workaround: You can create a new policy by cloning any existing policies and edit it according to your requirements.

    Software discovery information is not reported
     49138  1716007
    When you have edited the baseline files then upgrade from Inventory Solution 7.0 to 7.0 SP1 , SP1 does not install the new default baseline files that are shipped with Inventory Solution 7.0 SP1

    When the system detects during upgrading that the baseline files differ from those that are shipped, then the new default baseline files will not be installed. As a result the default baseline files with the extension *.*SP1 are not available.


    Back to top

    Fixed Issues in this Release

    The following are previous issues that were fixed in this release. If additional information about an issue is available, click the Article ID link.

    Issue Article ID Internal ID
    Application metering plug-in looses the start, stop and deny events every time Altiris Agent service restarts or the computer restarts
    You can configure Application metering plug-in to record start, stop and deny events and send it at a particular schedule. Application metering plug-in records the start, stop and deny events in a local queue and sends these when the schedule expires. If you restart Altiris Agent service or the computer before the schedule expires, Application metering plug-in restarts and it purges the event queue and re-initializes it. This results in loosing of the recorded events so far.

    The summary reported by Application metering plug-in is not affected because of this defect.

    Inventory Plug in for Windows platforms doesn’t install to a non-default location on target computers
    The default location refers to %ProgramFiles%\Altiris. If you have installed the Altiris Agent at a path other than this and roll out policy to install Inventory Plug-in for Windows, it does not get installed in the folder where Altiris Agent was installed; instead it gets installed at %ProgramFiles%\Altiris.
    Inventory Policy can be rolled out on "Agent Time” only

    If server time is selected while scheduling the policy then the policies do not get rolled out on the client computer.

    This issue is fixed by the Symantec Management Platform SP2 HF2 release in September 2009.

    "Enable verbose client logging" option is ignored
    The "Enable verbose client logging" option is ignored. The workaround is to enable Devnote level logging on the Agent for UNIX, Linux, and Mac.
    Licensing behavior

    The behavior of Inventory Solution 7.0 deviates in the area of licensing and changing the status of a non-active computer to active when compared to the behavior of Inventory Solution for Windows 6.1 SP2.

    Stand-alone inventory package fails to post NSE for Notification Server servers configured to use port other than 80
    You specify what port the NS should use under Select the web location for Notification Server" on Symantec Installation Management > Notification Server Configuration page. The default value for this port is 80.
    Stand-alone packages are not accessible through http location if Notification Servers configured to use port other than 80
    Also see "NSE posting fails for Notification Servers configured to use port other than 80" above

    The stand-alone package locations for a stand-alone package is displayed in the rightmost pane on Symantec Management Console > Settings > Discovery and Inventory > Inventory > Inventory Solution > Stand-alone Inventory Packages > Select the stand-alone inventory package.

    These locations includes http as well as file share links to the package. The http link does not contain port number and by default it uses 80 as the port number. If you have configured the NS to use port other than 80, the http link does not work.
    Software scan consumes very little CPU but takes a long time to finish when run through stand-alone inventory package.
    When stand-alone inventory runs the software scan, it processes up to 50 files per batch and then sleeps for 150 milliseconds between two batches, by default. These settings makes the software scan to run slower than that when Inventory process priority is set to Low in case when running an Inventory task.

    With these settings the software scan performed by stand-alone inventory package takes approximately 7 minutes for scanning up to 52728 or 14 minutes for scanning up to 97244 files on an average target computer.

    Possible issues when blacklisting an application that has File version wider than 32 characters and the application belongs to an imported software component or discovered through Inventory task or Targeted Software Inventory
    The File version here refers to File version property that you see when you right click on any binary file and go to Version > Other version information, select File version.

    The File version field in the CMDB database that stores this information is of type nvarchar(32). If the File version for an application is more than 32 characters wide, and you have imported the software component that contains this application, or populate the inventory of this file in to CMDB using either Inventory task or Targeted Software Inventory, the file version gets truncated to the first 32 characters.

    When you blacklist an application, Inventory solution fetches the properties for example, file name, file version, internal name and so on, for that application from the CMDB and defines a policy that tells Application Metering plug-in to block an application where these properties match.

    In case of the truncated File versions, Application metering plug-in receives only the first 32 characters of the File version, it tries to compare these with the original File version that it extracts from the application running on the target computers. Since these two don’t match, it considers the application different and does not match.

    Workaround for this problem is edit the blacklist policy and append * to the File version, to enforce wildcard match, if the file version of the application in original is wider than 32 characters.

    Hyphens (-) are not allowed in the names of data classes
    If you try to create a data class with hyphen (–) in its name, the Manage Custom Dataclasses UI shows error when you press Save Changes

    Hyphen (-) are not allowed in the names of data classes, but the Manage Custom Dataclasses UI fails to handle this character and crashes with following error.

    Altiris Notification Server Error 
    The following error occurred on the page 'DataClassConfiguration.aspx':
    Unknown or unspecified error.

    We recommend not to use hyphen (-) in the names of data classes.

    Reporting of incorrect architecture

    OS Architecture column of OS Operating System

     Software scan now reports the language for Microsoft Office binaries as it is shown in Windows File Explorer

    In environments where an executable supports multiple languages, for example, Microsoft Office installed on target computers running Japanese version of operating system, the software scan from Inventory Solution 6.x and 7.0, used to report "Neutral language" when the /olf switch was be applied, otherwise it was reported as English(United States). Now software scan always reports the “Neutral language” in such scenarios.m dataclass sometimes reports incorrect architecture. Inventory agent gets this value from the WMI and WMI itself reports it incorrectly.

    Error in Agent logs: SMFUtil::GetFileKey() call returned: 3 – Changed the error to trace
    "Unknown error processing summary row" message in agent logs indicating the Altiris Agent has crashed
    Application Monitor Policy fails to send proper data when a ''Command Line'' is defined
    ''Send event notifications in batches'' option generates duplicate rows in the Altiris database
    When an Inventory task is invoked on Windows Vista or other Windows OS, sometimes the Altiris Agent crashes
    Application Monitor Policy reverts to default target upon save
    Uninstalled software appears on the Add/Remove Program Search report
    Memory Configuration by Computer report is not always returning correct results
    The report ''Memory Configuration by Computer'' is showing negative values for the Free Slots column, some computers show multiple times
    Uninstalled software appears on the Add/Remove Program Search report

    Back to top

    Things to know

    The following are things to know about in this release. If additional information about an issue is available, click the Article ID link.

    Things to know Article ID Internal ID
    Custom Inventory

    Additional documentation is provided for using custom inventory.

    Add the link to Symantec Management Console to the list of trusted sites if you want to access the Console by name of the computer instead of localhost

    When you access Symantec Management Console using the name of the computer instead of localhost, for example http://SouthernWingNS/Altiris/Console/, you may face script errors like "permission denied" when navigating to:

    1. In the Symantec Management Console Manage > Jobs and tasks > Create a new job or task
    2. Already created Inventory task > Advanced
    3. Inventory task/policy > Advanced option > Data classes > Select/unselect data class gives "Data could not be loaded"
    Add the link to Symantec Management Console to Internet Explorer > Internet Options > Security tab > Trusted sites. Close all the instances of Internet Explorer. Re-open Symantec Management Console.
    Inventory policies run immediately and make the information available to you as soon as possible

    The default (pre-shipped) Inventory policies are scheduled to run every Monday at 6:00 PM. With this schedule, administrators would have to wait for Monday to get all the computers report their inventory to Symantec CMDB. However, Inventory policies have now been configured to run as soon as possible for the first time apart from the configured schedule, to make the inventory quickly available for administrators.

    The default enabled Inventory policies run as soon as possible after the first time installation.

    The ASAP behavior is implemented in the following way:

    1. Default enabled policies -
      1. Run ASAP after the first time installation.
      2. Run ASAP on any new computer that has joined the target collection.
      3. Run at the defined schedule.
    2. Custom created policies -
      1. If the schedule is set to run daily, weekly, or monthly
        1. Run ASAP after the schedule is created
        2. Run ASAP on any new computer that has joined the target collection.
        3. Run at the defined schedule.
      2. Custom schedules that are set to run once (for example at 3:00 PM on 7/28/09) or on recurring schedule (for example at 4:00 AM on second Friday of every month) run only at the specified time and the run ASAP behavior is not applied.
    Also, because the policies are not forcefully pushed from Notification Server, but rather pulled by Altiris Agent, the run ASAP behavior depends on:
    1. Update configuration interval - default 1 hour.
      This is the default time when Altiris Agent checks with Notification Server, if the Notification Server has any new policies for it to run.
    2. Altiris Agent basic Inventory interval - default 1 day. Notification Server would allow Altiris Agent to pull Inventory policies only if the Notification Server knows that the target computer has Inventory plug-in installed. In a scenario where the target computer does not have Inventory plug-in installed and administrator installs the Inventory plug-in on that computer, the computer will not receive the Inventory policy ASAP until it updates its basic inventory information on the Notification Server.
    The run ASAP behavior for the policies is enabled by default and you can not disable it in SP1.
    How does Inventory process react to maintenance window?

    If you schedule an Inventory policy, it will run on the schedule irrespective of whether any maintenance window is open or not.

    However, if you use a task, it will wait for the window to open. When you have scheduled a maintenance window on a set of computers and you schedule an Inventory task on the same set of computers but don't select the Override Maintenance Window option, the task does not start unless the schedule expires and the maintenance window is open or until the maintenance window opens next time.

    The behavior described above is the same as it was in 7.0 and is as designed.

    Inventory hierarchy and replication
    • Tasks and Policies are replicated from top to bottom.
    • Agent rollout policy is replicated top to bottom.
    • Summary data classes are replicated from bottom to top. The following data classes will be replicated by default: Hardware Summary, Operating System Summary, Monthly Summary.
    • By default, four Inventory reports will work on a top-level Notification Server: Installed versus Used, Application Usage by Computer, Application Resource History, Computer Summary.
    • By default, only the Machines by Operating System will work on a top-level Notification Server:

    If you want to replicate additional data classes, go to Settings > Notification Server > Hierarchy > Replication tab > Resources.

    If you enable all Inventory Solution replication rules (Inventory Data classes-Software, Inventory Data classes-Hardware, Inventory Data classes-User, Inventory Data classes-OS, Inventory Data classes-Metering, Inventory Data classes-Baselining) then all Inventory reports and web parts will work on the top-level.

    Caution: Enabling all data classes for replication will significantly increase the size of the parent NS database as well as add significant network and performance overhead.


    Back to top

    Known Issues in this Release

    The following are known issues for this release. If additional information about an issue is available, click the Article ID link.

    Issue Article ID Internal ID
    Items not replicated:
    • Standalone inventory packages are not replicated
    • Registry baseline tasks are not replicated
    • Plug-in policies are not replicated
    • Custom data classes are not replicated
    Client Inventory:    
    Logged-in users must be in local administrator group (Windows only)

    As in Inventory 6.x, when an inventory task runs in the context of the logged-in user, the user must be a member of the local administrators group. To execute a standalone package and gather the inventory correctly, the logged in user should be a part of “Administrators” group on a local computer.

    Inventory data classes:    

    The following versions of anti-virus products are supported:

    • Symantec/Norton 10.0.359, 10.1 
    • McAfee 8.0.0
    • Trend Micro Client 7.3, 8.0
    • Windows live OneCare 2.5.2900.03 2.5.2900.20

    The following two columns are not populated for McAfee AntiVirus:

    • Centrally Managed
    • Real Time enabled.

    Although the SW Antivirus dataclass appears under the common data classes category on the dataclass selection tree, it is not reported for the non-Windows platforms.

    MS SQL Server Processors and Virtual Software Packages Windows  data classes
    MS SQL Server Processors and Virtual Software Packages Windows data classes remain visible on the resource manager for a computer even when these are either not gathered or not applicable. For example, for UNIX, Linux, Macintosh platforms, these data classes are not applicable. For Windows computers which don’t have SQL Server of Software Virtualization Agent installed, these data classes will not be reported. But these will still be visible on the resource manager.
    Processor types
    Sometimes the Processor type shows up in Reports as Unknown .
    Stand-alone inventory:    
    Package failure
    A stand-alone inventory package will fail if a computer has the 6.x Altiris Agent installed.
    Stand-alone Inventory Packages are not created

    When you have created the Stand-alone Inventory Package, it is displayed in the Stand-alone Inventory Packages list, but not created and available in \\servername\nscap\bin\win32\x86\inventory\standalonepackages\ folder.

    Workaround: See the linked KB article.

     49178  1835825
    Running Inventory tasks in the context of Specified Users:    
    "Roaming User Profile"
    Users having "Roaming User Profile" are not supported with the Specified User context for Inventory task. For more details on what are roaming user profiles, please refer to the link
    Task fails on Domain Controller
    Running an Inventory task in a "Specified User" context on a Domain Controller (DC) machine fails.
    Application metering:    
    Not supported on server operating systems
    We recommend running Application Metering only on the client computers and not on the servers because Application Metering Agent observes each application running on the computer closely, even though the impact of this will not be noticeable on clients but it may result in slowing down the performances of critical servers.
    6.x policies
    Upgraded 6x policies are disabled by default.
    Blacklisting an application multiple times adds the same denial rule multiple times to the Blacklisted application policy

    When you blacklist an application multiple times, the same denial rule is added multiple times to the Blacklisted application policy. This can hamper the performance of the metering plug in, as it compares duplicate rules with the file properties of the launched executable. If you have blacklisted same application multiple times, go to the Blacklisted application policy through Manage > Policies > Software > Application Metering > Blacklisted Applications and delete any duplicate policies.

    Application Denial policy that uses "Product Version" in the metering rule might not work on x64 computers to deny applications

    This issue occurs because of a limitation of Windows. Windows returns different product versions when queried for a 64-bit .exe or given on the executable's Properties > Version UI. When the file properties of the .exe don't match with the ones defined in the policy, the policy is unable to deny or meter such applications.

    Workaround: If the targets for metering are x64 computers, avoid using the Product version to define a metering rule in a policy. Use other items like File version etc. to accurately identify specific executables.

    If you need to use Product version to meter executables, you can use wildcards. To meter an .exe with Product Version 5.2.3790.1830 you can use Product Version value 5.2* to define the rule.

    When you add the rule at Metering policy > Add > Software, the generated metering rule contains very specific information of the executable, including the product version. It is recommended to remove the product version value or to use wildcards as in the above given example.

    It is not possible to add a software resource at Metering policy > Add > Software if the selected software package doesn't have an executable in it

    Application metering can only meter and deny executables. When you add a software resource at Metering policy > Add > Software which doesn't contain an executable, it will not add a rule for that software to the policy. Currently there is no notification shown to the user whenever adding software in the above mentioned way fails.

    Inventory Plug-in for Windows:    
    Inventory Plug-in installer gives error "another version of this product is installed…"

    This issue occurs due to partial un-installation of Inventory Plug-in which could be due to many reasons.

    Warning: Backup your registry before making changes to it.

    Workaround: Delete the following registry keys:

    1. HKLM\SOFTWARE\Classes\Installer\Products\DE4223AD1A748B84682E7AFB2ACB835A
    2. HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\<SID>\Products\DE4223AD1A748B84682E7AFB2ACB835A
    3. HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DA3224ED-47A1-48B8-86E2-A7BFA2BC38A5}

    Note: <SID> is the registry key that changes for each user account. For example: S-1-5-21-1343024091-1637723038-725345543-27193. You need to iterate manually through each <SID> that is present.
    "History tables does not exist" in "Computers with Hardware Changes" report
    When you run the cross-platform "Computers with Hardware Changes", by default, it returns the message: "History tables does not exist."

    For the report to work correctly, you must enable 'History' to get data populated for the reports.

    Do the following:

    1. Go to Settings > All Settings > Settings > Notification Server > Resource and Data Class Settings > Resource History.
    2. Click ‘Resource History’.
          This will open ‘Configuration of resource data class and association history’ in the right pane.
    3. Enable the history of some data classes. (For example, Hardware).

        It will keep History of 6 months by default and Save changes.
    Unix, Linux and Mac Inventory:    
    Not all inventory data is reported on Linux, UNIX, and Mac computers
     The following inventory is not collected:
    • Physical number of processors and cores is reported incorrectly on Linux with 2.4 kerne
    • PointingDevice field "PointingType" is empty on Mac
    • NetworkPort not reported on Linux with kernel 2.4
    • PhysicalMemoryArray: field "MaxCapacity" is not reported on Mac
    • Baseboard not reported on Mac
    • DisplayController fields "MaxRefreshRate" and "VideoProcessor" are empty on Linux, Solaris and Mac
    • Keyboard information on VMware ESX servers
    • HW_PhysicalMemoryArray and HW_PhysicalMemoryLocation on Sun-Blade 1000, Sun Fire 480R,Sun Fire 880,Sun Fire V890, Sun Blade 100, and Sun Ultra 60 UPA/PCI
    • HW_PhysicalMemory, HW_Chassis, and HW_SMBIOS on Solaris where the smbios and prtfru utilites are not installed
    • HW_DiskPartition.Bootable on Solaris platforms
    • The "Family" field of the HW_Processor dataclass on ESX servers 3.x and on Linux-based systems with the following CPUs: Pentium 4, Duo-Core Xeon, multi-core Athlon
    • HW_Keyboard information on VMWare ESX clients
    • HW_PhysicalMemory - "Model" field is not reported on Linux platform (SMBIOS does not contain Model filed for memory modules by specs)
    • HW_SCSIController - "HardwareVersion" filed is empty for controllers "LSI SCSI-2" or "SCSI Fibre Channel Controller"
    • HW_SCSIController - "Index", "MaxTransferRate" and "MaxDataWidth" fields are empty on Solaris, Linux and Mac platforms
    • HW_Processor: field "ExternalClockSpeed" is not reported on Solaris x86 platforms
    • USB devices and Battery information are not reported on Solaris platforms
    Some inventory scans may take a long time to complete
    The default inventory task includes several software rules for scanning that can take quite a long time depending on the platform.

    For example, on Solaris, the /opt or /Volumes on Mac OS directories contains multiple subfolders and files. On weak computers, this can take more than one hour.

    To avoid this, you can exclude such rules and exactly define which directories will be scanned.

    Inventory scan does not scan deeper than system limitations
    Each operating system has a maximum length paths limitation (though not the file system). For example, for Solaris and Mac OS X, by default the limit is 1024 chars, and for Linux, it is 4096.

    As a result, an Inventory scan does not detect files allocated deeper than the system limitations.

    "Manufacturer" field of the Storage dataclass may be empty
    On UNIX/Linux/Mac OS clients that have IDE disks, the "Manufacturer" field of the Storage dataclass may be empty.
    "LastBootUpTime" of dataclass OS_OperatingSystem is not valid for Mac OS X 10.5.x computers
    The field "LastBootUpTime" of dataclass OS_OperatingSystem is not valid for Mac OS X 10.5.x computers.

    This also causes report "Longest Uptime of 'N' Computers" to show incorrect results for Mac OS X 10.5.x computers.

    Missing information under Resource Summary tab
    The drives capacity value has incorrect units in Resource Summary tab.
    Viewing legacy reports of Mac computers fails in Inventory Solution 7.x that is not installed as an 6.x upgrade.

    When you have installed Inventory Solution 7.x for the first time and not upgraded from Inventory Solution 6.x then viewing legacy reports fails. The reason for the error is that during first time installation of Inventory Solution 7.x, no legacy data classes are created.
    You can view legacy reports successfully if you upgrade from Inventory Solution 6.x to Inventory Solution 7.x.

    Some fields of HW_Chassis class may be empty on Mac OS X platform

    Fields may be empty for following reasons:

    1. Information for the fields PartNumber and AudibleAlarm is not available on Mac OS X platform.
    2. Availability of the fields PartNumber and SecurityBreach depends on the current model.


    Back to top

    Where to get more information

    The product installation includes the following documentation:

    Document Description Location

    User’s Guide

    Information about how to use this product, including detailed technical information and instructions for performing common tasks.

    This information is available in PDF format.


    Information about how to use this product. This information is the same as in the User’s Guide.

    Help is available at the solution level and at the suite level.

    This information is available in HTML help format.

    The Documentation Library, which is available in the Symantec Management Console on the Help menu.

    Context-sensitive help is available for most screens in the Symantec Management Console.

    You can open context-sensitive help in the following ways:

    • The F1 key.
    • The Context command, which is available in the Symantec Management Console on the Help menu.

    For more information, you can use the following resources:

    Resource Description Location

    Symantec Management Platform Release Notes

    Information about new features and important issues in the Symantec Management Platform.

    This information is available as an article in the knowledgebase.

    You can also search for the product name under Release Notes.

    Installing the Symantec Management Platform products

    Information about using Symantec Installation Manager to install the Symantec Management Platform products.

    This information is available as an article in the knowledgebase.

    Altiris 7 Planning and Implementation Guide

    Information about capacity recommendations, design models, scenarios, test results, and optimization best practices to consider when planning or customizing an Altiris 7 Infrastructure for your organization.

    This information is available as an article in the knowledgebase.

    Knowledge Base

    Articles, incidents, and issues about this product.

    Symantec Connect (formerly the Altiris Juice)

    An online magazine that contains best practices, tips, tricks, and articles for users of this product.

    Online Forums

    Forums for users of this product.

    Back to top

    Legacy ID


    Article URL

    Terms of use for this information are found in Legal Notices