I mean that if you are using a newer SG version and an older client, you will get SSL errors on the SG server because the version of sslsdk_b.dll mismatch. It’s always a good practice to match your client with your SG version. Hi Nice Article! I have to slightly disagree with you on that one.ġ1.2 is really old and has many issues as well. These will only steal unnessecarry memory from your system. While you’re at it, make sure you delete any references in Run to Acrobat Assistant 8.0, Adobe Acrobat Speed Lanucher, Adobe ARM, BCSSync and so on. For 圆2 this is located in HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Run.For x32 this is located in HKLM\Software\Microsoft\Windows\CurrentVersion\Run.If your users are constantly getting a MSI repair when they visit a Citrix Web Interface site this is most due to the missing ConnectionCenter entry in Registry. Simply push this registry value through Microsoft Group Policy Preferences. So keep safe and stick to the working Citrix ICA Client 11.2 and save some memory at the same time. The workaround for XenApp 6 is to copy the wshadow.exe from the XenApp 6.5 media, but on XenApp 5 there’s currently no hotfix available.
There’s currently also a bug with Citrix Receiver for Windows 3.0 and the Shadow Taskbar.
Register the Citrix Receiver with web browser : Normally the Citrix client is installed on XenApp servers only to allow for ICA in ICA to internal back-end or Cloud hosted applications. So when optimizing you Citrix servers for the highest user density you should consider if you even need some of these new features if any. The newest Citrix Receiver for Windows 3.0 (13.) requires almost 150% more memory per user than Citrix ICA Client 11.2.
0 kommentar(er)
