The first Desktop Director user to log on, after IIS restarts, experiences a delay of over one to two minutes before the initial Desktop Director web page loads.

You can disable signature verification to prevent the loading delays by completing the following tasks:

1. Check IIS for the ASP.net version that is in use with the Desktop Director site.

2. Open Aspnet.config for editing in the following directory:
   C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727 

   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

3. Add the following lines to your Aspnet.config file:
   <?xml version="1.0" encoding="utf-8"?>
   <configuration>
       <runtime>
           <generatePublisherEvidence enabled="false"/>
       </runtime>
   </configuration>

Problem Cause

This issue is caused by a CRL check sent to Verisign.

CTX117273 – Web Interface 5.x Delay on First Page

Best Practice - <GeneratePublisherEvidence> in ASPNET.CONFIG

FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start