Terminal Services - Frequently Asked Citrix Questions!

[12] Frequently Asked Asp Questions!
Updated: Jun 07, 2000
[188] Frequently Asked Citrix Questions!
Updated: Oct 10, 2006
[3] Frequently Asked Sco Tarentella Questions!
Updated: Aug 16, 2002
[260] Frequently Asked Windows Terminal Services Questions!
Updated: Aug 03, 2006
1 2 [3] 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Help! When I installed the Microsoft Patch for the Sasser worm it killed my Terminal Services Licensing Server. What can I do? 

Open regedt32.exe to remove the following 3 values to get your server connecting again to your license server.
To fix navigate to:
Hkey Local Machine/System/Current Control Set/Services/TermService/Parameters
Delete the following entries:
- Certificate
- X509 Certificate
- X509 Certificate ID>
Once you do this, reboot your server and it should take care of this particular issue.

How do I disable the Citrix Management Console splash screen?  

CTX101937 - How to disable the Citrix Management Console splash screen

This document was published at: http://knowledgebase.citrix.com/kb/entry.jspa?externalID=CTX101937

Document ID: CTX101937, Created on: Jun 3, 2003, Updated: Jul 9, 2003

Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000
 
There are two ways to disable the Citrix Management Console splash
screen:

• Add -nologo to the Ctxload.exe command line. For example, if you
publish ctxload as a published application, edit the published
application and add -nologo to the end of the command line.

• If you run the Citrix Management Console from the toolbar, open the
Program Files\Citrix\Administration folder. Create a shortcut to
ctxload. Open the properties of that shortcut and add -nologo to the
end of the target box. Click OK. Add the shortcut to the toolbar.

Note: These instructions work only with MetaFrame XP Service Pack 3
or later. Following these instructions with earlier versions causes
the Citrix Management Console to fail.

I`m trying to deploy PNAgent and I`m running into a strange issue. PNAgent loads and populates the Start Menu the way I want it to, but when I try to run a published app, I get the following message: Unable to launch applications. The remote server may be down, the launch.asp file may be invalid, or the launch.asp file contains errors. 

You may get this problem when you "lock" down the settings via the http://nfuse/citrix/pnagentadmin site. Specifically, if you checked the "Hide the Session Options tab from users" under Client Tab control, then you may get this message.

How do I allow a user to reset their own Terminal Server or Citrix ICA Session? 

Thanks to Ken Lutz for his compilation and leg work on this one:

I got this working.  If anyone is interested here is the solution that I came up with.

1) set the HKLM\System\CurrentControlSet\Control\Citrix
        IcaEnableKeepAlive  - Reg_Dword to 1
        ICAKeepAliveInterval - Reg_Dword to 1800 (30 minutes)  (I have my disconnected user reset
time set to 60 minutes)
This setting means that a users session will get reset after just over 1.5 hours, if they do nothing.

2) I got a copy of the FINDUSER.exe utility from this web site:  http://www.wizbang.org.uk 
(it`s part of the Command line tools download).

3) I also had to get the choice.exe utility from the NT Resource kit.

4) I then published this script:

<~~~~ Start of Script - watch for word wrap ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>
@Echo off
cls
@ECHO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@ECHO ~ Use this procedure to reset all your active Citrix sessions.         ~
@ECHO ~                                                                      ~
@echo ~ By resetting active Citrix sessions you may risk the lose of data!!  ~
@echo ~                                                                      ~
@echo ~ Are you sure you want to reset your active Citrix sessions?          ~
@Echo ~ Respond with Y for yes and N for no (upper case Y or N only).        ~
@echo ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Choice /C:YN /S Proceed with Citrix session reset?
If errorlevel 2 goto :END1                                         

   if exist H:\resetlist.txt del H:\resetlist.txt

   %WINDIR%\FindUser.exe %UserName% /server:%WINDIR%\serverlist.txt >H:\ResetList.txt

   for /f "skip=5 tokens=1,4" %%I in (H:\ResetList.txt) do   (set rserver=%%I& set rsess=%%J& call :DOIT)

goto :END2


:DOIT
    @ECHO %SESSIONNAME% %RSESS%
    IF RSESS == %SESSIONNAME% GOTO :EOF
    @ECHO RESET SESSION %RSESS% /SERVER:%RSERVER%
    RESET SESSION %RSESS% /SERVER:%RSERVER%
 
goto :EOF
 
 :END1
@ECHO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@ECHO ~ You chose NOT to reset any Citrix sessions at this time.             ~
@ECHO ~ No Citrix sessions have been reset!                                  ~
@ECHO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
pause


:END2
@ECHO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@ECHO ~                                                                      ~
@echo ~ Please wait until you get the "Saving your settings" message before  ~
@echo ~ you open any other Citrix session.  (Don`t click on another NFuse    ~
@echo ~ icon until after you see the "Saving your settings" message.)        ~
@ECHO ~                                                                      ~
@echo ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
pause
<~~~~~~~~~~~~~~~~~~~End of Script~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~>

