PVS vs MCS – Part 7: Summary


As Q said in the final episode of Star Trek: The Next Generation, “All good things must come to an end” and after 6 previous blogs focusing on deciding between Provisioning Services and Machine Creation Services, it is time to end.

As I explained, over the past 5 years, improvements were made to Provisioning Services and Machine Creation Services.  While Provisioning Services simplified deployment and maintenance, Machine Creation Services improved performance and delivery capabilities.

Five years ago, if someone had to decide between the two, most likely the answer would be Provisioning Services.  But now in 2016, because of the overall improvements in both solutions, the decision will mostly focus on a few core concepts explained in the previous blogs:

Five years ago, I created a decision tree helping you select the most appropriate solution.  Developing these previous six blogs helped me do the same thing based on the latest advancements.

CompareDid I miss any criteria?  Let me know

Daniel (Follow on Twitter @djfeller)
XenApp Advanced Concept Guide
XenApp Best Practices
XenApp Videos

 

 

Advertisements

4 thoughts on “PVS vs MCS – Part 7: Summary”

    1. It is correct. The read cache is done at the hypervisor level, that XenServer provides. The RAM based write cache is built within the actual VM, so it works across any hypervisor. It is just using non-paged pooled memory within the Windows OS.

      Like

  1. I get visits by a lot of vendors and go to seminars and done MCS and PVS deployments. I will pick PVS most of the time for ease of troubleshooting and agility. I can dump the image to a new datacenter and quickly have hundreds of devices provisioned successfully without a lot of headache. PVS server allows me to optimize workloads centrally. With MCS you have more chances another less experienced IT person messes up. Which is why it’s good to have 2 consoles to do things. This is all opinion. MCS works pretty well in well managed shop that’s not looking to failover frequently.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s