ESXi - VMWARE Guests (Problems)

[jeremy]

What versions of ESXi does Lansweeper support?

Currently getting weird issues under "vmware" guest it shows multiple instances:-

Server1 (192.168.0.3) 4096 MB
Server1 (192.168.0.3) 4096 MB
Server1 (192.168.0.3) 4096 MB
Server1 (192.168.0.3) 4096 MB
Server1 (192.168.0.3) 4096 MB
Server1 (192.168.0.3) 4096 MB
Server1 (192.168.0.3) 4096 MB
Server1 (192.168.0.3) 4096 MB
Server1 (192.168.0.3) 4096 MB
Server2 (192.168.0.4) 4096 MB
Server2 (192.168.0.4) 4096 MB
Server2 (192.168.0.4) 4096 MB
Server2 (192.168.0.4) 4096 MB
Server2 (192.168.0.4) 4096 MB
Server2 (192.168.0.4) 4096 MB
Server2 (192.168.0.4) 4096 MB
Server2 (192.168.0.4) 4096 MB
Server2 (192.168.0.4) 4096 MB

(It does detect all the servers but it appears to pickup other VMs which are not on this ESXi Server)

When I hover over the instances it's point to different/other IPs/Server information.

I have tried upgrading from v6.0.100.75, Lspush 6.0.100.27, SQL 150 (11 oct 2017) to v6.0.100.94.

After upgrading I tried the below items:-

- Remove ESXi Only & Rescan (Same issue)
- Remove VMWARE Only & Rescan (Same Issue)
- Remove ESXi & problem VMWARE & then Rescan (Same Issue)


Please advise best way to fix this issue

Thanks 🙂

[Esben_D]

Unfortunately, I don't have a list of supported ESXi versions. It could be that it is version related. The only thing I can recommend other that updating to a more recent ESXi version to see if it fixes the issue is to update Lansweeper. However it is unlikely updating Lansweeper will fix the issue since there have not been any recent fixes for VMWare servers.

The last change was made in version 6.0.0.63 (31 March 2017)

Fixed:#534683 Due to changes in the HTTPS title and certificate issuer of VMware servers, Lansweeper may fail to scan MOB (Managed Object Browser) data of servers running a recent ESX(i) version

You can update Lansweeper by following this knowledgebase article: https://www.lansweeper.com/kb/118/updating-your-installation.html

You can find our changelog here: https://www.lansweeper.com/changelog.aspx

[jeremy]

Hi Cahrles.X

Thanks for you response it must be a problem with Lansweeper detection of different ESXi versions I have running.

As each PC has a unique key + DNS resolves correctly.

Do you know if there is a list of supported ESXi versions as ours is a little old?

(If not will need to contact support)

[Esben_D]

I assume the asset is correctly and fully scanned with SSH (without errors). As such either this information is stored as such in the server's MOB or Lansweeper is indeed not displaying it correctly.

Additionally it is important to know how Lansweeper identifies assets which is explained here: https://www.lansweeper.com/kb/149/how-lansweeper-uniquely-identifies-assets.html

VM's can have a different domainname which is why they are listed as a separate asset. This could potentially be resolved by enabling Computer Renaming Detection under Configuration\Server Options. With this option enabled, Lansweeper will merge Windows computers with differing unique ID's if they have a matching MAC addresses, model names and serial numbers when the Windows computers are next scanned. For more information on using this option and how it works, you can check this article. Make sure to rescan VM guest and host though. https://www.lansweeper.com/kb/87/windows-rename-detection.html

If the issue does persists I would recommend contacting our technical support team with the following information. This will allow them to troubleshoot the issue correctly.

• Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper server.
  
• Screenshots of one problem machine's Lansweeper webpage. Show us the following tabs: Summary, Errors (if it exists).
  
• Screenshot of a connection test performed to the same problem machine with devicetester.exe, which can be found in Program Files (x86)\Lansweeper\Actions on your Lansweeper server. Perform the test from your Lansweeper server to the problem machine, submit any relevant (SNMP or SSH) credentials and show us the entire test window.