The only thing with this is that it will not reset the session if it is already disconnected. 
It will only reset active sessions.  It will not reset the session that is running the script
(the current active session).

The reason I had to write this is because I have some users that would loose their connection to Citrix
(via NFuse and published applications) yet leave their sessions active to Citrix. 
The only way I could recreate this is to reboot the PC while the Citrix session is active.

How do I install Office 2003 on Windows Terminal Services? 
See the Microsoft Page:
http://www.microsoft.com/office/ork/2003/two/ch5/DepD06.htm
Which States:
Unlike with previous versions of Microsoft® Office, installing Microsoft Office 2003 to a Terminal Services–enabled computer is not much different than installing Office to a non-Terminal Services–enabled computer. Before installing Office in this environment, however, the administrator needs to perform some tasks relating to how Terminal Services was installed. Installing Office 2003 on a Terminal Services–enabled computer Before you install Office to a computer that is enabled with Terminal Services, it is very important that you check to make sure that specific operating modes of Terminal Services were enabled when Terminal Services Setup was run, including the following: The installation of Terminal Services must have been installed to use Application Server mode. Terminal Services must be enabled and running on the server before installation of Office 2003 begins. For Microsoft Windows® 2000 servers, Windows 2000 compatibility mode should be selected to retain a locked-down installation. Once you have checked for these modes, you are ready to install Office 2003. To install Office 2003 on a Terminal Services–enabled server Open Control Panel. Run the Add/Remove Programs utility. Click Add New Programs (left-hand pane). Click CD or Floppy. Insert the Office 2003 CD into the CD-ROM drive, and then click Next. If needed, browse for the Office 2003 Setup program (Setup.exe) and select it, then click OK. – or – If you are installing from an administrative installation point, browse to that location, select setup.exe, and then click OK. In the resulting Run Installation Programs dialog, add any command-line customizations you require (unless already specified in the Setup settings file (Setup.ini) stored in the administrative installation point). Click Finish. Customizing Office 2003 for a Terminal Services installation Customizing Office 2003 for a Terminal Services–enabled installation is possible, but you need to first understand the differences between how Office runs with a Terminal Services–enabled operating system versus one that is not enabled as such. By default, almost all features in Office 2003 are enabled and installed as part of the installation. This helps reduce the number of subsequent application or feature installations an administrator might need to perform for users. Because Office, by default, is installed in a locked-down configuration, users cannot perform installations (like adding a feature), because they cannot write to the registry or application and system folders. Therefore, it is recommended to install all the applications and available features to minimize the need for further installations by the administrator. As part of an installation to a Terminal Services–enabled system, some specific features are disabled by default because of their high bandwidth requirements for network and dial-up users. For instance, animations, sounds, and high-resolution graphics are disabled; or, in the case of high-resolution graphics, substituted with lower-resolution graphics. To determine which settings are enabled or disabled, you can attempt to install Office to a properly configured Terminal Services–enabled server and examine the feature installation options during the installation. This will give you a baseline of what features are installed. Then, if you need to install many Terminal Services–enabled systems, you can create a transform using the Custom Installation Wizard and set the appropriate settings you want to use.
--------------------------------------------------------------------------------
Note Any features you set to Install on Demand will be ignored and installed as Run from My Computer. Also, by default, installations to Terminal Services–enabled systems will always install the low-resolution graphics for splash screens.
--------------------------------------------------------------------------------
Though you can create a transform for use with deployment of Office 2003, the majority of settings configured for installation are by default optimized for a Terminal Services-enabled system. Also, since most installations of this type are performed in a server farm or within a controlled environment, the creation and use of transforms is not as necessary as with distributed-client system scenarios. When creating transforms for use with Terminal Services-enabled systems, it is highly recommended that you not enable features that are disabled or set to Not Available. If you expect to deploy Office 2003 to more than two or three Terminal Services-enabled systems, creating a transform is worthwhile, especially if there are several customizations. See the Customizing Office 2003 section for more information about creating transforms for use with Office. The Below comes from Microsoft Knowledge base at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;828955

