Web Interface With RSA SecureID - Addtional Config

There are a couple of things to do to a web interface on version 5.4 to get it to work with the RSA SecureID Agent version 7 on a Windows 2008 R2 server.

After installing the relevant components and successfully performing a Test using the RSA Security Center on the web interface server you need to

• Add "C:\Program Files\Common Files\RSA Shared" to the PATH environment variable (or wherever you can find aceclnt.dll
• Copy the sdconf.rec and securid file from "C:\Program Files\Common Files\RSA Shared\Auth Data" to "C:\windows\system32"
• Alter the CitrixWebInterface5.4.0AppPool in IIS Manager to not allow 32 bit apps.

Web Interface Configuration

If there is a delay when the web interface first loads this is the fix.

This issue is caused by a CRL check sent to Verisign. If the Web Interface server cannot access the internet, the CRL check fails and times out.

Check in IIS for the ASP.net version that is in use with the Web Interface site.
Modify Aspnet.config  in the following directory
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 (If Web Interface uses .Net framework v2.0.50727)
Add the following lines to your ASPNET.CONFIG or APP.CONFIG file:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <runtime>
        <generatePublisherEvidence enabled="false"/>
    </runtime>
</configuration>

Taken from  http://support.citrix.com/article/CTX117273

Clearing the app V cache

1. Logon to the Citrix Server with a user account that has administrative rights.
2. Launch the Registry Editor.
3. Reset the following registry DWORD value to 0:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\AppFS\State
4. Reboot the Server.

Applications Crashing

A couple of links to reasons why some apps may be crashing when you publish them from a 2008 R2 server

http://support.microsoft.com/kb/2498855

http://support.microsoft.com/kb/2279689

http://blogs.msdn.com/b/anandgeorge/archive/2010/03/29/some-multi-thread-terminal-server-applications-crashes-in-win-2008-r2.aspx

WMI Corruption

Having SCCM on the Citrix servers WMI corruption seems to occur quite frequently. I will look into hotfixes for this later. In the mean time i've noticed that if WMI corruption does occur, here are the steps I used to get it back.

1. Disable and stop the WMI service.

     sc config winmgmt start= disabled

     net stop winmgmt

 2. Run the following commands.

    Winmgmt /salvagerepository %windir%\System32\wbem    
     Winmgmt /resetrepository %windir%\System32\wbem

 3. Re-enable the WMI service and then reboot the server to see how it goes.

     sc config winmgmt start= auto

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/8ed26d46-9994-4052-a307-5b071805aea8/

And then

Cd “C:\Program Files (x86)\Citrix\system32\Citrix\WMI”

for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

WMI

Had a couple of issues with a server. One being the App-V client wouldn't start properly (failed to initialize) and another the Xenapp Power and Capacity management wasn't working properly. It turned out that WMI had become corrupt. Here's a post on how to recover from it.

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/8ed26d46-9994-4052-a307-5b071805aea8/

Office Updates

According to http://technet.microsoft.com/en-us/library/cc754288%28WS.10%29.aspx installation of msi's does not require the terminal server to be in install mode. So this should mean that I can deploy the Office 2010 updates that my boss wants me to using the "Software Updates" section of the SCCM 2007 console.