Since its inception, a Machine Creation Services VM was based on thin cloning technology. Each VM would read from the same copy of the master image while any writes would be directed to a VM-specific differencing disk. Because the differencing disk only contains writes, it is often thin provisioned to save on storage space.
This approach is perfect for pooled, non-persistent desktops. But what about personal, persistent desktops? With the XenApp and XenDesktop 7.11 release, Machine Creation Services now supports full cloned VMs.
Instead of each VM reading from the same copy of the master image, each VM receives a full clone of the master VM’s disk. All reads come from the VM’s cloned disk and all writes go to the same disk.
If you recall, I spent some time discussing the differences between Machine Creation Services and Provisioning Services in order to help administrators better determine when to use which image management solution. In fact, this discussion was spread across 7 different blogs
- Point 1: Resource Delivery Options
- Point 2: Scalability
- Point 3: Storage Optimization
- Point 4: Deployment
- Point 5: On-going Maintenance
- Point 6: Architecture
- Point 7: Summary
With this new capability, I need to make one addition to the summary. Machine Creation Services now supports full cloned VMs.
Daniel (Follow on Twitter @djfeller)
XenApp Advanced Concept Guide
XenApp Best Practices
XenApp Videos
The technology works with both xa that xd catalog? I can not find the option in the MCS wizard selecting “Server OS”. Thanks
LikeLike
We also cannot find the option.
Is this new feature not available for “Server OS”?
LikeLike
It is only with a desktop-based OS catalog.
LikeLike
Hello ,
What happens now for the existing VMs when I update the master?
LikeLike
Nothing. When you go with the dedicated desktop model (regardless if using thin or thick provisioned), once that VM is created, it is no longer updatable via MCS. Dedicated, persistent desktops requires 3rd party desktop management solutions.
LikeLike
Hi Daniel,
I found out that MCS can provision maximum 9 Full Clones at a time. How can I increase this threshold? I don’t think I’ll have a storage issue as the storage is based on a very large all-flash VSAN cluster.
Thanks
LikeLike
In MCS full clone, do we need to place master image in all the storage LUN’s to create VM’s in storage LUN’s? or having master image in one LUN is sufficient?
LikeLike