Issue

VMware EFI machines identify themselves differently to VMware BIOS machines.

As a result you may get the following error message; "This machine type was not found in the lookup file".

Affected version

Imaging Toolkit 9.0.2 and later

Solution

Manually amend the images.ini to allow the identification of VMware machines using wildcard matching.

Procedures

Done Task
 
1. Review and update images.ini
 
2. Test

  1. Review images.ini

    The images.ini controls which driver add-on image a machine restores based on the type of machine it is and which operating systems it supports.

    NOTE: The file is updated by the Build Console Deployment Wizard and stored locally in <images path>\drivers
    • Open the images.ini file in the <images path>\drivers folder

    • Review the entry for VMware. For VMware workstation in BIOS mode it will look similar to the following;

      [VMware, Inc.]
VMware Virtual Platform="drivers-vmware|desktop|win8-x64,win8-x86,win7-x86"
    • Change the entry to use wildcards

      [VMware*]
VMware* ="drivers-vmware|desktop|win8-x64,win8-x86,win7-x86"
    • Save the updated images.ini file

    • Copy the updated images.ini file to the TFTP server

      NOTE: On Windows servers this will be:

         %ZENWORKS_HOME%\share\tftp\zimfiles\images.ini

       and on Linux:

         /srv/tftp/zimfiles/images.ini

  2. Test updated files

    • PXE boot a VMware machine in BIOS mode

    • PXE boot a VMware machine in UEFI mode

    • Select and restore a project on both

    • The vmware drivers image will be restored to both and the ENGL build process will run as normal.


If you have any problems or questions about the steps in this TID please contact the ENGL support team