Understanding the Citrix Provisioning Target Device Boot Process and vDisk Streaming

Study guide

Technical reference and lesson notes

Citrix Provisioning, commonly called PVS, is a Citrix image management technology that allows multiple target devices to boot from a shared virtual disk, or vDisk, across the network. Instead of maintaining a separate operating system disk for every VM or physical endpoint, PVS allows many machines to stream from a centralized image. The transcript’s main point is that PVS reduces image sprawl by allowing many target devices to use one centrally managed disk image rather than maintaining hundreds of separate images.

In a typical PVS model, the vDisk is placed into Standard Image mode for production use. This means the base image is read-only, and each target device uses a write cache location for operating system writes. Citrix describes Standard Image mode as the model where many computers can boot from the same virtual disk simultaneously, reducing both image management overhead and storage requirements.

How the PVS Boot Process Works

When a target device starts, it is configured to boot from the network or from a configured boot device. The target device contacts the Citrix Provisioning infrastructure to locate the appropriate boot information and assigned vDisk. Citrix documentation states that after a target device is created, it must be configured to boot from the network, have a virtual disk assigned, and have the set of Provisioning Servers configured for boot-time contact.

At a high level, the process works like this:

The target device powers on and attempts to boot from the configured boot method.

The device obtains boot information through PXE/TFTP, BDM, ISO, or another supported boot method.

The target device contacts the appropriate Citrix Provisioning Server.

The Provisioning Server identifies the assigned vDisk.

The operating system is streamed to the target device as needed.

From the perspective of the target device, the streamed vDisk appears like a normal local disk, but the actual disk content is being delivered across the network on demand. This is different from a traditional imaging process where the entire operating system is copied locally before the machine runs.

Why Write Cache Matters

When a vDisk is in Standard Image mode, the base image is read-only. The target device still needs somewhere to write changes because Windows and applications constantly write data during normal operation. That is where the write cache comes in.

The write cache stores the changes that the target device attempts to make while it is running. Depending on the design, that cache may be stored in RAM, on a local cache disk, on the server, or in another supported configuration. Citrix notes that Standard Image mode is used for multiple devices with write cache options, while Private Image mode is used when a single device needs read/write access.

This is one of the most important concepts in PVS. The shared image stays clean and consistent, while each device’s temporary writes are redirected to cache. This is what allows many machines to boot from the same image without corrupting or changing the base vDisk.

Standard Image Mode vs. Private Image Mode

Private Image mode is generally used for image maintenance or single-device access. In this mode, the vDisk is writable and is normally assigned to one device.

Standard Image mode is generally used for production delivery. In this mode, the vDisk is read-only and can be streamed to many devices at the same time. Citrix documentation confirms that a vDisk can be shared by multiple target devices in Standard Image mode or exist for only one target device in Private Image mode.

A practical way to think about this is:

Private Image mode is used when changing or maintaining the image.

Standard Image mode is used when delivering the finalized image to production target devices.

Network and Port Considerations

Because PVS streams the operating system across the network, network reliability and throughput matter. The transcript calls out the importance of using appropriate network capacity and avoiding weak network configurations for production streaming.

Citrix documents several important default ports for Citrix Provisioning. Provisioning Server to Provisioning Server communication uses UDP 6890 through 6909 by default. Provisioning Server to target device communication uses UDP 6910 through 6930 by default. Target device to Citrix Provisioning communication uses UDP 6901, 6902, and 6905. TFTP uses UDP 69 and cannot be changed.

These ports are important when troubleshooting target devices that fail to boot, hang during streaming, or cannot communicate with the Provisioning Server.

Boot Device Management Utility

Citrix also supports the Boot Device Management utility as an alternative to traditional DHCP, PXE, and TFTP boot methods. Citrix describes BDM as an optional method for providing IP and boot information directly to target devices, allowing the target to locate, communicate with, and boot from the correct Citrix Provisioning Server.

BDM can be useful in environments where PXE is not preferred, where network boot configuration is difficult, or where a more controlled boot mechanism is needed. Supported boot device options include USB, CD-ROM/ISO, and hard disk partition.

Provisioning Server Configuration Notes

During PVS configuration, the administrator typically defines the farm, database, site, license server, network adapters used for streaming, and bootstrap settings. The transcript specifically highlights these areas as part of the initial Provisioning Server configuration flow.

Citrix documentation also notes that server stream service ports are configured on the server’s network settings, with the default first UDP port set to 6910 and the default last UDP port set to 6930.

Performance Considerations

Performance depends heavily on the PVS server, vDisk storage, network path, and write cache design. Citrix also supports asynchronous I/O streaming for certain cache modes, which can improve performance but may temporarily increase memory consumption. Citrix recommends testing this feature in a non-production environment before deploying it to production.

In practical terms, a PVS design should pay close attention to:

Network throughput and stability.

Storage performance where vDisks are hosted.

Write cache placement and sizing.

Provisioning Server redundancy.

Firewall rules between target devices and PVS servers.

Whether the environment is using PXE/TFTP or BDM.

Key Takeaway

Citrix Provisioning is powerful because it centralizes operating system image management. A single vDisk can be streamed to many target devices, which reduces administrative overhead and makes image updates more controlled. The important concepts to understand early are the target device boot process, the difference between Private Image and Standard Image mode, the role of write cache, and the network ports required for successful streaming.

For troubleshooting, always confirm the target device can reach the Provisioning Server, has the correct boot method, has an assigned vDisk, and can communicate over the required UDP/TFTP ports.