Why are 64-bit computers sometimes reported as 32-bit computers when Basic Inventory is sent on initial installs of the Altiris Agent?


Article ID: 181573


Updated On:


Management Platform (Formerly known as Notification Server)




When the Altiris Agent is installed on 64-bit computers, the computers are added to Windows 32-bit collections. Testing has revealed that after two or more attempts by the Altiris agent to send Basic Inventory to the Notification Server, the 32-bit collections are updated and the computers appear in the 64-bit collections as expected.

Notification Server 6.0.6074 SP3 R7
Windows 64-bit computers
Microsoft Windows XP 5.2 Professional (Service Pack 2)

This issue is caused by a Windows API call to IsWow64Process that is made by the Basic Inventory component when the tool attempts to locate the "System Type" in order to populate the AeX AC Identification table. When this call is made, the API call provides the wrong System Type value. After several calls to the IsWow64Process, the correct System Type value is returned.

This issue is scheduled to be resolved in Notification Server 7.0 (the entire architecture has changed so this particular change was made as part of a larger change to the fundamental structure).

A possible workaround for Notification Server 6.x is to identify a unique characteristic on those systems besides using System Type Win64 that will help to exclude them from 32-bit machines (like operating system, a specific naming convention, etc.). One example would be a unique characteristic was the operating system version for 64-bit computers: Microsoft Windows XP 5.2 Professional (Service Pack 2). Since the operating system version is one of the first values collected previous and after the Altiris Agent is installed (see article 22596, "What inventory is recorded with a Basic Inventory?"), it can be used as unique characteristic to avoid getting those 64-bit computers on 32-bit collections right after the Altiris Agent is installed.

To use this method, create a Collection that will contain resources that match that operating system version criteria and use that Collection as exclusion on the 32-bit Collections. Here is an example of the query that can be used to create the Exclusion Collection:

select [Guid] from vItem
where [ClassGuid] in ('539626D8-A35A-47EB-8B4A-64D3DA110D01','1F54FC7C-6DFB-4EFE-AB2B-97194CDD75E8') --These GUIDs are for Computers and Virtual Machines Resource Types
and [Guid] in (
                         select [_ResourceGuid]
                         from [Inv_AeX_AC_Identification]
                         where [Inv_AeX_AC_Identification].[OS Name] = 'Microsoft Windows XP'
                         and [Inv_AeX_AC_Identification].[OS Type] = 'Professional'
                         and [Inv_AeX_AC_Identification].[OS Version] = '5.2'
                         and [Inv_AeX_AC_Identification].[OS Revision] = 'Service Pack 2'