[General] [GLPI Toolbox]

[fmeunierFKY]

Your question

hi,

inventory of stand-alone Esxi is OK but it is possible to inventory VMware ESxi with GLPi ToolBox from the VCENTER ?

GLPI Agent version 1.15

[g-bougard]

Hi @fmeunierFKY

yes, you can provide credentials for ESX and use a netscan task.

[fmeunierFKY]

Hello Guillaume, this what I have done

Credential

Scheduling

IP Range

Invent

At the end 2 files are produced below, 1KB

From command line it words

c:\Program Files\GLPI-Agent\glpi-esx.bat -host vp-vcsa-a01.escota.net -user Domain\User -password "XXXX" -path c:#support\toto --json

[g-bougard]

And ? What's the problem ?
It seems you have 2 inventories in XML format. Are they wrong ?
If you have any error, share the debug2 output you can find into the log frame.

[fmeunierFKY]

there is only 12 lines in files

Debug 2

[info] Starting VCENTER network scan task job...
[info] Running VCENTER task...
[debug] initializing job 1
[debug] initializing block 10.40.215.10-10.40.215.12
[debug] Current netdiscovery run expiration timeout: 45 minutes
[debug] using 1 netdiscovery worker
[debug] starting job 1 with 3 ips to scan using 1 worker
[debug] #1, scanning 10.40.215.10
[debug] #1, - scanning 10.40.215.10 with netbios: no result
[debug] #1, - scanning 10.40.215.10 with echo ping: success
[debug2] #1, executing arp -a 10.40.215.10
[debug] #1, - scanning 10.40.215.10 in arp table: no result
[info] #1, Netdiscovery result for 10.40.215.10 saved in C:/GLPIAgent/netdiscovery/10.40.215.10.xml
[debug] #1, #1, worker termination
[debug] #2, scanning 10.40.215.11
[debug] #2, - scanning 10.40.215.11 with netbios: no result
[debug] #2, - scanning 10.40.215.11 with echo ping: success
[debug2] #2, executing arp -a 10.40.215.11
[debug] #2, - scanning 10.40.215.11 in arp table: no result
[info] #2, Netdiscovery result for 10.40.215.11 saved in C:/GLPIAgent/netdiscovery/10.40.215.11.xml
[debug] #2, #2, worker termination
[debug] #3, scanning 10.40.215.12
[debug] #3, - scanning 10.40.215.12 with netbios: no result
[debug] #3, - scanning 10.40.215.12 with timestamp ping: no result
[debug2] #3, executing arp -a 10.40.215.12
[debug] #3, - scanning 10.40.215.12 in arp table: no result
[debug] #3, #3, worker termination
[debug] #3, Netdiscovery worker terminated
[info] #3, VCENTER: VCENTER network scan done
[debug] #3, Task run in 3.445 seconds

[g-bougard]

Probably ESX task is not installed. By default, this task is not installed on windows.

From GLPI-Agent installation folder, try to run the following command to check if the task has been installed:

glpi-agent --list-tasks

If you don't see it in the list, you has to reinstall agent using ADDLOCAL=feat_ESX if you installed it with the vbs script or from the command line or select it in the installer UI.

[fmeunierFKY]

i have this

c:\Program Files\GLPI-Agent>glpi-agent --list-tasks

Available tasks :

• Inventory (v1.22)
• Collect (v2.11)
• NetDiscovery (v6.8)
• NetInventory (v6.8)
• Deploy (v3.5)
• RemoteInventory (v1.8)
• ESX (v2.14)

target local0: local C:\GLPIAgent
Planned tasks: RemoteInventory,Inventory

target server0: server https://xxx.com/
Planned tasks: NetInventory,Deploy,RemoteInventory,ESX,Inventory,Collect,NetDiscovery

[g-bougard]

Oh, I just see you forgot to associate credentials to ip range. This has to be done from the ip range configuration.

[fmeunierFKY]

Hello

seems to not work, even with credential set.

below the file produced

content of the file

yaml file

configuration:
  agent_home_navbar: yes
  archive_format: 7z
  credentials_navbar: yes
  default_columns: name|mac|ip|serial|tag|source|type
  display_options: 30|0|5|10|20|40|50|100|500
  inventory_navbar: yes
  inventory_tags: esx
  iprange_navbar: yes
  language: en
  languages: en|fr
  mibsupport_disabled: no
  mibsupport_navbar: yes
  networktask_save: C:\GLPIAgent
  remotes_admin: yes
  remotes_navbar: yes
  remotes_show_expiration: yes
  remotes_show_password: yes
  remotes_workers: 1|2|5|10|20
  results_navbar: yes
  scheduling_navbar: yes
  session_timeout: 86400
  threads_options: 1|5|10|20|40
  timeout_options: 1|2|5|10|30|60
  updating_support: yes
  yaml_navbar: yes
credentials:
  VCENTER:
    password: xxxxxxxx
    type: esx
    username: XXXX\xxxxx
ip_range:
  VCENTER:
    credentials:
      - VCENTER
    ip_end: 10.40.215.11
    ip_start: 10.40.215.11
jobs:
  VCENTER:
    config:
      ip_range:
        - VCENTER
      tag: esx
      target: local0
      threads: 1
      timeout: 60
    enabled: no
    last_run_date: 1760339932
    next_run_date: 1760912459
    scheduling:
      - Monday
    type: netscan
scheduling:
  Monday:
    duration: 01:00
    start: 00:00
    type: timeslot
    weekday: mon
  VCENTER:
    delay: 24h
    type: delay

[g-bougard]

Hello,

you forgot to share the debug2 output you can find into the log frame.

About username, if you have \ into the string, can you try adding a second one to have \\ ?

[fmeunierFKY]

[g-bougard]

Oh, did you see where the inventory is really saved ? You shared the netdiscovery XML content, which is not the full inventory.

[fmeunierFKY]

it is almost empty

10.40.215.11.xml

[g-bougard]

The inventory is really there:

[fmeunierFKY]

my vmware infra is 32 esxi composed, and in my file --> VP-MHSS-A02.ESCOTA.NET-2025-10-13-09-25-42.xml I've only esxi showing up.

VP-MHSS-A02.ESCOTA.NET-2025-10-13-09-25-42.xml

[g-bougard]

Yes, you'll have to scan all other ESX computers. If they are on one ip range, this should be simple.

[fmeunierFKY]

this is the IP of my VCENTER, I should retrieve all my esxi ?

[g-bougard]

Yes, you should.