A customer wanted to publish an internal hosted IIS 7.0 website to the outside world through a Netscaler 10.5. I configured the server, services and Virtual Server objects in the Netscaler interface.
So far so good. The IIS server still had to be configured with the website, so till that time the default website showed with no problems. Untill the the supplier of the website installed the website. From that moment on the services object state on the Netscaler went down.
Although there are a number of methods and tools to maintain print-driver replication amongst Xenapp servers, the main objective is to keep your drivers in sync with your print-server. Setting up a Xenapp farm means that users don’t have the right to add print-drivers. And so even when the most piddling DLL deviates from your print server your users are presented with malignant looking windows demanding all sorts of admin stuff. Can your hear the phone ringing at the service desk…?
Read moreA client, running a Windows 2008 R2 RDS/Citrix Xenapp 6.5 environment managed with RES Workspace Manager 2011 SR5, faced an issue with Outlook 2010 signature which disappeared with each new logon. Only a specific group of users was affected by this. Others had no problems at all. Read more
A client experienced Intermittent High CPU and Increased Disk I/O with SPOOLSV.EXE When Mapping TS User Session Printers on Windows Server 2008 R2 (Provisioned on Citrix Xenserver 6.0.2). A large amount of printers where mapped for each new user session. During the most logon extensive period in the morning the whole environment came to a grinding halt. After thorough investigation we noticed that with each client session starting heavy disk I/O was noticeable in the %system32%\spool\driver\3 folder. One could see the creation of a {GUID}-folder for each printer created during a session logon. The folder disappeared straightaway after the printer was mapped. Read more
Citrix HDX Mediastream Blacklisting
There are certain situations in which HDX MediaStream for Flash fails for certain Website URLs. This happens as a result of certain web pages that have been designed to work in a way that is not compatible with the HDX architecture. These failures cannot be detected, so HDX has been designed to create and use a Dynamic Blacklist to remember Websites that provoke these failures. In these situations, the HDX feature falls back to server-side Flash rendering for the current browser tab that provoked the failure. Additionally, it uses server-side rendering for all future browser tabs that navigate to the failing URL Website.
Read more