understanding Citrix XenApp VDA through MCS
Posted on 2014-11-26
I am in the process of migrating to Windows 2012 with Citrix Xen App 7.5. I am new to this environment, but getting a hang of it. I wanted to to just confirm some things of how it works.
I have setup a server running the Citrix Delivery Controller service and then another server with the Citrix VDA service. After I set up this server with all the settings and applications, I used the Citrix Studio console on the Delivery Controller to create 2 new servers using the MCS from the Base server that was created with my settings and apps.
Originally I had understood that once the new VM's get created they work on their own until you make a change to the base and update the catalog. However, I made a change to a text file in one of the program folders in Program Files. The software vendor needed this change and I figured that it was faster to make the change to these 2 servers than making it in the master and doing an update. However, when I rebooted the VDA VM and it started up again the text file reverted back. I did several tests with adding and deleting files and it seems like when the server is rebooted, it loads up the last updated catalog image as opposed to what was currently on before the reboot.
Is this the normal intention of the VDA catalog concept. My concern with this is that while the user profiles will be saved offline to a UPM store, there are often programs that will modify files and settings in their working directories which may be slightly different in each server and for sure from the base. When the base gets updated and overwrites these changes, not sure how the programs would react to that.