ESX Discovery = CPU Name, CPU Type

[Doci1]

Hi, I have a question, why horizontal Discovery on Windows Servers is filling:

cpu_name: Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz

cpu_type: GenuineIntel

but ESX probe VMWare - vCenter ESX Hosts is OOTB filling :

cpu_name: (empty)

cpu_type: Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz

Is there any reason for that?

[AJ-TechTrek]

Hi @Doci1 ,

Please check the permission on your Windows Credentials , or test the pattern for same IP using Debug Pattern Option.

As ESX Server will discovery using different pattern as well as different credentialsPlease appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 
Thank You
AJ - TechTrek with AJ
Linkedin:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community Rising Star 2024 are required for that.

[Doci1]

My question is that what is the reason that Horizontal DIscovery is filling the value to "cpu_name", but ESX patterns the same value to "cpu_type"

[AJ-TechTrek]

Hi @Doci1,

Please check the both Probe\Pattern and Mapping for CPU type and CPU field, you will get your answer.

Here is the details from Windows CPU probe.

if (JSUtil.notNil(Win32_Processor.Name))

current.cpu_name = Win32_Processor.Name;

if (JSUtil.notNil(Win32_Processor.MaxClockSpeed))

current.cpu_speed = Win32_Processor.MaxClockSpeed;

if (JSUtil.notNil(Win32_Processor.Manufacturer))

current.cpu_type = Win32_Processor.Manufacturer;

if (processors.length > 0)

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 
Thank You
AJ - TechTrek with AJ
Linkedin:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community Rising Star 2024

[Doci1]

Hi, thx but this is not what i am asking for. The question is why the same value is once "name" for windows servers the same value is "type" for ESX.

It is probably that ESX are virtuals? that might be the reason.