[THIN] Re: KB: CTX104489 - Hotfix XE103W2K126 - For MetaFrame XP 1.0 for Windows 2000 Server - English
- From: "Claus, Brian" <BClaus@xxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 17 Sep 2004 10:02:51 -0400
LOL look at the registry value of #16!
16.
In an operation running 24x7, license warning error messages caused a
flurry of help desk calls and emails. Management was also alerted. User
wanted to disable regular notification or an option to control who saw the
error messages.
To avoid the error messages from being sent to everyone, you need to make
the following change to the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
Type: DWORD
Value: AnnoyAdminsOnly=1
With the value set to 1, only administrators receive the license warning
error messages.
[From Hotfix XE103W2K030][#66608]
_____
Brian Claus, MCP, Network+, A+
Network Administrator
WESCO Distribution, Inc.
225 West Station Square Drive, Suite 700
Pittsburgh, PA 15219-1122
Phone: 412-454-2412
Fax: 412-454-2540
bclaus@xxxxxxxxxxxxx <mailto:bclaus@xxxxxxxxxxxxx>
_____
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Jim Kenzig http://thin.net
Sent: Friday, September 17, 2004 9:50 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] KB: CTX104489 - Hotfix XE103W2K126 - For MetaFrame XP
1.0 for Windows 2000 Server - English
CTX104489 - Hotfix XE103W2K126 - For MetaFrame XP 1.0 for Windows 2000
Server - English
This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=CTX104489
Document ID: CTX104489, Created on: Jul 7, 2004, Updated: Sep 15, 2004
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000
Attachment: XE103W2K126.msi (557.5 K)
http://support.citrix.com/servlet/KbServlet/download/4732-102-11741/XE103W2K
126.msi
Hotfix readme name: XE103W2K126.HTM
Hotfix package name: XE103W2K126.MSI
For: MetaFrame XP 1.0 with Service Pack 3 for Windows 2000
Replaces:
XE103W2K004, XE103W2K011, XE103W2K022, XE103W2K030, XE103W2K039,
XE103W2K041, XE103W2K049, XE103W2K053, XE103W2K056, XE103W2K062,
XE103W2K079, XE103W2K089, XE103W2K115, XE103W2K120
Date: June, 2004
Language supported: English (US)
Note: This hotfix can be applied only to a Windows 2000 Server with
MetaFrame XP Version 1.0 with Feature Release 3/Service Pack 3 installed.
Where to Find Documentation
This document describes the issue(s) solved by this hotfix and includes
installation instructions. You can find more information about MetaFrame for
Windows in the Administrator's Guide. The Administrator's Guide is in the
\DOCS directory on the Citrix MetaFrame Server CD. All product documentation
is also available from the Citrix Web site at http://www.citrix.com/support.
The Administrator's Guide is in an Adobe Portable Document (PDF) format
file. To view, search, and print the documentation, you need Acrobat Reader
4 or above. You can download Acrobat Reader for free from the Adobe Web site
at http://www.adobe.com.
Issue(s) Resolved in this Hotfix
Caution! Several fixes require you to edit the registry. Using Registry
Editor incorrectly can cause serious problems that may require you to
reinstall your operating system. Citrix cannot guarantee that problems
resulting from the incorrect use of Registry Editor can be solved. Use
Registry Editor at your own risk.
1.
Note: This line item was fixed in non-English versions of Feature Release 3
with Service Pack 3.
When a modal dialog box was created from an IME pad soon after it was
created in a seamless session, the Windows operating system client sometimes
stopped responding.
In seamless logic, the set owner of the IME pad window was intentionally set
to the foreground. When the accessibility hook was disabled, the seamless
engine could create a situation where its enumeration routine picked the
modal dialog box from the IME pad window as the parent
of the IME pad window. This created a situation where the seamless engine
caused both windows to see each other as the parent.
Now the foreground window, which is set as the parent, is not mistaken as
the child of the enumerated window. If it is the child, the engine will not
associate the window with the parent. The Windows operating system client
does not stop responding.
[From Hotfix XE102W2K004][#50843]
2.
Note: This line item was fixed in non-English versions of Feature Release 3
with Service Pack 3.
Using the Management Console for MetaFrame to configure "use universal
driver only" or "use universal driver only if native driver is unavailable"
to auto-create client printers, the scaling field sometimes did not display
properly when running Excel in an ICA session. This occurred under the
following scenario:
A.
Create a new Excel document.
B.
Type a from A1 to A37 in the Excel work sheet.
C.
Open Print Preview in Excel.
D.
Click Setup.
E.
Change the orientation from Portrait to Landscape.
F.
Change the scaling from Adjust to to Fit to.
G.
Close the Print Setup window.
H.
Click Setup again.
Note that the percentage in the Adjust to field sometimes appears to be
changed.
If Excel.exe was launched from the console and the scenario above was
repeated, the percentage of scaling in the Adjust to field did not change
when the server default printer was the HP LaserJet Series II printer.
The DEVMODE set for autocreated client printers may not have been valid.
This could cause the scaling fields to be interpreted incorrectly by the
print driver.
This fix ensures the DEVMODES for autocreated client printers are valid
before setting them. The scaling fields in Excel launched in an ICA session
display correctly.
[From Hotfix XE102W2K004][#51176]
3.
Note: This line item was fixed in non-English versions of Feature Release 3
with Service Pack 3.
The Connect Client Printers policy did not work consistently. The code was
looking at an incorrect return value and ignored the correct value.
The Connect Client Printers policy was changed so that it looks at the
correct value and the policy now works consistently.
[From Hotfix XE102W2K004][#52158]
4.
Note: This line item was fixed in non-English versions of Feature Release 3
with Service Pack 3.
16-bit Windows applications launched as published applications
intermittently failed to launch.
With some 16-bit applications, timing became an issue when determining if a
process was actually running because these applications run as "tasks" under
Ntvdm.exe.
The timing in the functionality that checks for these "tasks" under
Ntvdm.exe was modified to verify when is a process is running. 16-bit
Windows applications now launch properly as published applications.
[From Hotfix XE102W2K004][#54663]
5.
Note: This line item was fixed in non-English versions of Feature Release 3
with Service Pack 3.
Closing nested popup menus in a seamless session sometimes caused an
application to lose focus when the seamless session was displayed on a
Windows NT 4.0-based system.
Menus that are created as a regular window using the CreateWindow API did
not always adhere to top level window changes correctly.
A new seamless Exception Global Flag has been introduced that provides the
ability to prevent the creation of top level windows in a seamless session.
To set this flag, create the following registry value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Key name: SeamlessFlags
Type: REG_DWORD
Value: 0x1000
Closing nested popup menus in a seamless session no longer causes an
application to lose focus.
[From Hotfix XE103W2K004][#56912]
6.
Note: This line item was fixed in non-English versions of Feature Release 3
with Service Pack 3.
When ATOK IME Version 16 is installed on a MetaFrame server and a user
attempts to use it in an ICA session, the session may not logoff even after
all the published application are
closed.
ATOK Version 16 introduced new processes to host IME windows. Those
processes were left in the session and MetaFrame regarded them as user
processes.
With this fix, those processes are regarded as system processes. MetaFrame
logs off the session if only those system processes are present.
The ICA session is logged off if all the published applications in the
session are closed.
[From Hotfix XE103W2K004][#61232]
7.
Additional output trays on client printers were not being saved and
restored on subsequent logons. This affected certain Lexmark-developed
printer drivers among others.
This occurred because printer driver data registry keys greater than 2KB in
length were not being read and could not be saved or restored.
This fix ensures that printer driver data registry keys up to 16KB are saved
and restored.
Some device-specific properties that were reset with each logon; for
example, output expander setups, are saved and restored on subsequent
logons.
[From Hotfix XE103W2K004][#62041]
8.
When using the shadow taskbar, the server occasionally experienced a fatal
system error.
This occurred because wsxica was calling a function in TermService but it
was not checking whether or not the returned value was an error. This caused
an access violation error.
With this hotfix, the function now checks to determine if the returned value
is an error or not.
[From Hotfix XE103W2K004][#62319]
9.
Some client printer properties were not being saved and restored on
subsequent logons. This affected certain Lexmark-developed printer drivers
among others.
This occurred because printer driver data registry keys greater than 2KB in
length were not being read and could not be saved or restored.
This fix ensures that printer driver data registry keys up to 16KB are saved
and restored.
Some device-specific properties that were reset with each logon; for
example, output expander setups, are saved and restored on subsequent
logons.
[From Hotfix XE103W2K004][#62625]
10.
Changing a password when logging on to a seamless session launched two
instances of the same published application.
This problem occurred as a result of the functionality in the seamless
engine that determines whether or not applications are launched.
With this update, only one instance of an application is launched if a
password is changed during logon to a seamless session.
[From Hotfix XE103W2K004][#63595]
11.
When published seamlessly, text-based telnet application flickered after
upgrading to or installing Citrix' Feature Release 3.
This occurred because new logic introduced with Feature Release 3 caused the
client to treat certain windows of an application differently from the way
the server was treating them.
With this fix, the server sends the correct information to the client.
[From Hotfix XE103W2K004][#65105]
12.
When running an application in a seamless session, a problem sometimes
occurred when the application changed its large icon using WM_SETICON. The
operating system failed to change the associated small icon. This hotfix
introduces a new per-window exception flag
(TYPE_TWI_NO_SMALLICON_FROMWINCLASS 0X200) that can be set to direct the
seamless engine to not request the small icon associated with the specified
window class. The addition of a registry key specifies the window class name
Navigate to the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: ClassName
Type: REG_SZ
Data: <Name of the window class>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: Type
Type: REG_DWORD
Data: 200 (hex)
[From Hotfix XE103W2K011][#63960]
13.
Outlook.exe's parameters were used by the client when launching
OutlookExpress as a published application if client-to-server content
redirection was enabled. This occurred because the default setting was to
use Outlook.exe's parameters for mailto requests.
This hotfix adds functionality to better handle mailto requests from the
client. Based on the mailer application to be launched, the appropriate
mailto parameters are selected from the registry to format the launch
string.
[From Hotfix XE103W2K022][#53537]
14.
When a session was reset because of an ICA connection time-out or logged
off from the Management Console, the client autocreated printer properties
were saved in the incorrect registry key. As a result, MetaFrame could not
get the current user security ID from the winstation query.
With this hotfix, the client autocreated printer properties are saved in the
correct registry key.
[From Hotfix XE103W2K030][#65428]
15.
If a starting program was specified under the Environment tab in User
Account Properties and if the ICA pass-through Client had pass through
authentication enabled, Ssonsvr.exe was running in the user's ICA session.
When the user exited the application (specified under the Environment tab in
User Account Properties), the ICA session could not be logged off; the
administrator had to manually stop the Ssonsvr.exe process. The thread that
caused the Ssonsvr.exe process to exit when the user logged off from the
application was not being started.
Now The thread that causes the Ssonsvr.exe process to exit is started when
the user logs off from the application.
[From Hotfix XE103W2K030][#66092]
16.
In an operation running 24x7, license warning error messages caused a
flurry of help desk calls and emails. Management was also alerted. User
wanted to disable regular notification or an option to control who saw the
error messages.
To avoid the error messages from being sent to everyone, you need to make
the following change to the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
Type: DWORD
Value: AnnoyAdminsOnly=1
With the value set to 1, only administrators receive the license warning
error messages.
[From Hotfix XE103W2K030][#66608]
17.
A Java application experienced a fatal error when running as a published
application or the initial application. The size of the buffer for the
window class name was incorrect; the error occurred if the application
window exceeded 64 characters.
This behavior has been corrected.
[From Hotfix XE103W2K030][#67014]
18.
Windows 2000 Server with Service Pack 3 or Service Pack 4:
By selecting Logoff from the ICA Connection Center, a user was able to log
off another user's seamless, locked session without being prompted for a
password. The unauthenticated user also had access to the locked session
while the logoff script was running.
This behavior has been corrected.
[From Hotfix XE103W2K030][#67296]
19.
Logon names prefaced with a pound sign or hash mark (#) followed by a
decimal value equal to or greater than 49152 sometimes caused a memory leak.
For example, the logon name #99999 would cause the memory leak.
This hotfix corrects that behavior; user logon names prefaced with a pound
sign or hash mark (#) followed by a decimal value equal to or greater than
49152 can be used without causing a memory leak.
[From Hotfix XE103W2K039][#66490]
20.
Note: For this fix to work correctly, you need Version 7.100 or later of
the Win32 ICA Client.
Instant Messenger type programs commonly use the FlashWindow() API to flash
the taskbar button to alert users of incoming messages. Prior to this, this
functionality was not available when running a seamless session.
This fix adds support for this API when running a seamless session. The
taskbar button now flashes to alert users of incoming messages.
[From Hotfix XE103W2K041][#69369]
21.
An ICA session sometimes failed to delete autocreated printers when a user
logged off from the session soon after logging on. The thread to delete
printers finished its task before the thread to create them finish its task,
causing some printers to be left in the session.
With this hotfix, the thread to delete printers waits for the thread to
create printers to finish its task All printers in the session are always
deleted correctly.
[From Hotfix XE103W2K049][#69638]
22.
When a user disconnected from a session, then later reconnected to it from
a different workstation that had a different printer, the new printer was
not autocreated and the session had the printer from the first connection.
A race condition was discovered where the previous client name was sent
instead of the new one. This hotfix corrects that race condition.
[From Hotfix XE103W2K053][#68279]
23.
Sometimes a published application was launched more than once in the same
session in the following scenario:
*
The published application was configured with Allow only one instance of the
application for each user in the Management Console
*
The user rapidly clicked the published application icon in the Program
Neighborhood Client
*
The published application was to run seamlessly
This occurred because the program was not enforcing an application instance
limit check while launching a published application. This hotfix corrects
the problem and only one instance of the published application is launched.
[From Hotfix XE103W2K053][#71801]
24.
An access violation occurred in Wsxica.dll. This occurred because
winstations were not being enumerated properly.
The winstations are now being enumerated properly and the access violation
no longer occurs.
[From Hotfix XE103W2K053]]#72688]
25.
If a published application was a program that created a new process and
then terminated itself, the published application appeared in the Management
Console for MetaFrame XP. However, in a seamless session the application was
launched through session sharing, the application appeared in the Management
Console but then disappeared.
By default, the thread that checks the process cares about only the first
instance of the launched process. The thread regarded the published
application as terminated when the first instance of the process was
terminated even if that process created a separate process.
This fix provides a way to configure those published applications to use the
JOB object so that additional processes created by the initial process are
considered as published applications.
For this fix to work properly, you need to perform the following steps:
*
If the command line of the published application is [ApplicationPath], go to
the following registry key and make changes as necessary:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\Start
InJobObject
Key Value: [ApplicationPath]
Type: DWORD
Value: 0
*
For example, if the command line specified for the published application is
c:\notepad.cmd, go to the following registry key and make changes as
necessary:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\Start
InJobObject
Key Value: c:\notepad.cmd
Type: DWORD
Value: 0
For those applications whose command line is specified in the
StartInJobObject key, the published application will not disappear from the
Management Console until all of the processes created by the process are
terminated.
[From Hotfix XE103W2K056][#63894]
26.
An administrator on a Feature Release 3 server could not enumerate users on
a Feature Release 2 server from the shadow taskbar. An empty list was
returned.
With this fix, the administrator is able to enumerate the users on a Feature
Release 2 server when he is using the shadow taskbar on a Feature Release 3
server.
[From Hotfix XE103W2K056][#71364]
27.
If Connect Client Printers at Logon was not checked, users either were
completely unable to map client printers or could not see any of the UPD
printers available when connecting to a printer. A misplaced initialization
of the Metafile drivers caused the drivers to be unavailable.
This hotfix enables the Metafile drivers; client users can now map to any
client printer.
[From Hotfix XE103W2K062][#73621, #73769]
28.
MetaFrame XP was bypassing any application limits set in the Management
Console for pass-through connections. A global variable was not being
properly set in pass-through connections.
The global variable is now set correctly and MetaFrame adheres to any
application limits set in the Management Console for pass-through
connections.
[From Hotfix XE103W2K079][#77372]
29.
If session sharing was disabled, client-to-server redirection failed
because applications with command lines that contained spaces in the paths
were not being launched.
This fix ensures that client-to-server redirection will work even if session
sharing is disabled.
[From Hotfix XE103W2K079][#79331]
30.
The server-side wallpaper appeared occasionally for a short time when a
seamless window was closed. There was a slight delay between the time the
window was closed and the seamless engine notified the client that the
window was closed. During that time, the client-side engine tried to update
the window that was already closed, resulting in the brief appearance of the
server-side wallpaper.
This fix ensures that the seamless engine immediately detects that the
window is closed and the server-side wallpaper no longer appears.
[From Hotfix XE103W2K079][#80221]
31.
When an application running in seamless mode became unresponsive, users
sometimes could not switch to other applications that were running in
seamless mode also. Clicking the taskbar icon or using the Alt-Tab sequence
did not work. The server seamless engine was using an API that did not
return if the target application was unresponsive.
This fix provides additional routines that will call only those applications
that are responding. Users can switch to other applications even if one is
unresponsive.
[From Hotfix XE103W2K089][#76070]
32.
The display speed of the combo list box became very slow if the list box
expanded beyond the area of the background window. The seamless routine that
checked to determine whether or not the target window was a top-level window
ignored the window, causing a delay in the display of the window.
A new API is now used to determine whether or not the target window is a
top-level window. The combo list box appears as quickly as other types of
windows in a seamless session.
[From Hotfix XE103W2K089][#83550]
33.
When the following registry entry was set, Sehook20.dll was still loaded in
the session:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\Wfshell\TWI
Type: REG_DWORD
Data: SeamlessFlags=0x4
In certain situations the registry entry was ignored, causing Sehook20.dll
to be loaded despite the registry setting.
This hotfix ensures that the registry entry is used to determine whether or
not to load Sehook20.dll in the session.
[From Hotfix XE103W2K089][#83555]
34.
This fix addresses a custom application's performance when run seamlessly.
Some applications appeared to be slower to respond when performing actions
such as moving, resizing, or closing windows. This fix introduces two new
registry settings that allow administrators to configure an explicit time
interval for the seamless engine mechanism to monitor when changes take
place in the seamless applications.
Create the following two registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Key: WorkerWaitInterval
Type: REG_DWORD
Value: <Number of milliseconds allowed> (Values are between 5 - 500; the
default is 50.)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Key: WorkerFullCheckInterval
Type: REG_DWORD
Value: <Number of milliseconds allowed> (Values are between 50 - 5000; the
default is 500.)
For both values, a larger size slows responsiveness but improves
scalability; a smaller size increases responsiveness but decreases
scalability slightly. The level of scalability depends on several factors,
such as hardware sizing, types of applications, network performance, and
number of users.
[From Hotfix XE103W2K115][#85657]
35.
Some custom applications that did not display properly when running on
Windows XP/2000 with the Windows XP Theme enabled sometimes saw the same
behavior when running as a seamless application on MetaFrame XP Feature
Release 3 on Windows 2003 that does not have the Windows XP Theme enabled.
For example, the title bar of the application is larger in height.
Starting with MetaFrame XP Feature Release 3 for Windows 2000/2003, the
server seamless engine has extended support for certain window style
properties of the workstation where the seamless application is running; for
example, the styles generated by Windows XP Themes.
This hotfix introduces a new seamless global registry flag that, when set,
instructs the server-side seamless engine not to read certain client
workstation window style information.
Set the following server-side registry key to instruct the server seamless
engine not to synchronize with the client's window style that pertains to
those representative of the Windows XP Theme:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: SeamlessFlags
Type: REG_DWORD
Value: 0x4000
Custom applications that do not display properly when running on Windows
XP/2000 with the Windows XP Theme enabled can be run in a seamless session
from a workstation that has the Windows XP Theme enabled and be displayed
using the Windows Classic style.
[From Hotfix XE103W2K120][#87052]
36.
If users attempted to access a Web site through Start > Run with a URL that
was longer than 256 characters (in some cases longer than 202 characters),
the correct Web page appeared but Wfshell experienced a fatal error. This
problem occurred because of a buffer overrun in handling the URL.
With this fix, when a URL longer than the allowed character limit is pasted
into Start > Run, Internet Explorer is launched and Wfshell remains running
without experiencing a fatal error.
[From Hotfix XE103W2K126][#87825]
37.
This is an enhancement to add the ability to configure which of the
server-to-client content redirection file types are allowed to be
redirected.
By default, server-to-client content redirection redirects all or none of
the file types (http, https, rtsp, rtspu, pnm, mms).
A new registry key is specified to allow certain file types to be excluded
from content redirection. If HKEY_LOCAL_MACHINE \SOFTWARE\Citrix\SFTA
\DisableServerFTA is set, the multistring registry value
HKEY_LOCAL_MACHINE\SOFTWARE \Citrix\SFTA\NoRedirectClasses specifies which
file types are excluded from redirection. If the file type is not in the
list, it is redirected.
To implement this enhancement, make the following value changes to the
registry key using regedt32:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SFTA
Name: DisableServerFTA
Type: REG_DWORD
Value: 1
Name: NoRedirectClasses
Type: REG_MULTI_SZ
Value: Specify any combination of the following values:
http,https,rtsp,rtspu,pnm,mms (these values are comma-delimited with no
space between)
With these registry changes, administrators can configure which file types
to exclude when using server-to-client redirection.
[From Hotfix XE103W2K126][#88380]
38.
Some of the Japanese IME 2003 functions were not available in published
applications because the routine to enable IME was not being executed.
This fix includes the routine to ensure that IME 2003 will function as
expected in published applications.
[From Hotfix XE103W2K126][#89686]
39.
When reconnecting to a disconnected seamless session, users were unable to
maximize the application window by double-clicking its title bar. Although
the application window did get maximized temporarily, it reverted to its
previous size immediately thereafter.
This fix corrects the issue.
[From Hotfix XE103W2K126][#87308]
Installation Instructions
Note: This hotfix is packaged with Microsoft Windows Installer. You can
deploy the hotfix package to a group of servers using Microsoft Active
Directory Group Policy Object or using Citrix Installation Manager. For more
information, see the Citrix server Administrator's Guide or the Citrix
Installation Manager Administrator's Guide.
1.
Download the hotfix package from the Hotfixes and Service Packs page of the
Citrix Web site at http://www.citrix.com.
2.
Copy the hotfix package to an empty directory on the hard drive of the
MetaFrame server.
3.
Close all applications.
4.
Run the executable.
5.
Shut down and restart the server.
Note: To install this hotfix silently, use the /q option after the
executable. For example:
msiexec /I XE103W2K126.MSI /q
Using the /q option without additional options automatically restarts the
server.
For additional information about msiexec, see the Microsoft Web site at
http://www.microsoft.com. Search on keyword msiexec.
Uninstallation Instructions
1.
From the Start menu, select Setting > Control Panel.
2.
In Control Panel, double-click Add/Remove Programs.
3.
Highlight the hotfix you want to uninstall and click Remove.
4.
Follow the directions on-screen.
Files Updated
chgcdm.exe
69,632
07/02/2004
06:45p
ctxnotif.dll
98,304
07/02/2004
06:45p
ctxrpc.dll
37,272
07/02/2004
06:45p
hotfix.exe
74,000
04/28/2003
01:55p
iexplore.exe
32,768
07/02/2004
06:45p
printcfg.exe
114,688
07/02/2004
06:45p
seamls20.dll
53,248
07/02/2004
06:45p
sehook20.dll
15,872
07/02/2004
06:45p
wfshell.exe
98,304
07/02/2004
06:45p
wsxica.dll
196,744
07/02/2004
06:45p
Copyright © 2004 Citrix Systems, Inc. All rights reserved.
Citrix, MetaFrame, and MetaFrame XP are registered trademarks of Citrix
Systems, Inc. in the United States and other countries.
All other trademarks and registered trademarks are the property of their
respective owners.
********************************************************
This Weeks Sponsor triCerat:
Have you had your fill of printing support calls, unauthorized apps running on
unsecured Terminal Servers, profile headaches, and application performance
problems? Join us and learn how you can have a less demanding on-demand
enterprise!
http://www.tricerat.com/?page=events#register
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
********************************************************
This Weeks Sponsor triCerat:
Have you had your fill of printing support calls, unauthorized apps running on
unsecured Terminal Servers, profile headaches, and application performance
problems? Join us and learn how you can have a less demanding on-demand
enterprise!
http://www.tricerat.com/?page=events#register
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
