This topic has been discussed in the Altirigos.com (http://www.altirigos.com/vbulletin/inventory-solution/8420-lets-collaborate-cpu-not-reporting-correctly.html) but I thought I would get this to others who might not look at that forum too. For the NS 6 ( Not NS 7 ) CPU identification is limited and not updated any more. So to help update it some there happens to be a wonderful tool in the Altiris Knowledge base called AeXCpuIdent.exe ( KB # 17610 ) which will get you the CPU information of whatever Intel chipset it is ran on. Example Processor Info =========================================== Vendor: GenuineIntel Family: 0110 Model: 1101 Step: 1000 Type: 00 BrandId: 10110 Of course there is other ways of getting this information such as KB article 39909 which has you use the dbgview.exe from Microsoft. Which I find to take a whole lot more time then I can spare. So using this tool it lists out the series of numbers you will need to include in your all might processordesc.ini. This file is located on your NS server under NSCap\Bin\Win32\X86\Inventory Solution. So after you get your CPU numbers I would recommend you look under computer manger and get the official Microsoft CPU name and have that handy for this file. Let’s now put it all together in the processorDesc.ini file When you edit this file it will start with the [GenuineIntel] structure where all Intel names will be listed, Then AMD and so on. Example of File: GenuineIntel] 00 1111 0011 0100 Intel Pentium 4 Processor 00 1111 0100 0001 Intel Pentium 4 Processor 00 0110 1111 1101 Intel Core 2 Duo Processor 00 0110 1111 0110 Intel Xeon Processor 00 0110 1111 1011 Intel Core 2 Duo Processor 00 1111 0100 0011 Intel Xeon Processor (Hyper Threaded) 00 0110 1111 0111 Intel Xeon Processor 00 0110 1110 1100 Intel Core Duo Processor 00 1111 0100 1000 Intel Xeon Processor 00 0110 0100 1010 Intel Pentium 4 processor 00 0110 1111 0010 Intel Core 2 Duo processor 00 0110 0111 1010 Intel Core 2 Duo processor 00 0110 1101 0110 Intel Pentium M 00 1111 0110 0100 Intel Xeon Processor 00 1111 0100 1001 Intel Pentium 4 Processor (Hyper Threaded) 00 0110 0110 1010 $Mem128 Intel Mobile Celeron processor 00 0110 0110 1010 $Mem256 Intel Mobile Pentium II processor 00 0110 0110 1101 $Mem128 Intel Mobile Celeron processor 00 0110 0110 1101 $Mem256 Intel Mobile Pentium II processor 00 0011 0000 Intel386 DX processor 00 0011 0000 Intel386 SX processor 00 0011 0000 Intel386 CX processor 00 0011 0000 Intel386 EX processor 00 0011 0000 Intel386 SL processor 00 0011 0001 Intel386 SL processor 00 0011 0100 RapidCAD coprocessor 00 0100 0000 Intel486 DX processor 00 0100 0010 Intel486 SX processor 00 0100 0011 Intel487 processor 00 0100 0011 IntelDX2 processor 00 0100 0011 IntelDX2 OverDrive processor 00 0100 0100 Intel486 SL processor 00 0100 0101 IntelSX2 processor 00 0100 0111 Write-Back Enhanced IntelDX2 processor 00 0100 1000 IntelDX4 processor 01 0100 1000 IntelDX4 OverDrive processor 00 0101 0001 Intel Pentium processor 00 0101 0010 Intel Pentium processor 01 0101 0001 Intel Pentium OverDrive processor for Pentium processor 01 0101 0010 Intel Pentium OverDrive processor for Pentium processor 01 0101 0011 Intel Pentium OverDrive processors for Intel486 processor-based systems 00 0101 0100 Intel Pentium processor with MMX technology 01 0101 0100 Intel Pentium OverDrive processor with MMX technology for Pentium processor 00 0110 0001 Intel Pentium Pro Processor 00 0110 0011 Intel Pentium II processor, model 3 00 0110 0101 Intel Pentium II processor 00 0110 0111 Intel Pentium III Processor 00 0110 1000 Intel Pentium III processor Special ------------------------------------------------------------------ Using this one as an example: 00 0110 0111 1010 Intel Core 2 Duo processor Now let’s define each column for Intel 00 is the type 0110 is the family 0111 is the model 1010 is the step And currently as far as I can see BrandId is not used right here. So with this knowledge you can update your processor description file and help get better inventory data until you are ready to switch over to NS 7. PS from what I have experienced is that the ones with a step ID should go first since it seems like a check list that looks for the first one and returns that name. I could be wrong but that is how it seems to work on my server currently.
Hey guys, I am having this very same issue in my environment, but found an additional issue.
I followed HOWTO8433 and ran the debug info. Apparently the AeXMachInv.exe /norbin is only detecting the first 6 bits of the CPU ID. Meaning the debug details only report 00 0110 and nothing else. Now I added my specific CPU ID: 00 0110 0111 1010 for Intel Mobile Core2 Duo, with the other Core2 Duo processors, and it still reports my pc as a P3. So I put the new ID at the top of the list, and it then reports as the Mobile Core2 Duo.
Is there a way to fix the AeXMachInv.Exe to properly read the whole processor ID? Symantec's own CPUIdentifier.exe properly reads the cpu just fine.