How to Install Office 2003 on a Computer That Is Running Windows Terminal Server

View products that this article applies to.

SUMMARY

This step-by-step article describes how to install Microsoft Office 2003 on either of the following computers:
  • Microsoft Windows Server 2003-based computer with Terminal Services enabled.
  • Microsoft Windows 2000 Server-based computer with Terminal Services enabled.
Before you install Office 2003 to the Windows 2000 or Windows Server 2003 Terminal Services computer, the computer must be configured as follows:
  • Terminal Services is installed and enabled.
  • Terminal Services is configured for application server mode for multiple terminal server clients to run Office 2003.


back to the top

How to Install Office 2003 on a Computer That Is Running Windows 2000 or Windows Server 2003 with Terminal Services Enabled

To install Office 2003 on a computer that is running Windows 2000 or Windows Server 2003 Server with Terminal Services enabled, follow these steps:
  1. Click Start, point to Settings, and then click Control Panel.
  2. Double-click Add/Remove Programs, click Add New Programs, and then click CD or Floppy.
  3. Click Next.
  4. Click Browse.
  5. Locate the root folder of the Office 2003 source location, click Setup.exe, and then click Open.

    Setup.exe is added to the command line that appears in the Open box of the Run Installation Program dialog box.
  6. Click Finish to run Office 2003 Setup.
  7. If requested, type your customer name and product key (CD key) information in the appropriate boxes, and then click Next.

    Note The Next button is not available until you type a valid product key.
  8. Accept the End User License Agreement, and then click Next.
  9. Specify the location where you want to install Office 2003, and then click Next.
  10. On the Choose which applications for setup to install page, click Next.

    If you click Choose detailed installation options for each application on the Choose which applications for setup to install page, and then click Next, the feature tree appears on the Choose installation options for all Office applications and tools page. Because Office Setup detects that you are using Terminal Services, the only installation states that are available are Not Available and Run from My Computer. By default, some features are set to Not Available. Do not change the installation states of these features to Run from My Computer, because you may experience problems with the Office 2003 programs that use these features.

    Warning By default, some features are set to Not Available to make sure that there is optimum performance in a Terminal Server environment, including the elimination of unexpected errors. Do not change the installation states of these features to Run from My Computer.

    Note If your Office 2003 source location is an administrative installation, Run from Network is also displayed as an installation state.
  11. On the Begin installation page, click Install.
  12. When you receive a message that the installation completed successfully, click OK, click Next, and then click Finish.
back to the top

REFERENCES

For more information about how to install and configure Terminal Services, see your Microsoft Windows 2000 documentation and Microsoft Windows 2000 online Help.

For more information about the installation and customization of Office 2003 on Terminal Services, visit the following Microsoft Web site:

http://www.microsoft.com/office/ork/2003/two/ch5/DepD06.htm

For more information about how to install Office 2003 on a computer that is running Terminal Services, visit the following Microsoft Web site:

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/entserver/terminal_server_role.asp

For more information about how to deploy Office 2003, see the Microsoft Office Resource Kit. To do so, visit the following Microsoft Web site:

http://www.microsoft.com/office/ork/2003/two/default.htm

back to the top

