Sep 232011


previous post remembered me another annoying thing I’ve faced off. XenApp 6 Citrix Delivery Console let you set reboot policy settings (time, warning messages, frequency, and so on).
For me it was not working. I’ve check the rules several times, checked the registry keys and figured that everything was fine but… always not working.

In fact you must have at least an Enterprise Edition to make it work. It’s not even mentioned in the latest Citrix XenApp Comparative Feature Matrix.

Thanks to everyone in this post for pointing it out:

Citrix Support Forum

Sep 232011


I’m designing for a customer his new Citrix XenApp 6 farm.
I was wondering why the user’s explorer view was not saved when the user reconnects between servers.
Unfortunately for me, it was the first time I did not use a profile manager under Windows 2008 for managing profiles (Citrix Profile Manager, Appsense, Tricerat and so on). After searching on internet, I discovered that it was something introduced by Microsoft since Windows Vista (It concerns only roaming profiles).

Citrix Profile management is a feature available for XenApp Enterprise and Platinum editions and XenDesktop Advanced, Enterprise and Platinum editions and guess what we use the XenApp advanced edition 🙂

So if you are facing this problem and you care about your explorer view settings under Terminal Server or Citrix then use at least the Enterprise edition for Citrix or use a dedicated software.

Dec 072010


Here is a an NRPE script which will monitor your Citrix Licence server. The script is based on article CTX112594 which is quite old now (Oct. 2007).

If someone have a newer reference file, please post a comment and I’ll try to update my script.

I use “lmstat -a” command and then parse the result. Normaly, this command should work on your server. When you try it on your server and if you receive an error please check this post:
Continue reading »

Apr 232010


Recently trying to package silent install of “Evolan Report” product. I faced with this error:

I googled a lot and found many posts complaining that it’s a Terminal Server issue but without solution.

Finally using the following command line before the setup arrange everything:

change user /install

After you finish your setup, just switch back to execution mode:

change user /execute