Deploying VMware Fusion 5 with a custom package

In a precedent post a method to mass deploy VMware Fusion was documented. This is the official solution offered by VMware but a problem can occur with the script include in the metapackage when using Absolute Manage to deploy it.

With some reverse engineering a way was found to create our own (minimal) install script :
– The official package sets all settings to the file “/Library/Preferences/VMware Fusion/config”
– The official package uses “VMware” to set the license key

The “config” file is used on the first launch to set the initial settings. I’m not sure if the file is used later or not. With this file, you can :

  • Disable the EULA
  • Disable the antivirus check
  • Disable the registration
  • Disable the license message
  • Disable the data collection message
  • Change the support URL (hide the serial number when asking support)

Below an example of the “config” file with the correct syntax that can be deployed in “/Library/Preferences/VMware Fusion/” :

.encoding = "UTF-8"

fusion.ui.eula.skipPrompt = "TRUE"
fusion.ui.antivirus.skipCheck = "TRUE"
fusion.ui.registration.skipPrompt = "TRUE"
fusion.ui.registration.hideLicense = "TRUE"
fusion.ui.dataCollection.skipPrompt = "TRUE"
fusion.ui.getSupport.url = "https://your own support website"

To add the serial number to VMware Fusion 5, you can use the script below as postscript in a custom package. This script has three variables to configure :

  • The serial number (SERIAL_NUMBER)
  • Your company name (COMPANY_NAME)
  • The fullpath of VMware Fusion 5 if not in Applications (FUSION_PATH)

COMPANY_NAME="My company"

PRODUCT_NAME="VMware Fusion for Mac OS"
if [ -d $FUSION_PATH ]; then
"$FUSION_PATH/Contents/Library/vmware-licenseTool" enter $SERIAL_NUMBER "" "$COMPANY_NAME" $PRODUCT_VERSION "$PRODUCT_NAME" ""


Leave a Reply

Your email address will not be published. Required fields are marked *