:::: MENU ::::

RES WorkspaceManager 2011 causes a delay when an application is started


RES WorkspaceManager 2011 causes a delay when an application is started

At this moment I am working on a project for a new workspace for medical personnel. The products we are using are Windows 2008 R2 with XenApp6 for the desktop, Windows 2003 with XenApp5 for legacy apps. The workspaces will be managed by RES WorkspaceManager.
After a basic install of Windows and XenApp we installed RES WorkspaceManager Agent. After this install the servers responded slowly. Explorer, control panel and all other windows explorer windows opened after about 15 seconds. For testing purpose we removed the RES Agent and immediately the problem was solved.
I decided to contact RES Support. They came with the following solution/KB article.
Problem: Installing RES Workspace Manager 2011 causes a delay when an application is started
After installing RES Workspace Manager 2011, some applications have a delay when started for the first time. For example, Windows Explorer and Internet Explorer.
Cause: The system cannot access a recent Certificate Revocation List (CRL)
Solution: Make sure the system can access a recent Certificate Revocation List (CRL) or doesn`t check for revocation
Use the following solution:
1) Make sure the system doesn`t check for revocation of certificates:
a) Disable the option “Check for publisher`s certificate revocation” in Internet Explorer => Internet Options => Advanced.
b) Change the following registry key:
Key: HKCUSoftwareMicrosoftWindowsCurrentVersionWinTrustTrust ProvidersSoftware Publishing
Value Name: State
Value Data: 0x00023e00 (hex) or 146944 (dec)
Checking certificates for revocation is default security behavior.
For more information check the “Revocation Checking” section in the following Microsoft Technet article: http://technet.microsoft.com/en-us/library/cc700843.aspx#XSLTsection126121120120
I used the solution above together with the proxy settings from the company. RES also mentioned that this problem is caused by a signed .DLL and that this behavior is by design from Microsoft.
To make a long story short. The workaround for this problem:
– Making sure that the server has internet connection
– And make sure the server is not checking for publisher`s certificate revocation


Update 9-4-2011: RES confirmed that this is a bug and will be fixed!


    • admin

      You can reach me via my blog or via e-mail N.Geursen@gmail.com. I will also add a contact form to my blog so everyone can contact me for additional information.

      Niels Geursen


Leave a comment