The information in this article applies to:

  • Microsoft Office 2003, All Editions, when used with:
      Microsoft Windows XP 64-Bit Edition Version 2003
      Microsoft Windows Server 2003, 64-Bit Enterprise Edition
      Microsoft Windows Server 2003, Enterprise Edition
      Microsoft Windows Server 2003, Standard Edition
      Microsoft Windows 2000 Advanced Server
      Microsoft Windows 2000 Server
      Microsoft Windows 2000 Professional
How do I remove a dead server from the Citrix Management Console? 

Run DSVERIFY SERVERS /CLEAN /FORCE to optimize the Data Store.
DSVerify can be run rom any server in the farm.
Dsverify is available here.
Metaframe Feature Release 3 has a new command line tool called DSCHECK works in a similar way:
DSCHECK /CLEAN

How do I make the IMA Service start even if the datastore is not available on Metaframe XP? 

Page 20 of the Metaframe XP FR2advanced concepts guide reads:
Data Store Activity
All servers in the farm query the data store when they are started. The
following registry setting determines whether or not IMA requires a connection to
the data store in order to start:

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Runtime\PSRequired
(DWORD)
Value: 0 or 1
If the value is 0, IMA can start without a connection to the data store.
If the value is 1, IMA requires a connection to the data store in order to start. After
the first time the IMA service starts successfully, the value is set to 0.

How do I set ICA Keepalives so sessions get disconnected properly?  
This solution from the Citrix Knowledge base pertains to:
  • WinFrame 1.8
  • MetaFrame XP for Windows 2000
  • MetaFrame XP for Microsoft NT Server 4.0, Terminal Server
  • MetaFrame 1.8 for Windows 2000
  • MetaFrame 1.8 for Microsoft NT Server 4.0, Terminal Server
Please read the instructions for your product below:

Symptom

After a ICA_TCP session is abnormally terminated, subsequent viewing of the ICA-TCP session in either Citrix Server Administration, mfadmin.exe Terminal server Administration, tsadmin.exe, or CMC, Citrix Management Console shows the connection in an ACTIVE not a DISCONNECTED state.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

WinFrame 1.7 and WinFrame 1.8

The following Registry key contains the values that control this behavior:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

As documented in the Windows NT Resource Kit, the values most important to WinStation connections are:

ICAKeepAliveInterval REG_DWORD 1 to 0xffffffff milliseconds
This parameter determines the interval separating keep alive retransmissions until a response is received. Once a response is received, the delay until the next keep alive transmission is again controlled by the value of KeepAliveTime. The connection is ended after the number of retransmissions specified by TcpMaxDataRetransmissions have gone unanswered.
Default: 1000 (1 second)

KeepAliveTime REG_DWORD 1 to 0xffffffff milliseconds
This parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a keep alive packet. If the remote system is still reachable and functioning, it acknowledges the keep alive transmission. Keep alive packets are not sent by default. This feature may be enabled on a connection by an application.
Default: 7200000 (two hours)

TcpMaxDataRetransmissions REG_DWORD 0 to 0xffffffff
This parameter controls the number of times TCP will retransmit an individual data segment (non- connect segment) before ending the connection. The retransmission time-out is doubled with each successive retransmission on a connection. It is reset when responses resume. The base time-out value is dynamically determined by the measured round-trip time on the connection.
Default: 5

The KeepAliveTime determines how often a keep alive packet is sent to TCP/IP WinStations. The default is two hours, which is too long. It is recommended that this value be set between 60000 and 300000 (1 to 5 minutes). Make sure that the "decimal" radio button is selected prior to typing this number into the Data field in the Registry Editor. Once a keep alive packet is sent, the TcpMaxDataRetransmissions sets how many more keep alive packets will be sent before the connection is determined to be disconnected. The KeepAliveInterval sets the interval between these retransmission packets. It is not necessary to change these values - only the KeepAliveTime.

In summary, if no response is received after the first keep alive packet (every two hours by default), WinFrame will send another five keep alive packets with a one second interval between each packet. If no response is received, the user is disconnected from the WinStation and the WinStation is reset to an idle state.

MetaFrame 1.8 (SP1 or higher) for Windows Terminal Server, MetaFrame 1.8 (SP2 or higher) for Windows 2000, and MetaFrame XP Application Server for Windows

