Citrix Provisioning Services (PVS) is one of the two image management technologies available in Citrix Virtual Apps and Desktops and Citrix DaaS. Historically PVS has been used to deliver Citrix Virtual Apps and Desktop workloads (VDA’s) to servers and virtual machines from a single image over the network. However, it can also be used without CVAD/DaaS as a standalone product, physically streaming the OS disk to an endpoint device. These endpoint devices can be “dummy terminals” with no hard drives at all, zero/thin clients, high-end compute and graphics devices, and everything in between. This can include additional use cases for Security and locations with devices without hard drives.
In this episode we discuss the history of PVS and some of its applicable use cases. We also cover some technical aspects of PVS and the benefits enabled by the roll-forward and roll-back of images.
Host: Bill Sutton
Co-Host: Geremy Myers
Co-Host: Todd Smith
Where Provisioning Services Came From
Citrix Provisioning Services (PVS) began as Ardence technology, which Citrix acquired in 2008. It was built to solve a specific problem for a US national laboratory: endpoints needed to boot without a local hard drive that could be corrupted or stolen. The answer was to boot over the network using PXE, with the operating system disk streamed from a central location. When the operating system reads a block of disk, the read goes out across the network instead of to a local drive, which keeps it efficient on a local or near-local network.
It works for both desktop and server operating systems, and the streaming service even handles machine identity. What PVS calls personality, such as machine name, is applied as part of the stream, which removes the Sysprep and domain join steps that came with older imaging tools like Ghost.
The Consistency Problem It Solved
Citrix saw customers struggling with consistency across server farms. In a farm of several servers, drivers, applications, and settings drifted apart, which disrupted application load balancing and caused audit and compliance problems, especially as rules like Sarbanes-Oxley arrived. Imaging each server separately meant drift began as soon as users logged on.
With PVS, one image is created and streamed to many machines. Adding ten more servers meant adding them as objects in the console and booting them from the right file, and every one came up identical. Virtualization later removed the need for identical physical hardware, which improved the model further.
Streaming to Physical Endpoints
Most deployments today stream the operating system to virtual machines, sometimes for thousands of users. The blog highlights a less-seen use: streaming directly to a physical endpoint with no local disk. If a device is lost or stolen, no data is on it, and when it is powered off nothing is left behind. This also suits thin and zero clients, and customers continue to use it this way.
Several scenarios fit this approach. Secure environments avoid local data. Education labs reboot often and can switch images for different classes. Call centers need consistent devices and a fast turnaround without reimaging. One example was a state motor vehicles department that placed a provisioning server in each branch and booted every teller and kiosk machine from one image, managed centrally. A reboot returned a machine to a known good state, and updates were handled during maintenance windows.
Versioning and Rollback
The versioning system is the real strength. A production disk can be in use while a snapshot becomes a version 2 for testing. Switching to the new version is simple, and if a bad patch or update causes trouble, administrators can roll back to a previous version or a known good state almost instantly. This replaces imaging jobs that could take an hour or more per machine.
Newer releases make PVS easier to manage alongside Machine Creation Services (MCS). PVS images can now be managed from the MCS console, so the choice between the two no longer has to be made early in the design. Image portability to Azure or GCP is also emphasized, and target devices can be created in Studio, reducing the need for a separate console.
Licensing and Who Benefits
PVS is included in every current Citrix edition: Private Cloud, Universal Hybrid Multi-Cloud, and the Platform License. Streaming to a physical endpoint, and running PVS in Azure or GCP, require the Platform License. The blog focuses on public sector use, but the technology is just as relevant to commercial organizations, and any organization with higher security requirements, or one that wants the speed and protection of no local hardware, can benefit. It pairs naturally with a thin client approach.