![]() ![]() Generally speaking, this is a very reliable and trouble-free process, requiring only that the Citrix Virtual Apps & Desktops (CVAD) site have a properly configured so-called “hosting connection” to the target hypervisor cluster (including sufficiently permissioned credentials) and that the user account running the machine catalog creation wizard in Citrix Studio have sufficient permissions to create machine accounts in the selected AD OU, both of which were the case here.Īfter going through the steps to create a new machine catalog, specifying the MCS option and selecting a fresh snapshot of the (now powered off) source VM, the number of desired machines, their naming convention, and target OU, I saw the MCS process start as always with its first step, “Copying the master image”, and its progress bar quickly get to about halfway, … then appear to stop. ![]() On a recent occasion at a client, after building and customizing a Windows Server 2016 RDS image (on VMware ESXi, not that this particularly matters here) and installing the Citrix Virtual Desktop Agent (VDA) for Server OS with a view toward deploying it via Machine Creation Services (MCS), came time to actually perform the MCS deployment. Here is another great write-up by Jacques Bensimon. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |