Primer 1. Primer 2. MCS Prep overview (good post, I don’t refer to all its points below).
- MCS creates a snapshot of the master VM you specify, but if you specify a snapshot it will not create another one.
- This snapshot is used to create to create a full clone. A full snapshot, so to say.
- This way the image used by the catalog is independent of the master VM.
- During the preparation of this full snapshot an “instruction disk” is attached to the VM that is temporarily created using the full snapshot. This disk enables DHCP on all interfaces of the full snapshot; does some KMS related tasks; and runs vDisk inventory collection if required.
- This full snapshot is stored on each storage repository that is used by Desktop Studio.
- This full snapshot is shared by all VMs on that storage repository.
- Each storage repository will also have an identity disk (16 MB) per VM.
- Each storage repository will also have a delta/ difference disk per VM.
- This is thin provisioned if the storage supports it.
- Can increase up to the maximum size of the VM.
Remember my previous post on the types:
- Random.
- Delta disk is deleted during reboot.
- Static + Save changes.
- Changes are saved to a vDisk.
- Delta disk not used?
- Static + Dedicated VM.
- Delta disk is not deleted during reboot.
- Important to keep in mind: if the master image in the catalog is updated, existing VMs do not automatically start using it upon next reboot. Only newly created dedicated VMs use the new image.
- The delta disk is deleted when the master image is updated and existing VMs are made to use the new image (basically, new VMs are created and the delta disk starts from scratch; user customizations are lost).
- Better to use desktop management tools (of the OS) to keep dedicated VMs up to date coz of the above issue.
- Static + Discard changes.
- Delta disk is deleted during reboot.
A post on sealing the vDisk after changes. Didn’t realize there’s so many steps to be done.