Speed Screen and Resource Manager 1.0b may Fail when IBM's Director Console Software Agent Is Instal
Speed Screen and Resource Manager 1.0b may Fail when IBM's Director Console Software Agent Is Instal Speed Screen and Resource Manager 1.0b may Fail when IBM's Director Console Software Agent Is Instal
Citrix states in their article: CTX483818
CTX483818 - Speed Screen and Resource Manager 1.0b may Fail when IBM's Director Console Software Agent Is Installed
This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX483818
Document ID: CTX483818, Created on: Nov 25, 2002, Updated: Sep 12, 2003
Products: Citrix MetaFrame 1.8 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame 1.8 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Resource Management Services 1.0b
Modify the following registry keys:
Issues
When IBM’s Remote Supervisor Adapter (RSA - Hardware) with the IBM Director Console Monitoring agents (Software) is installed on a MetaFrame 1.8 Service Pack 3 for TSE 4.0 Service Pack 6 Server, the following problems may occur:
WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Citrix cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.
1.
If Citrix Resource Manager Services Version 1.0x is installed, the following registry entry may be corrupted:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Windows.
The registry value AppInit_DLLs may have corrupted strings such as: z@appinit.dll.
You can correct this by editing the appInit_DLLs registry entry and removing the z@ characters.
2.
Speed Screen Latency Reduction does not work. The IBM software adds the DLL name, TwgProc.DLL, to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Windows Value: AppInit_DLLs
The Citrix DLL, zlc_api.dll, which is required for SpeedScreen Latency Reduction to load, is the last entry listed.
The strings in the registry value may appear as follows: TwgProc.DLL, zlc_api.dll.
To correct this issue, place the Citrix DLL, zlc_api.dll as the first entry in the above registry key.
Note: The IBM Director Console also functions in this configuration.
3.
Microsoft’s appinit key has a 32-character limit. This may prevent Speed Screen’s zlc_api.dll from being called when an ICA client connects.
a. Run Filemon from http://www.sysinternals.com to identify if ZLC_API.dll is called when an ICA client connects to your Metaframe server.
b. Identify the placement of ZLC_API.dll in the appinit registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Windows
c. If the placement of zlc_api.dll or any portion is beyond the 32-Character limit move the dll to the beginning of the registry value.
Note: This may cause other entries in the AppInit registry key to not be called during Winlogon.
d. Alternately, use Ln.exe tool from the Microsoft Windows NT 4.0 Resource Kit to create "hard" links with shorter names to the DLLs that are listed in the AppInit registry key. (Q317372)
e. Q197571 Working with the AppInit_DLLs Registry Value
User login
Who's new
- japhabept
- Rullydery
- eagenorce
- rittaarier
- swasseZex