Creating and configuring ESD update VMs

Virtual machines (VMs) that are used to update a Managed vDisk are first created on the hypervisor before configuring for vDisk Update Management in Provisioning Services. Supported hypervisors include: Citrix Xenserver, Microsoft SCVMM/Hyper-V, and VMWare vSphere/ESX.

The type of ESD determines the specific steps involved in creating and configuring the VM on the hypervisor. However the following general prerequisites apply to Update VMs regardless of the ESD system selected:

  • Download, install, and configure the appropriate ESD Server software on the server.
  • A VM must be uniquely named on the hypervisor and follow naming conventions equivalent to a Provisioning Services target device name. The name can be up to 15 bytes in length.
  • Only one VM should exist for a Managed vDisk because only one update task can occur on that vDisk at any given time.
  • Citrix recommends allocating at least 2GBs of memory for each VM.
  • Appropriate ESD licenses must be made available and the ESD client software must be properly installed and enabled on the vDisk.
  • Using Microsoft HyperV Server without SCVMM is not supported.
  • Configuring the Update VM, that is used to build the Update vdisk, with multiple NICS when streaming to SCVMM server fails to PXE boot. Citrix suggests using a single NIC or use only one Legacy NIC.
  • Because the image update client requires .NET 3.5 or higher, it must be installed on the vDisk that serves the update VM.
  • Citrix recommends to only apply updates that can be downloaded and installed in 30 minutes or less.

The following ESD systems are supported:

  • WSUS
  • SCCM
Version

Creating and configuring ESD update VMs

In this article