Video Screencast Help
Endpoint Management Community Blog

ALtiris NS 6 CPU Identification updates (ProcessorDesc.ini)

Created: 25 Mar 2009 • Updated: 26 Mar 2009 • 5 comments
ag97690's picture
+4 4 Votes
Login to vote

This topic has been discussed in the Altirigos.com (http://www.altirigos.com/vbulletin/inventory-solut...) 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.

Comments 5 CommentsJump to latest comment

aspen's picture

We recently integrated Swimage Encore so that it will work in conjunction with Altiris. If we had this information at the time it would have helped us dramatically. Thanks for the find.

0
Login to vote
jharings's picture

Until the Altirigos discussion took place, and the corresponding KB article with the CPU Ident utility, this really was a grey area for inventory data.

Keep in mind there is still an issue with identifyign CPU cores, which is a Windows WMI limitation. See Altiris KB38797 for details.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

+1
Login to vote
KSchroeder's picture

A few more gathered today from some of our new Dell E6510 machines and an Optiplex 980:

00 0110 0101 0101 Intel Core i5 processor
00 0110 0101 0010 Intel Core i5 processor
00 0110 1110 0101 Intel Core i7 processor

Note that these have to be inserted in the file above the Intel Pentium II processor entry or else they will still be identified as Pentium II (as ours were).  Not sure what happens if you actually do have a Pentium II running around somewhere that matches this family,model,step...?

Also does anyone know if it is necessary/beneficial to update the [Memory Sizes] section with something like:
46h 4096
47h 8192

etc?

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

0
Login to vote
MrSoapsud's picture

I'm getting

00 0110 1111 0110 

on my Core 2 Duo system. The earlier list had this from a Xeon?

0
Login to vote
JHolmez's picture

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.

0
Login to vote