In environments where the TCP/IP network has high latency, modifying the operation of the Windows TCP/IP stack can improve TCP-based ICA sessions.

The TCP/IP retransmission is controlled by the Windows Terminal Server TcpMaxDataRetransmissions registry value. See Microsoft Knowledgebase Articles Q120642 and Q170359 for more information.

In some networks, ICA Clients might time out when connected to a session and then receive a new session upon reconnect, instead of being reconnected to the dropped session. This new session is received on reconnect because the former host server is not aware that the previous session was dropped due to high network latency.

The Service Packs add a new “ICA KeepAlive” feature so the MetaFrame server can recognize broken ICA sessions and take appropriate action. When the ICA KeepAlive expires, the server disconnects or resets the broken session based on the setting “On broken or timed-out connection...,” which is configurable for the user or ICA connection. Two registry values control the ICA KeepAlive feature. Both values can be manually added to the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

IcaEnableKeepAlive REG_DWORD: 0 or 1
When this value is 0, ICA KeepAlives are disabled. When this value is set to 1, ICA KeepAlives are enabled. The IcaEnableKeepAlive is set to 1 by the Service Pack installation.

ICAKeepAliveInterval REG_DWORD: <number in seconds>
This parameter determines the interval separating keep alive retransmissions until a response is received. Once a response is received, the delay until the next keep alive transmission is again controlled by the value of KeepAliveTime. The connection is ended after the number of retransmissions specified by TcpMaxDataRetransmissions have gone unanswered. If the IcaEnableKeepAlive value is 1, this value controls the frequency at which ICA KeepAlives are sent to the client. This IcaKeepAlive Interval is set to 60 seconds by this hotfix installation. Sixty seconds is also the default interval if this value is not defined but IcaEnableKeepAlive is set to 1.
Default: 60 seconds

The time that elapses between an ICA broken client connection and the MetaFrame server disconnect (or reset) event may be longer than the IcaKeepAliveInterval. For instance, suppose the IcaKeepAliveInterval is set to 15 seconds. A client’s ICA WAN connection is dropped at 12:00:00. The server may not put the session into a disconnected (or reset) state until sometime after 12:00:15, although the session will usually disconnect (or reset) within approximately IcaKeepAliveInterval +2 minutes. This is because the Windows NT 4.0, Terminal Server Edition TCP/IP stack retransmits the ICA keep alive packet a number of times at increasing intervals before timing out. When the TCP/IP stack finishes its retransmissions, the session is disconnected (or reset).

Symptom

After a ICA_TCP session is abnormally terminated, subsequent viewing of the ICA-TCP session in either Citrix Server Administration, mfadmin.exe Terminal server Administration, tsadmin.exe, or CMC, Citrix Management Console shows the connection in an ACTIVE not a DISCONNECTED state.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

WinFrame 1.7 and WinFrame 1.8

The following Registry key contains the values that control this behavior:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

As documented in the Windows NT Resource Kit, the values most important to WinStation connections are:

ICAKeepAliveInterval REG_DWORD 1 to 0xffffffff milliseconds
This parameter determines the interval separating keep alive retransmissions until a response is received. Once a response is received, the delay until the next keep alive transmission is again controlled by the value of KeepAliveTime. The connection is ended after the number of retransmissions specified by TcpMaxDataRetransmissions have gone unanswered.
Default: 1000 (1 second)

KeepAliveTime REG_DWORD 1 to 0xffffffff milliseconds
This parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a keep alive packet. If the remote system is still reachable and functioning, it acknowledges the keep alive transmission. Keep alive packets are not sent by default. This feature may be enabled on a connection by an application.
Default: 7200000 (two hours)

TcpMaxDataRetransmissions REG_DWORD 0 to 0xffffffff
This parameter controls the number of times TCP will retransmit an individual data segment (non- connect segment) before ending the connection. The retransmission time-out is doubled with each successive retransmission on a connection. It is reset when responses resume. The base time-out value is dynamically determined by the measured round-trip time on the connection.
Default: 5

