Citrix Clipboard issues in a published desktop environment

It amazes me in this day and age that something as fundamentally simple as the clipboard in a windows environment can have issues, but it does happen… Especially in a multi user environment.

If you experience clipboard issues with office, Lotus notes and other copy and paste capable programs you have have a session memory issue!

The session View size and pool size have a massive part to play in 32 bit citrix environments, these size options dictate the amount of graphical memory that can be assigned to each session. The ceiling for these options in 32 bit are just 16mb, which rediculously low in modern days.

Taking equal parts of graphically heavy applications like Office 2007 and Known citrix killers like lotus notes, it really isn’t long until these limits spill over into horrible clipboard and copy / paste disasters. Take one step further and implement Microsoft App-V and you are in serious trouble.

If alike me, you run an environment that requires all the above nasties, help is at hand. After 12 months of continued troubleshooting I’ve found a happy medium of 64mb between low limits and too high limits.

To test the same, simply bash these off the following command lines and reboot, waving goodbye to your horrible clipboard issues:

reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management” /v SessionPoolSize /t reg_dword /d 64 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management” /v SessionViewSize /t reg_dword /d 64 /f

Disclaimer:

We currently run with 10gb of memory, allowing us to allocate this extra 112mb of memory per user. If you require these options, consider a lower value or upgrade your ram capacity

App-V applications hang for 30 seconds on a CMD box before opening

In our powerfuse environment we came accross this problem recently.

When we would try to launch an App-V application the following window would open and remain open for 30 + seconds before finally opening the application:

The problem we discovered was to do with file type associations inside of the RES session, App-V by default will try to associate it’s file type associations for the application being sequenced and store them in the .osd file. The problem was that PowerFuse also controls file associations and this became an issue! PowerFuse has to be associated with the app and not vice versa.

I recommend you specify the file type associations inside of powerfuse and remove the associations inside of the App-V package. To remove the associations, open the .osd file and remove anything between the <FILEEXTENSIONLIST>  </FILEEXTENSION>:

After the link is an example.