there is but if the timeout is not working on ESXQuery it probably wont work once you alter it in the registry either,
but.. If you want to extend the timeout for a VMware rule its important to realise that rule scanning for VMware is performed using an exe on the beacon called mgsipscan, for all intents purposes its pretty much a flexera variant of Nmap, so here is a cheat sheet on commands you can feed nmap: https://highon.coffee/blog/nmap-cheat-sheet/
one of which is:
--host-timeout TIME
Give up on target after this long
to give it this command you need to alter the following registry key on the beacon:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Discovery\CurrentVersion\DefaultPingSweepOptions
in my instance, below you can see I am feeding this -e eth4 which forces the scanner to only scan network card 4
you can use this to feed commands in, so I suspect most of the things on that cheat sheet I linked above including the timeout should work (although I have not tested that timeout command myself),
here is a previous log where I did this and I have highlighted the section that the registry key populates in the command as an example:
just be wary that here be dragons, this is generally not tested territory and if it isn't required I wouldn't recommend feeding it any additional commands, I only know about this due to a certain scenario when I wanted a rule to scan on my fourth network card only on the beacon and not any others
have you tried increasing the timeout on ESXQuery first to see what value works?
just curious as to if it may be timing out due to delay or just unavailability, in the case of the latter, the timeout adjustments in the registry wont really be relevant
there is but if the timeout is not working on ESXQuery it probably wont work once you alter it in the registry either,
but.. If you want to extend the timeout for a VMware rule its important to realise that rule scanning for VMware is performed using an exe on the beacon called mgsipscan, for all intents purposes its pretty much a flexera variant of Nmap, so here is a cheat sheet on commands you can feed nmap: https://highon.coffee/blog/nmap-cheat-sheet/
one of which is:
--host-timeout TIME
Give up on target after this long
to give it this command you need to alter the following registry key on the beacon:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Discovery\CurrentVersion\DefaultPingSweepOptions
in my instance, below you can see I am feeding this -e eth4 which forces the scanner to only scan network card 4
you can use this to feed commands in, so I suspect most of the things on that cheat sheet I linked above including the timeout should work (although I have not tested that timeout command myself),
here is a previous log where I did this and I have highlighted the section that the registry key populates in the command as an example:
just be wary that here be dragons, this is generally not tested territory and if it isn't required I wouldn't recommend feeding it any additional commands, I only know about this due to a certain scenario when I wanted a rule to scan on my fourth network card only on the beacon and not any others