The KeepAliveTime determines how often a keep alive packet is sent to TCP/IP WinStations. The default is two hours, which is too long. It is recommended that this value be set between 60000 and 300000 (1 to 5 minutes). Make sure that the "decimal" radio button is selected prior to typing this number into the Data field in the Registry Editor. Once a keep alive packet is sent, the TcpMaxDataRetransmissions sets how many more keep alive packets will be sent before the connection is determined to be disconnected. The KeepAliveInterval sets the interval between these retransmission packets. It is not necessary to change these values - only the KeepAliveTime.

In summary, if no response is received after the first keep alive packet (every two hours by default), WinFrame will send another five keep alive packets with a one second interval between each packet. If no response is received, the user is disconnected from the WinStation and the WinStation is reset to an idle state.

MetaFrame 1.8 (SP1 or higher) for Windows Terminal Server, MetaFrame 1.8 (SP2 or higher) for Windows 2000, and MetaFrame XP Application Server for Windows

In environments where the TCP/IP network has high latency, modifying the operation of the Windows TCP/IP stack can improve TCP-based ICA sessions.

The TCP/IP retransmission is controlled by the Windows Terminal Server TcpMaxDataRetransmissions registry value. See Microsoft Knowledgebase Articles Q120642 and Q170359 for more information.

In some networks, ICA Clients might time out when connected to a session and then receive a new session upon reconnect, instead of being reconnected to the dropped session. This new session is received on reconnect because the former host server is not aware that the previous session was dropped due to high network latency.

The Service Packs add a new “ICA KeepAlive” feature so the MetaFrame server can recognize broken ICA sessions and take appropriate action. When the ICA KeepAlive expires, the server disconnects or resets the broken session based on the setting “On broken or timed-out connection...,” which is configurable for the user or ICA connection. Two registry values control the ICA KeepAlive feature. Both values can be manually added to the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

IcaEnableKeepAlive REG_DWORD: 0 or 1
When this value is 0, ICA KeepAlives are disabled. When this value is set to 1, ICA KeepAlives are enabled. The IcaEnableKeepAlive is set to 1 by the Service Pack installation.

ICAKeepAliveInterval REG_DWORD: <number in seconds>
This parameter determines the interval separating keep alive retransmissions until a response is received. Once a response is received, the delay until the next keep alive transmission is again controlled by the value of KeepAliveTime. The connection is ended after the number of retransmissions specified by TcpMaxDataRetransmissions have gone unanswered. If the IcaEnableKeepAlive value is 1, this value controls the frequency at which ICA KeepAlives are sent to the client. This IcaKeepAlive Interval is set to 60 seconds by this hotfix installation. Sixty seconds is also the default interval if this value is not defined but IcaEnableKeepAlive is set to 1.
Default: 60 seconds

The time that elapses between an ICA broken client connection and the MetaFrame server disconnect (or reset) event may be longer than the IcaKeepAliveInterval. For instance, suppose the IcaKeepAliveInterval is set to 15 seconds. A client’s ICA WAN connection is dropped at 12:00:00. The server may not put the session into a disconnected (or reset) state until sometime after 12:00:15, although the session will usually disconnect (or reset) within approximately IcaKeepAliveInterval +2 minutes. This is because the Windows NT 4.0, Terminal Server Edition TCP/IP stack retransmits the ICA keep alive packet a number of times at increasing intervals before timing out. When the TCP/IP stack finishes its retransmissions, the session is disconnected (or reset).

How do I Share the XML Service Port 80 with IIS in MetaFrame XP? 
This solution from the Citrix Knowledge base pertains to:
  • MetaFrame XP for Windows 2000
  • MetaFrame XP for Microsoft NT Server 4.0, Terminal Server

Last modified: Fri May 18 13:32:32 2001

The following document details how to share the XML Service port in MetaFrame XP.

1. The Citrix XML Service should not be listed as a service under Control Panel/Services. If it is:

A. Stop the Citrix XML Service.
B. From a command prompt, type ctxxmlss /u. This unregister the service, which deletes the service from Services.

2. Ensure these three files exist in the InetPub\scripts directory:

  • ctxxmlss.txt
  • clm.dll
  • wpnbr.dll

3. Stop and restart the IIS Admin Service or reboot the server.

