Citrix remoting service is used amongst other things for the SCCM connector to manage deployment and publishing of applications straight through the SCCM console. however what if you can’t get the service to start. You might get a message such as:

A timeout was reached (30000 milliseconds) while waiting for the Citrix XenApp Commands Remoting service to connect.

The Citrix XenApp Commands Remoting service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

One reason this might occur is if your XenApp servers where the remoting service is installed does not have internet access. I’ve written a few blog posts recently on performance when components do not have internet access (its not just smartphones that expect constant access these days).

When you start the demoting service it performs a CRL check which is when the server calls the internet to find a revoked SSL certificate list. Because the service cannot do this it times out and fails to start.  Luckily there is an easy win for this.

On the XenApp server with the remoting service on you need to create a new configuration file called Citrix.XenApp.Commands.Remoting.Service.exe.config in the file location C:\Program Files\Citrix\XenApp Commands

Inside the file paste the below contents and save it.

<?xml version=”1.0″ encoding=”utf-8″?>
<configuration>
<runtime>
<generatePublisherEvidence enabled=”false” />
</runtime>
</configuration>

 

This file will disable the initial CRL check when the service starts so you should find the service starts without any trouble now. There is very little effect in performing this action as the server does not internet access it is unlikely to be subject to revoked certificates being used for nefarious purposes.

 

Author: Dale Scriven

Leave a Reply

Set your Twitter account name in your settings to use the TwitterBar Section.
%d bloggers like this: