After a couple days of using Windows 8.1 I suddenly got an error when connecting with Citrix or a normal remote desktop session. Both the applications gave the error that there were no terminal server license servers available, which prevented me from connecting.
When new sessions are started, either via Microsoft RDP of Citrix ICA, they are disconnected within seconds. This applies to normal users and users with administrative privileges. This problem is caused by a chain of events. One components crash leads to an ungraceful shutdown of other components leaving a garbage configuration, preventing new connections.
On April 4th this year Citrix announced that no Synergy would be held in Europe, unlike previous years, and a new approach for the customer conference strategy was introduced: multiple regional mobility events.The article insinuated that Synergy Europe was replaced with the local conferences, starting with three mobility events (in Paris, Munich and London).
Yesterday I was troubleshooting an application that was migrated to Citrix XenApp.
The application is able to use a high precision scale which is attached to the client pc’s com port. This com port is redirected to XenApp.
While testing users reported several issues, let’s have a look at them.
Error configuring COM Port
Within the application the comport to which the scale is connected must be configured:
After pressing "Registreer" to register the new com port the following error message was shown
Configuring sites on multiple Citrix Web Interface servers can be cumbersome. It is a repetitive task that needs to be executed exactly the same on each Citrix Web Interface server. Missing one setting results in a inconsistent environment, and as we all know those situations suck to troubleshoot.
Fortunately Citrix came up with a solution: shared configurations. With shared configuration slave servers use the configuration of a master server, all the changes needs to applied once on the master servers and the slave servers inherit the same configuration.
If you start the tool without parameters you will get the GUI, just like before:
To use the COM interface you first need to register the executable with the /regserver switch:
After the registration you can call it using any language that supports COM. To get you started I wrote a few examples
This application reads data from an external device called SECUTEST.
The device is connected to a COM port which is redirected to the XenApp session. In contrast to Microsoft Remote Desktop Services COM ports are not automatically redirected in XenApp but need to be mapped via eg a logonscript (NET USE COM1: \\Client\COM1🙂 or using UEM.
In my case the COM port was mapped with RES Workspace Manager:
Author: Ingmar Verheij
With the release of Citrix XenServer 5.6 Citrix also released a new virtual appliance dedicated to licensing, the License Server VPX. The appliance is available since July 2010, in the 2.5 years the appliance is available only Citrix XenServer is supported.
If you’re company is using VMware vSphere (or Microsoft Hyper-V) you’re unable to use the virtual appliance. Citrix refuses to release an appliance for other hypervisors then their own, let alone supporting other hypervisors. Technically it shouldn’t be too difficult to support other hypervisors (some people tried), they already do for the NetScaler VPX.