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.
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
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.
On a certain batch of VDA’s we had running in an environment here they were running 2 versions back (7.11) from current version on our delivery controllers (7.13) noticed tickets coming in relating to general sluggishness with performance. Ops teams did some digging and noticed it was related to WMIprvse.exe. Seen this in the past and wondered if a similar fix adopted to same issue we’d seen in XenApp 6.5 would work.
Sure enough did the trick.
Issue related to performance counters.
On a “happy” VDA (eg one chugging along nice and quiet from a CPU perspective)
export the performance counters
c:\ lodctr.exe /S:C:\counters.txt
On the “unhappy” VDA’s import the counters in
c:\ lodctr.exe /R:C:\counters.txt
Previously known as folders in the XenApp 6.x environments or earlier. When working in medium / large scale environments generally comes a biting point when applications are better grouped into folders (like files). The simplest way to do this in XenApp 7.x is by doing the following.
– Go into Citrix Studio
– Right click on an application in Studio and select properties
– Select Delivery on the pop-up window
– You will see the application category showing under the icon. Simply create your category there. Whether it be alphabetical eg “A-E Apps” or by type “Administrative apps” and click ok when done
Tags are handy things that Citrix have introduced as of 7.x always found it much trickier finding published apps/desktops in 6.x without the tagging feature. Here’s how to set them up:
How to use tags to locate published apps
More of a “memory dump” for me this whenever see this one, few things to watch out for etc
Troubleshooting – VDA registration issues eg using XDPing etc