Unable to Add Virtual Host Devices From UDD to Inventory

Version 1

    Verified Product Versions

    LANDESK Management Suite 9.6

    Unable to Add Virtual Host Devices From UDD to Inventory

    discovered VM Host machines with UDD and after right clicking on the device and selecting 'Add to Inventory', the device never show in inventory under Virtual OS Hosts.

    This issue can be caused by a couple different thing.

    1. If you installed the LANDesk agent on the core server, then uninstalled the agent.  A reinstall of the client will not regenerate the needed files as these are created during the core install. These default (31) will need to be copied from a core that has not had the an agent installed, as a starting point, but the below resolution steps will need to be followed.  Or you can restore the LDClient folder if you have a backup from prior to the agent being installed. (Make sure the back up is from the correct service pack level)

    2. If you have pointed the core server at a different database besides the one that the core was installed with.


    What is happening is the there are several key files that are needed for the Virtual Host discovery to work and also needed to move the VM Hosts into the Inventory.  Just copying these (31) files back into the \LDClient folder will not fix the issue completely.  Doing this will usually fix the UDD discover, but not the inventory issue.  The v12n.sk file is a type of certificate file needed to add the devices into inventory, what happens is that when this file gets copied in from another core or is deleted, there is a reference to a key value in this file that is also in the database.  If these do not match, then VM Host devices will not get added to the database.



    - Rename the v12n.sk file in the ...\LANDesk\LDClient folder if is exists.

    - Run the following command on the core server. DriveLetter:\Program Files (X86)\LANDesk\ManagementSuite\Virt_ESX_Manage.exe /genkey=ESX

    (Replace the DriveLetter for whatever drive LANDesk is installed on, and remove the (x86) if you are not on 2008 R2 X64 server)


    This will remove the old reference from the database, recreate the v12n.sk file and re-enter the correct reference in the database.