[THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 -ForMetaFrame X P for Windows 2000 Server - English
- From: "Steve Greenberg" <steveg@xxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 13 Apr 2004 08:15:41 -0700
Yes, more printing stuff!
Steve Greenberg
Thin Client Computing
34522 N. Scottsdale Rd. suite D8453
Scottsdale, AZ 85262
(602) 432-8649
(602) 296-0411 fax=20
steveg@xxxxxxxxxxxxxx
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On =
Behalf
Of BRUTON, Malcolm, FM
Sent: Tuesday, April 13, 2004 2:39 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 -ForMetaFrame X P =
for
Windows 2000 Server - English
What does 55 supposedly fix? Printing stuff?
Malcolm
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On =
Behalf
Of Steve Greenberg
Sent: 13 April 2004 01:36
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 -ForMetaFrame XP =
for
Windows 2000 Server - English
Just had to deal with this again today and ended having to call Citrix
support. Tursn out the roll up did not include 016 which is still =3D
considered a critical print fix. Also, 055 is not rolled up and not =
publicly
=3D available. So in addition to pulling your hair out to figure this =
out,
when you =3D trace all the KB articles they refer to 055 which is not
available on the website-aargh!
Therefore, the current recommendations are to do 016 and 089, if you =3D =
need
055 you can get it by crying to Citrix....
Steve Greenberg
Thin Client Computing
34522 N. Scottsdale Rd. suite D8453
Scottsdale, AZ 85262
(602) 432-8649
(602) 296-0411 fax=3D20
steveg@xxxxxxxxxxxxxx
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On =
=3D
Behalf Of Jay Moock
Sent: Thursday, April 08, 2004 2:11 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 -ForMetaFrame XP =
=3D
for Windows 2000 Server - English
It is my understanding that if 056 replaced any previous hotfixes then =
=3D
those would also be listed on 089's list.
I don't have 056 so I can't say for sure, but I do have 041 and here's =
=3D
what it replaced:
XE103W2K004, XE103W2K011, XE103W2K022, XE103W2K030, XE103W2K039
All of those are reflected in 089:
XE103W2K004, XE103W2K011, XE103W2K022, XE103W2K030, XE103W2K039,
XE103W2K041, XE103W2K049, XE103W2K053, XE103W2K056, XE103W2K062, =3D
XE103W2K079
Sure it may take a little work to figure out what you need, but the
information is definitely available. I suppose the reason that they =3D =
don't
post a roll-up package is because that is what the SP's are for.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Shonk, Joe - Perot
Sent: Thursday, April 08, 2004 4:58 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 -ForMetaFrame XP =
=3D
for Windows 2000 Server - English
And how are we suppose to know that 016 didn't get rolled up in another
hotfix.
In order to find out what the CURRENT list of hotfixes you have to =3D
enumerate and remediate ALL of hotfixes from the beginning. Sure 056 is
include =3D in 089, but what hotfixes did 056 replace? (if any)
Joe
-----Original Message-----
From: Jay Moock [mailto:jmoock@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, April 08, 2004 12:26 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 - ForMetaFrame XP =
=3D
for Windows 2000 Server - English
They always say right at the top of the page which hotfixes they =3D =
replace.
Clearly XE103W2K016 is not in the list so what are you complaining =3D =
about?
------------
Hotfix readme name: XE103W2K089.HTM
Hotfix package name: XE103W2K089.MSI
For: MetaFrame XP 1.0 with Service Pack 3 for Windows 2000
Replaces:
XE103W2K004, XE103W2K011, XE103W2K022, XE103W2K030, XE103W2K039,
XE103W2K041, XE103W2K049, XE103W2K053, XE103W2K056, XE103W2K062, =3D
XE103W2K079
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Shonk, Joe - Perot
Sent: Thursday, April 08, 2004 12:49 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 - ForMetaFrame XP =
=3D
for Windows 2000 Server - English
It does not appear to have the required XE103W2K016 printing patch.
I wish Citrix would manage their patches better. Either roll them all =
=3D up
every so often or have a list of recommend hotfixes. You have to guess
which ones you need and which one are included/rolled up into another =
=3D one.
Joe
-----Original Message-----
From: Steve Greenberg [mailto:steveg@xxxxxxxxxxxxxx]
Sent: Thursday, April 08, 2004 9:42 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 - For MetaFrame =
=3D XP
for Windows 2000 Server - English
Does anyone know if this a complete "roll up"?
Steve Greenberg
Thin Client Computing
34522 N. Scottsdale Rd. suite D8453
Scottsdale, AZ 85262
(602) 432-8649
(602) 296-0411 fax=3D3D20
steveg@xxxxxxxxxxxxxx
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On =
=3D =3D3D
Behalf Of Jim Kenzig http://thin.net
Sent: Thursday, April 08, 2004 4:12 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] KB: CTX103692 - Hotfix XE103W2K089 - For MetaFrame XP =
=3D =3D3D
for Windows 2000 Server - English=3D3D20
CTX103692 - Hotfix XE103W2K089 - For MetaFrame XP for Windows 2000 =
=3D3D =3D
Server
- English
This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=3D3D3DCTX103692
Document ID: CTX103692, Created on: Mar 30, 2004, Updated: Mar 30, 2004
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000
Attachment: XE103W2K089.msi (548.0 K)
http://support.citrix.com/servlet/KbServlet/download/4032-102-10903/XE103=
=3D
=3D3D
W2K
089.msi
Hotfix readme name: XE103W2K089.HTM
Hotfix package name: XE103W2K089.MSI
For: MetaFrame XP 1.0 with Service Pack 3 for Windows 2000
Replaces:
XE103W2K004, XE103W2K011, XE103W2K022, XE103W2K030, XE103W2K039,
XE103W2K041, XE103W2K049, XE103W2K053, XE103W2K056, XE103W2K062, =3D3D
XE103W2K079
Date: March, 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 =3D3D =3D
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 =
=3D
=3D3D for Windows in the Administrator's Guide. The Administrator's =
Guide is =3D
in =3D3D the \DOCS directory on the Citrix MetaFrame Server CD. All =
product
=3D3D documentation is also available from the Citrix Web site at =3D3D
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 =
=3D3D
Reader 4 or above. You can download Acrobat Reader for free from the =3D =
Adobe
Web =3D3D 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 =3D3D =
=3D
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 =3D3D
sometimes stopped responding.
In seamless logic, the set owner of the IME pad window was intentionally =
=3D
=3D3D set to the foreground. When the accessibility hook was disabled, =
the =3D3D
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 =
=3D
IME pad window. This created a situation where the seamless engine =
caused =3D
both windows to see each other as the parent.
Now the foreground window, which is set as the parent, is not mistaken =
=3D =3D3D
as the child of the enumerated window. If it is the child, the engine =
will =3D
=3D3D not associate the window with the parent. The Windows operating =
system =3D
=3D3D client does not stop responding.
[From Hotfix XE102W2K004][#50843]
2.
Note: This line item was fixed in non-English versions of Feature =3D3D =
=3D
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 =3D3D
unavailable" to auto-create client printers, the scaling field sometimes =
=3D
did not =3D3D display properly when running Excel in an ICA session. =
This =3D
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 =3D3D =
=3D
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 =
=3D3D
session display correctly.
[From Hotfix XE102W2K004][#51176]
3.
Note: This line item was fixed in non-English versions of Feature =3D3D =
=3D
Release 3 with Service Pack 3.
The Connect Client Printers policy did not work consistently. The code =
=3D =3D3D
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 =3D3D =
=3D
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 =
=3D =3D3D
if a process was actually running because these applications run as =
"tasks"
=3D =3D3D 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 =3D3D =
=3D
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 =
=3D =3D3D
did not always adhere to top level window changes correctly.
A new seamless Exception Global Flag has been introduced that provides =
=3D =3D3D
the ability to prevent the creation of top level windows in a seamless =
=3D3D
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 =3D3D =
=3D
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 =
=3D =3D3D
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. =3D3D =
=3D
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 =
=3D
=3D3D 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 =
=3D =3D3D
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 =
=3D =3D3D
fatal system error.
This occurred because wsxica was calling a function in TermService but =
=3D =3D3D
it was not checking whether or not the returned value was an error. This =
=3D
=3D3D caused an access violation error.
With this hotfix, the function now checks to determine if the returned =
=3D =3D3D
value is an error or not.
[From Hotfix XE103W2K004][#62319]
9.
Note: This line item was fixed in non-English versions of Feature =3D3D =
=3D
Release 3 with Service Pack 3.
After exiting a published application in an ICA session, the session did =
=3D
=3D3D not close on a MetaFrame/Windows 2003 Server if the Windows =
Product =3D3D
Activation process (Wpabaln.exe) was running. The ICA session was not =
=3D
closed if any applications other than the system applications that were =
=3D
registered =3D3D with MetaFrame were running.
To resolve this problem, Wpabaln.exe was registered to the MetaFrame =
=3D3D
system process list. The ICA session now closes even if the Windows =3D
Product Activation process is running.
[From Hotfix XE103W2K004][#62617]
10.
Some client printer properties were not being saved and restored on
subsequent logons. This affected certain Lexmark-developed printer =3D3D =
=3D
drivers among others.
This occurred because printer driver data registry keys greater than 2KB =
=3D
=3D3D 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 =
=3D =3D3D
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]
11.
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]
12.
When published seamlessly, text-based telnet application flickered =
=3D3D =3D
after upgrading to or installing Citrix' Feature Release 3.
This occurred because new logic introduced with Feature Release 3 caused =
=3D
=3D3D the client to treat certain windows of an application differently =
from =3D
the =3D3D way the server was treating them.
With this fix, the server sends the correct information to the client.
[From Hotfix XE103W2K004][#65105]
13.
When running an application in a seamless session, a problem sometimes
occurred when the application changed its large icon using WM_SETICON. =
=3D =3D3D
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 =3D3D
specified window class. The addition of a registry key specifies the =3D
window class =3D3D 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]
14.
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 =
=3D =3D3D
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]
15.
When a session was reset because of an ICA connection time-out or =3D3D =
=3D
logged off from the Management Console, the client autocreated printer =
=3D3D =3D
properties were saved in the incorrect registry key. As a result, =
MetaFrame
could =3D =3D3D not get the current user security ID from the winstation =
query.
With this hotfix, the client autocreated printer properties are saved in =
the
=3D3D =3D correct registry key.
[From Hotfix XE103W2K030][#65428]
16.
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 =3D3D =
=3D
session. When the user exited the application (specified under the
Environment =3D =3D3D tab in User Account Properties), the ICA session =
could not
be logged off; =3D the administrator had to manually stop the =
Ssonsvr.exe
process. The thread =3D =3D3D that caused the Ssonsvr.exe process to =
exit when
the user logged off =3D from the application was not being started.
Now The thread that causes the Ssonsvr.exe process to exit is started =
=3D =3D3D
when the user logs off from the application.
[From Hotfix XE103W2K030][#66092]
17.
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 =
=3D =3D3D
the error messages.
To avoid the error messages from being sent to everyone, you need to =
=3D3D =3D
make the following change to the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
Type: DWORD
Value: AnnoyAdminsOnly=3D3D3D1
With the value set to 1, only administrators receive the license warning
error messages.
[From Hotfix XE103W2K030][#66608]
18.
A Java application experienced a fatal error when running as a =3D3D =
=3D
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]
19.
Windows 2000 Server with Service Pack 3 or Service Pack 4:
By selecting Logoff from the ICA Connection Center, a user was able to =
=3D =3D3D
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]
20.
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 =
=3D =3D3D
leak. For example, the logon name #99999 would cause the memory leak.
This hotfix corrects that behavior; user logon names prefaced with a =
=3D3D =3D
pound sign or hash mark (#) followed by a decimal value equal to or =
greater
=3D =3D3D than 49152 can be used without causing a memory leak.
[From Hotfix XE103W2K039][#66490]
21.
Note: For this fix to work correctly, you need Version 7.100 or later =
=3D =3D3D
of the Win32 ICA Client.
Instant Messenger type programs commonly use the FlashWindow() API to =
=3D =3D3D
flash the taskbar button to alert users of incoming messages. Prior to =
=3D
this, =3D3D this functionality was not available when running a seamless =
=3D
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]
22.
In Windows Server 2000, client printers could not be autocreated =3D3D =
=3D
without installing a Citrix Feature Release 3 license.
Terminal services in Windows Server 2000 were changed so that the =3D3D =
=3D
printer virtual channel needed to be created in the system context. The =
=3D3D
=3D MetaFrame server would not issue a printer autocreation command =
through
the =3D3D =3D printer virtual channel.
This hotfix ensures that the printer virtual channel is created in the
system context and a Feature Release 3 license is no longer required.
[From Hotfix XE103W2K049][#63348]
23.
An ICA session sometimes failed to delete autocreated printers when a =
=3D =3D3D
user logged off from the session soon after logging on. The thread to =
=3D
delete printers finished its task before the thread to create them =
finish
its =3D =3D3D 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 =3D3D =
=3D
always deleted correctly.
[From Hotfix XE103W2K049][#69638]
24.
When a user disconnected from a session, then later reconnected to it =
=3D =3D3D
from a different workstation that had a different printer, the new =3D =
printer
=3D3D was not autocreated and the session had the printer from the first =
=3D3D
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]
25.
Sometimes a published application was launched more than once in the =
=3D =3D3D
same session in the following scenario:
.
The published application was configured with Allow only one instance of =
=3D
=3D3D 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 =3D3D
instance limit check while launching a published application. This =3D =
hotfix
=3D3D corrects the problem and only one instance of the published =
application
=3D is =3D3D launched.
[From Hotfix XE103W2K053][#71801]
26.
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 =3D3D =
=3D
violation no longer occurs.
[From Hotfix XE103W2K053]]#72688]
27.
If a published application was a program that created a new process and
then terminated itself, the published application appeared in the =3D3D
Management Console for MetaFrame XP. However, in a seamless session the
application =3D3D was launched through session sharing, the application =
=3D
appeared in the =3D3D Management Console but then disappeared.
By default, the thread that checks the process cares about only the =
=3D3D =3D
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 =
=3D
=3D3D the JOB object so that additional processes created by the initial =
=3D
process =3D3D
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest =3D =
constraint
to scaling up?! Get this free white paper to understand the real =3D
constraints & how to overcome them. SAVE MONEY by scaling-up rather than
buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D147
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or=3D20
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest =
constraint to
scaling up?! Get this free white paper to understand the real =
constraints &
how to overcome them. SAVE MONEY by scaling-up rather than buying more
servers. http://www.rtosoft.com/Enter.asp?ID=3D147
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
*************************************************************************=
***
*******
The Royal Bank of Scotland plc. Registered in Scotland No 90312.
Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB.
Authorised and regulated by the Financial Services Authority =20
=20
This e-mail message is confidential and for use by the =
=20
addressee only. If the message is received by anyone other =20
than the addressee, please return the message to the sender =20
by replying to it and then delete the message from your =
=20
computer. Internet e-mails are not necessarily secure. The =
Royal Bank of Scotland plc does not accept responsibility for =20
changes made to this message after it was sent.
=20
Whilst all reasonable care has been taken to avoid the =
transmission of viruses, it is the responsibility of the recipient to
ensure that the onward transmission, opening or use of this =20
message and any attachments will not adversely affect its =20
systems or data. No responsibility is accepted by The Royal =20
Bank of Scotland plc in this regard and the recipient should carry =20
out such virus and other checks as it considers appropriate. =20
=20
Visit our websites at:
http://www.rbs.co.uk/CBFM
http://www.rbsmarkets.com
=20
*************************************************************************=
***
****
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest =
constraint to
scaling up?! Get this free white paper to understand the real =
constraints &
how to overcome them. SAVE MONEY by scaling-up rather than buying more
servers. http://www.rtosoft.com/Enter.asp?ID=3D147
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
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:
