Category: Citrix

Trouble getting rid of them really old citrix receiver versions (6.x / 7.x)?

Came across an issue removing some really old citrix clients (version 7.x) in a locked-down environment that was running (ahem) windows vista machines. Had issues upgrading the receivers on the machines.

As these machines had ICA clients using a version that was packaged using installshield they used an EXE file. The method to remove these files was somewhat different than the later MSI method. To remove successfully:

isuninst –f C:\PROGRA~1\Citrix\ICACLI~1\Uninst.isu –c C:\PROGRA~1\Citrix\ICACLI~1\uninstpn.dll –a.

 

Troubleshooting HTML5 receiver issues

Recently in the lab updated the HTML5 receiver (version 2.3) on my storefront servers. After which hit issues with my connection going “in and out”.

Turns out my patching wasn’t up to scratch. XenApp 6.5 environment and moving hotfix rollup pack 7 (per CTX129229) resolved the issue.

What was instructive was enabling HTML5 logging per https://support.citrix.com/article/CTX217352

What did help me gather from it was it was session reliability-related. Sure enough when I switched it off all worked. Ultimately though did want to leave enabled so updating to latest HRP resolved but the HTML5 logging was very useful on this occasion as reasonably negligible so a good takeway

 

Citrix PVS tip: how to install PVS powershell snap-in

Recently was looking to utilize the vDisk replicator utility (see: https://www.citrix.com/blogs/2017/04/12/vdisk-replicator-tool/) which had a requirement for the PVS powershell snap-in. After a few times did manage to get the snap-in to work but have to be careful to get the syntax correct which was in the end:

C:\Program Files\Citrix\Provisioning Services Console>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installutil.exe Citrix.PVS.SnapIn.dll

After that was up and running with my replicator

 

 

 

Getting “Aw, Snap!” on launch of google chrome in citrix environments?

See plenty of pain on this one in the field. Not quite sure what is going on with chrome as seen as same from my own machine.

Anyways in order to circumvent message below which is what greets you launch simply need to do the following:

C:\Program Files (x86)\Google\Chrome\Application\chrome.exe” –no-sandbox –disable-infobars –disable-gpu

 Editing the shortcut is the simple method. Use shift+right click to edit the one on the taskbar. Sure there is noise in the forums on this but been busy to check what root cause is/ultimate fix but above should get you over the hump for now.

 

 

PVS write cache filling up? handy filter in Procmon to give a clue as to what’s causing it

So of course with write cache filling up issues no simple way to tell what’s going on. Needless to say like most quirks that happen in Windows the sysinternals tools can come to you rescue.

Recently started work on a windows 10 PVS image and after about 10 minutes the write cache would fill up.

So using Procmon (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx) was able to determine what was going on.

In order though to filter out the extraneous stuff found the following 2 filters gave me info on the offenders.

To do click Filter and filter out everything except write activity by making two filters as follows:

Operation begins with WriteFile Include
Operation begins with WriteConfig Include

and you’ll be on our way.