After years of MCS virginity I decided it’s finally time to ditch the little farms and try out good ol’ Citrix Machine Creation Services.
So today is my very first time: After years of MCS virginity I decided it’s finally time to ditch the little farms and try out good ol’ Citrix Machine Creation Services. In the last ten years I almost exclusively installed small deployments. The big ones have about 150 concurrent user. All are build upon XenApp 6.5 or XenApp 7.6+ with static persistent virtual machines. I always told myself, that static persistent virtual machines, together with a fully automated patch management (for example: PDQ) are enough. And this is still true, because the maintenance effort is virtually not existent. But it really bugs me, that I’m not equally familiar with at least one of the provisioning methods. You might ask, why I don’t try to learn PVS instead. Well, the simple reason is that my stomach tells me not to. The more valid reason is that MCS is included in every XenApp license and doesn’t require additional infrastructure. And additional infrastructure is always a really big topic for the customer.
#PVS will die. CTPs unified in their opinion at #E2EVC. Investment will be feature porting to #MCS.
In XenApp projects you always face the challenge to decide whether to deploy a published Desktop or different published applications for the users. Many times you will have to use a combination of both. Especially in the published application use-case, you have to find a way to allow your users manage their files with a file explorer. This might not be a problem for Fat-Client users with their Windows 10 Notebooks inside the corporate LAN. Those can simply run their local file explorer and access smb shares.