Provisioning Server is a fantastic option for image management in Citrix Virtual Apps and Desktops. It offers excellent performance and reliability. On the other hand, while Machine Creation Services can be scaled easily, they can significantly increase storage consumption. For instance, creating a Windows 10 image in MCS typically requires at least 80 GB of storage, in addition to any separate disks needed. To store changes made by users in Machine Creation Services, the differencing disk must be equal in size to the base disk, leading to significant storage consumption. On the other hand, Provisioning Server uses image versioning, creating a new image version every time it's modified. As a result, virtual machines streamed from the server revert to their original state after a reboot, which is similar to their state during the first boot. Using the provisioning server, I start by configuring a virtual machine with either a 2016 or 2019 server operating system. I install the necessary Citrix client provisioning server target device software, followed by installing the required applications. After that, I capture the entire configuration to a file share. The image is then streamed from the file share to the hypervisor, which can handle multiple machines. In some large-scale deployments, we have used a single image to provision thousands of servers. Once the image is captured and stored on the file share, it is set to read-only mode, and any changes made to it are not accepted until it is put in read-write mode. When a virtual machine is rebooted, it returns to its previous state before the changes were made. This feature can be beneficial in situations like a virus outbreak, where a simple reboot of the virtual machines can remove any malicious code or changes. A provisioning server offers a faster recovery time from a bad change and is generally faster than machine creation services. With the provisioning server, changes are not accepted until the read-write mode is enabled, and if a virus outbreak occurs, rebooting the machines restores them to the previous state. On the other hand, machine creation services' speed is dependent on the storage's speed, and recovery time from a bad change can take longer, especially with a large number of devices. If a bad change is made with machine creation services, the replication process can take a while to revert, whereas, with a provisioning server, all machines can be rebooted quickly. Within thirty minutes, I can restore my system to its previous state using the provisioning server.
