hasemclass.blogg.se - Mcs calculation tool

Mcs calculation tool full#
Mcs calculation tool windows#

Virtual disk of 13.63GB - this is the image as I’ve built it including Windows, applications, and the XenDesktop 7.9 VDA.

Initially, the image has two snapshots (or checkpoints) created in the process of provisioning and updating the image.

Mcs calculation tool windows#

The master image is Windows Server 2012 R2 or 2016 with a set of applications including Office. Note that Hyper-V allows for modifying the paths for virtual machines (config files), virtual hard disks and Smart Paging files, so the folder structure shown in my environment in the screenshots below may differ to yours. The environment is based on Windows Server 2016 and System Center Virtual Machine Manager 2016. To keep this size exercise simple, I have used a single data store that contains both my master image and the Machine Catalogs.

Mcs calculation tool full#

Full Clones - new in XenDesktop 7.11 is the ability to deploy full clones from a master image and rely on the storage platform to provide optimisation.IO optimisation enables a cache in RAM with overflow to disk Delta Clones with Storage Optimisation - this is the new default option for MCS deployments since XenDesktop 7.9.Delta clones work for XenApp, pooled and dedicated clone VMs

In Hyper-V parlance, this is referred to as a differencing disk.

Delta Clones - this has been the traditional deployment approach for MCS, where virtual machines reference a base image and store changes in a delta disk.

In this article, I’ll cover the deployment options at a high level, including: XenDesktop 7.9 and 7.11 have introduced new features to MCS that will require additional consideration for storage requirements over previous versions. To understand sizing Machine Creation Services on Hyper-V, we should first look at how XenDesktop creates virtual machines across the various deployment choices.