Scribd
Upload
2 views

MCS

Machine Creation Services (MCS) is a method for desktop image delivery that utilizes hypervisors to manage virtual machines (VMs) and creates linked clones from a master VM snapshot. MCS supports both random and static desktop types, allowing for different user experiences, while also enabling updates to the master VM for pooled-random desktops. MCS differs from Provisioning Services (PVS) in that it relies on cloning rather than streaming, making it suitable for smaller deployments and compatible with cloud services like AWS and Azure.

Uploaded by

rakesh.naidu362436
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views

MCS

Machine Creation Services (MCS) is a method for desktop image delivery that utilizes hypervisors to manage virtual machines (VMs) and creates linked clones from a master VM snapshot. MCS supports both random and static desktop types, allowing for different user experiences, while also enabling updates to the master VM for pooled-random desktops. MCS differs from Provisioning Services (PVS) in that it relies on cloning rather than streaming, making it suitable for smaller deployments and compatible with cloud services like AWS and Azure.

Uploaded by

rakesh.naidu362436
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

1. MCS is the one of the option for desktop image delivery.

It is simply uses the Hypervisor


(Xenseerver, HyperV and Vspheer) to create , start, stop and delete Vm
2. Machine Creation Services creates a snapshot of the master VM and a full copy of the snapshot,
which it places in a storage repository to serve as the master image
3. MSC use copies of Master VM (like snapshot) to provision Virtual desktops.
4. These process like a linked clone. A linked clone is a copy of a parent virtual machine and shares
virtual disks with its parent VM. The term is most often associated with VMware.
5. To update users' virtual desktops, admins can make changes to the master VM and then select
the update option in Studio. For pooled-random and pooled-static desktops, MCS creates
entirely new clones that replace the old ones the next time users boot up their desktops. MCS
cannot update dedicated desktops without erasing all user customizations
6. VM V-disk
Differencing disk
Identity disk and optionally
A personal vdisk( dedicated virtual disk that store user files, settings and other data)
7. Using the MSC we can create N number of VMs while crating machine catalog wizard
8. We can create both Desktop OS and server OS
9. Desktop Types:
A. Randam: Each time user will get different desktop at the time of login
Pooled-random desktops are nonpersistent virtual desktops assigned to users randomly
every time they start a VDI session. These desktops erase any user-specific changes each
time they reboot.

B. Static: Each time user will ger same desktop and we can configure desktop with persistence
or with persistence

Persisteance: it is like a dedicated VM user can save all data


Pooled-static desktops are assigned to a specific user who is the only person able to use that
desktop, but the user's personal data and settings do not carry over from session to session.

Without persistence : changes will not be save on desktop


Dedicated desktops are assigned to specific users and include a personal vDisk so that any
changes the users make to their desktops are saved.

Process:

1. We need one Master VM that should installed VDA


2. Create MC >> select os type >>Machine Management- PVS or MSC >> Desktop Experience –
Random or static >> Master Image selection for base image >> select N number of VMs and
set memory resource for each vm>> create machine account in ad and naming scheme## >>
machine catalog name. finish
Update master base image:

1. Power on Master VM and update required application and patches what ever we want
2. Go to studio select MC >> select update machines >> select disk image M_VM>> choose
immediate update or next login.

Notes:

A. How to know the which vm is our master VM: Get-BrokarCatolog catologname

Get-Provscheme here we can get all data.

B. For static desktop we can not update master we can do only random machines.
C. We can not update if machines in MM state.

Differences between MCS and PVS.

1. MSC takes a snapshot of master vm , copies it to a storage location and clones are made using
this copy we can called a linked clones. It not support PHYSICAL Machimes
2. PVS is a streaming technology it will boot VMS through network using V_Disk form PVS
console. It is not rely on hypervisors and could actually be used by physical machines to
stream the os
3. PVS using Streaming and MCS using cloning
4. PVS requires additional infrastructure to control and manage target devices like PVS
Environment.
5. Citrix MCS is component of Xendesktop we can control through studio management console.
6. PVS support instantanons roollbacks and fast updates.
7. MCS supports AWS and AZURE but PVS not
8. MCS NON-Persistence desktops also include differencing disks, but they belated all user
specific data in between VDI sessions.
9. MSc is Suited for small deployments
10. MSC store the snapshot fine on Hypervisor storage all VMs should be in same storage, PVS
store Vdisk in PVS storage.
11. MCS user the differencing disk and pvs use Write cache
12. Updates and writes with MSC are saves to a differencing Disk while writes with PVS save to a
write cache

You might also like