Kemp 360 Central makes use of VMware content libraries when automatically deploying a VLM to a VMware vCenter or VMware ESXi environment. Content libraries are commonly used to deploy machines on VMware. When Kemp 360 Central connects to VMware vCenter or VMware ESXi, it attempts to do the following:

  • Select a content library associated with the datastore that was specified during the deployment workflow
  • Create a new library item in the content library
  • Upload the VLM manifest and disk image files to the library item
  • Instantiate a VLM using the data in the library item

The VMware vCenter or VMware ESXi datastore that is chosen for deployment (either by specifying one manually during deployment or by choosing an existing target environment) must have an existing Content Library defined on it, or the deployment will fail with an error in the Kemp 360 Central Debug and Audit logs that looks like this:

ERROR Could not fetch library for target 'target-environment-name' to deploy 'profile-name' (Library not found).

If you see this error after a failed deployment, you can work around it by manually creating a content library on the VMware vCenter or VMware ESXi datastore. The name of the library does not matter (Kemp 360 Central picks the first one it finds on the datastore) and it can be empty.