Perhaps you’ve seen the KB articles for solving a delay on first launch for Web Interface http://support.citrix.com/article/CTX117273 or Desktop Director http://support.citrix.com/article/CTX130580…well I’m here to tell you that these changes apply to Citrix Receiver Storefront too. While there isn’t yet a KB article for this on Storefront these issues occur across many of the Citrix product lines as they all use signed code. When this signed code starts up the certificates that were used to sign it are checked against a certificate authority. More information about this process is here http://blogs.msdn.com/b/pfedev/archive/2008/11/26/best-practice-generatepublisherevidence-in-aspnet-config.aspx.
If security is of the highest importance and you want/need to ensure that the code that is executing on your server is indeed the code Citrix created and not some rogue dll then you should leave things as they are and instead try to lengthen the worker process timeout value so they don’t shut down so quickly when there isn’t any activity and/or use health monitors from Citrix Netscaler to keep the site “warmed up”.
If speed and user experience is more important you’ll want to make these changes below to speed up the first connection to the Citrix Receiver Storefront site.
For quick reference here, the change you’ll need to make in order to speed up first login/connection to Citrix Receiver Storefront is:
- Check IIS for the ASP.net version that is in use with the Receiver Storefront site.
- Open Aspnet.config for editing in the following directory:
- Note: The ASPNET.CONFIG file is located in Framework Directory for the version of the Framework you are using. For example, for a 64-bit ASP.NET application it is: c:\Windows\Microsoft.NET\Framework64\v2.0.50727
- For a 32-bit application it is: c:\Windows\Microsoft.NET\Framework\v2.0.50727
- Add the following lines to your Aspnet.config file:
<?xml version=”1.0″ encoding=”utf-8″?>