4. Verify that port 80 is now being shared.

A. Log on to the Citrix Management Console.
B. On the Servers tab, select the server in question.
C. Right click and go to Properties.
D. Select the MetaFrame Settings tab. The Citrix XML Service section lists the TCP/IP port as "Sharing with IIS."

5. Check the NFuse.properties file on the Web server under systemroot/java/trustlib. Make sure that port 80 is registered here also. The line containing this information should look like:

SessionField.NFuse_CitrixServerPort=80

If this line does not refer to port 80, change to port 80 and stop and restart the IIS Admin Service. The Citrix XML Service is now sharing port 80 with IIS.

How do I determine what version of Microsoft Data Access Components ( MDAC ) is on my system? 

HOW TO: Check for MDAC Version

The information in this article applies to:
  • Microsoft Data Access Components 2.1
  • Microsoft Data Access Components 2.1 (GA)
  • Microsoft Data Access Components 2.1 SP1
  • Microsoft Data Access Components 2.1 SP2
  • Microsoft Data Access Components 2.5
  • Microsoft Data Access Components 2.5 SP1
  • Microsoft Data Access Components 2.5 SP2
  • Microsoft Data Access Components 2.6
  • Microsoft Data Access Components 2.6 SP1
  • Microsoft Data Access Components 2.6 SP2
  • Microsoft Data Access Components 2.7
This article was previously published under Q301202

SUMMARY

This article describes two different ways to check which version of Microsoft Data Access Components (MDAC) is installed on a system:
  • Use the Component Checker tool.
  • Check the version information that is stored in the registry.
back to the top

Install and Use the Component Checker Tool

The most reliable way to determine which version of MDAC is installed is to compare the version number of each MDAC DLL file to a list of the DLL files that are shipped with each MDAC version. The Component Checker can help you to do this. It checks the files on the computer, compares them to a list from each version of MDAC, and reports the closest match.

To install Component Checker, follow these steps:
  1. Browse to the following Microsoft Web site:

  2. Click the link to download Component Checker. When you are prompted by the browser, save Cc.exe (a self-extracting executable file) to the desktop.
  3. On the desktop, double-click Cc.exe; this extracts the Component Checker files and installs to the default location, C:\Comcheck.
To use Component Checker to check the MDAC version, follow these steps:
  1. From the Start menu, click Run.
  2. In the Open text box, type c:\comcheck\comcheck.exe and then click OK.
  3. In the Component Checker - Choose Analysis Type dialog box, select Perform Analysis of your machine and automatically determine the release version, and then click OK.
  4. The program attempts to identify the MDAC version on your computer by scanning all of the core MDAC files and registry settings. This process normally takes several minutes. When finished, you should receive the following message:
    The MDAC version that is closest to the version on your computer is `XXXX`.
    					
  5. Click OK.
  6. A summary of the Component Checker scan appears. Note that the Dir, FileDescription, and FileSize errors can be safely ignored.
back to the top

Check the Version Information Stored in the Registry

Although not the most reliable way to check the MDAC version, checking the registry for the version information is an easy way to double-check this information (if you are not experiencing any MDAC-related issues).

The version information is found in the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer

To check the registry, follow these steps:
  1. On the Start menu, click Run.
  2. In the Open text box, type regedit and then click OK; this starts Registry Editor.
  3. In the Navigation pane, drill-down to the following path:
    HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess

  4. In the Details pane, look in the Name column for FullInstallVer and Version. Each of these keys will have corresponding version information in the Data column.
  5. When finished, click Exit on the Registry menu to close Registry Editor.
back to the top

Troubleshooting

Note that the version information stored in the registry may be incorrect for versions of MDAC prior to 2.1 when compared with the versions of the actual files. Windows 2000 installs version 2.5. Only versions of MDAC later than 2.5 may be installed on Windows 2000.

Downloads for Microsoft Data Access Components are available at the following Web site:

back to the top

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
307255 INFO: Component Checker: Diagnose Problems and Reconfigure MDAC Installations

231943 INFO: Microsoft Data Access Components (MDAC) Release History
1 2 [3] 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

Featured Links