Monday, December 19, 2011

Citrix XenApp 6 Policies not applying

If you have read some of my other posts recently you will know that I am in the process of designing and building a new Citrix environment to replace my companies old PS4 desktop setup.
Recently we found that Citrix Policies were not applying on a consistent basis.  What normally occurs is that a key is created HKLM\software\policies\.  This contains all of the policies which are relevant to your particular session.

During our testing we found that this key was not being written when logging on, which meant users had access to everything they wanted including client drives from home!

The problem was even harder to diagnose though, we saw that when Group Policy was updated automatically every 90 minutes during a session, the was written with the correct settings.  This meant nothing as the shell had already been setup and these settings would not apply.

As these keys are not deleted on logoff, when new users logged in they would inherit the settings of another user. 

Now hopefully that makes sense!!!!!!!!


We repaired the Citrix Group Policy CSE on the servers and Visual Studio installation as recommended here.

We tried running the above account under a domain admin account
We tried moving the group policies into the Citrix IMA datastore.

None of the above things worked.


One of our legacy applications must be installed in "c:\program files" if you try to install it by default it will fail.  To achieve this you must change the following registry key

"ProgramFilesDir"="C:\\Program Files"

This defaults installations in "c:\program files"

What we found is that when this registry was not set back to "c:\\program files (x86)" and you use the Citrix imaging and provisioning tool, policies would not work.

(more details of provisioning here

So to fix, make sure you set the registry back to the following after all of the application installs

"ProgramFilesDir"="C:\\Program Files (x86)"

It is an odd one!  but maybe I might save 1 person a lot of time!!!


Tuesday, November 29, 2011

Memory error when trying to print pictures

As mentioned in my previous blogs, I am building a XenApp 6 environment for my organisations to replace the current PS4 farm. I am fixing all of the little niggles at the moment and I came across a really annoying issue.

Windows 2008 R2 Standard
VMware vSphere 4.1
6GB Ram
XenApp 6.0

When right clicking an image and selecting Print from the context menu, a number of error messages appearing saying
Your pictures can't be printed because this error occurred:
There isn't enough available memory to print your pictures. Close some open programs, and then try again.
Now, troubleshooting was a little difficult but this is the approach I took
Memory - 6GB for 2 issues showing in task manager etc.
Permissions - occurs for all users, even local administrators
Applications - uninstalled all other applications from server, problem still occurred
Process Monitor - Took a log during a repro but couldn't see any obvious faults occuring.
Print Drivers - removed all print drivers, problem still occurs
Searched Internet - nothing other than idiots stating that you need more RAM..........if only it were that simple!!!


Now at this point I was a little stumped, and I remebered the system file checker utility.

I wondered if a system file or registry key had become corrupt so a scan would not do any harm
open command prompt and type (make sure you run as administrator)

sfc /scannow

reboot and try printing the image again, the fault does not occur.

I hope this saves you a few minutes, it would of done in my situation!!!


Monday, November 28, 2011

XenApp 6 duplicate server name error

I am currently designing and building a XenApp 6 farm upgrade for my organisation. They are moving from Citrix Presentation Server 4 to XenApp 6 in the new year.

Whilst designing the administration console for support staff I came across the following issue.


When specifying more than one server in the discovery list for custom administrators and error message appears with the following text.

"another discovered farm has the same name as the farm to which this server belongs. Connecting to different farms with the same name is not supported"

Now, these servers are both in the same farm, but for some reason using a custom administrator it does not work.



After looking through the custom permissions provided to these administrators I found that adding the following permission fixed the problem.

"View Server Information"

Make sure when applying this setting you click the button "copy to subfolders"

Once this has permission has been granted, subsequent discovery attempts will work correctly without errors.

Thursday, September 22, 2011

Citrix Online Plugin 13

Citrix have recently released Citrix Online Plugin 13.1 on their website. This is only available as part of Citrix Receiver 3.2 here.

This makes it difficult to have the same experience which many are used to with older versions of the client especially in the enterprise arena with Program Neighborhood Agent.

To install the plugin in the same way as before you can use the following installation string.

CitrixReceiverEnterprise.exe ADDLOCAL="ICA_Client,SSON,USB,DesktopViewer,Flash,PN_Agent,Vd3d" ENABLE_SSON="Yes"

Below are all of the installation string options. You need to remove the option "ReceiverInside" section

CitrixReceiverEnterprise.exe /silent ADDLOCAL="ReceiverInside,ICA_Client,SSON
,USB,DesktopViewer,Flash,PN_Agent,Vd3d" SERVER_LOCATION="my.server" ENABLE_SSON=
errided_name" DEFAULT_NDSCONTEXT="Context1,Context2"

And if you want Citrix Online Plugin 14 the process is similar with 3.3 onwards
As PNA has been removed from Receiver 3.3, go check out this link

Otherwise do the same install for Online Plugin 14