There are many post around to tune Citrix XenApp in many ways and there are even more to tune Microsoft Windows 2008 R2. I want to begin a new document as we had with Citrix Metaframe 1.8 tuning tips on Microsoft Windows NT4 TSE. This was a great document and very helpfull in many way. If you have any ideas, agree on what I will write or disagree, I take everything to form a big document available online for everyone. First I would like to know if we should create a wiki-like to let everyone working on the document and add/change at will, what do you think ? If you choose other please add a comment bellow !

XenApp 4.5 / 5 unattended installation 4 Comments

Unattended installation is very usefull in large XenApp farm, of course if you're deploying one server per two month you might not be interessed by this process automation but this is always interresting to know this kind of tips. Scripts bellow are example I use every day in production to install servers, of course its needs to be change and adapt to your own settings and of course if you have some ideas to share, I take it ! This unattended example assume you have only one network card enable, a local XenApp source installation file and IP address type 192.168.3 / 192.168.10 / 192.168.200 / 10.113 / 10.112. This file allow to join an existing farm named CTX_TEST with a datastore hosted on a SQL server. Finally, you need to create one folder per farm inside your XenApp source folder if you are automating multi farm setup. This is the UnattendedTemplate.txt you can find on your XenApp installation media, this file is very simple to fill and everything is comment and explain. This file example is for the XenApp zone named ZoneA I wanted to comment every option bellow but I think existing comments are very clear and you will understand everything. If you have any question, just ask on the forum. And if you want to go further, you can create one file per zone and use a script to deploy your XenApp server to the right zone while checking the machine IP address. This script needs XenApp installation files locally on your server (c:\Citrix\XenApp5). This unatended installation generate a verbose log file on c:\XENAPPCTX_PROD.log , don't under estimate this part, it can be very usefull to troubleshoot your silent installation. One last thing before you go, don't forget to use a valid MF20.dsn :