Okay, this is getting too weird... :) 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 Ron Oglesby Sent: Wednesday, May 12, 2004 9:43 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: high availability Whats even funnier is I have a bottle of that. Bought at Heaven on Seven = in Chicago... Cool. Ron Oglesby Senior Technical Architect Microsoft MVP - Windows Server =20 RapidApp, Chicago Mobile 815 325-7618 Office 312 372-7188 e-mail roglesby@xxxxxxxxxxxx =20 -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On = Behalf Of Steve Greenberg Sent: Wednesday, May 12, 2004 11:05 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: high availability >If it all goes belly up, then I'm changing my name to Fifi and=3D20 =20 >moving to Mexico and buying a very very large sombrero. Brian,=3D20 That is the greatest tag line in email I have ever seen! It reminds of = =3D the hot sauce bottle I saw on a client's desk. It is the hottest sauce ever = =3D made and its name is "Slap my ass and call me Sally!" 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 Lilley, Brian Sent: Wednesday, May 12, 2004 2:35 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: high availability I am keen to pursue a single global farm as it will allow us single =3D = points of administration, and the single farm allows us to provide much =3D simplified global DR and failover through the use zone preferences and = zone =3D failover. On Big Ron's advice, I am looking seriously at the subscriber/publisher replication model with a non-clusterd master and maybe 5 (max) non =3D clustered replication partners! I believe that, if we cannot trust a Data Store for a global solution, = =3D then we cannot trust it for a regional solution which, would be also be catastrophic if we lost. =3D20 If the worst comes to the worst we will automagically rebuild the farm = =3D using the shiney new .net MF class libraries included with the MPS3 SDK. Ok, =3D I just made the bit about the .net MF classes up...but soon.. Citrix touts MPS3 as a real global solution and I am prepared to take = =3D them on. If I can keep the replicated data stores down to the minimum I feel reasonably warm about a single global farm. Again, as I said earlier, = =3D its not so much about high availability of the Data store but more to do =3D = with the integrity of the Data Store. If it all goes belly up, then I'm changing my name to Fifi and moving to Mexico and buying a very very large sombrero. In the meantime, in terms of ensuring integrity of the data store, does anyone have recommendations of using dscheck on a daily basis on perhaps = =3D an off-line replicated copy of the data store database? What are the = best switches for dscheck and I wonder if the version with MPS3.0 includes everything that dsverify can do?? Thanks again for the discussions buys.. just tell me I am doing the =3D = right thing... Brother Brianos -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Steve Greenberg Sent: 12 May 2004 05:33 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: high availability Ron,=3D3D20 I think you are right about the multiple farms. I think Brian's solution = =3D =3D3D is really to have multiple farms managed under a single 3.0 = environment. =3D =3D3D Each farm could have whatever level of SQL redundancy that is = =3D appropriate =3D3D locally with it's own unique farm/data store. In = addition, SQL could be backed =3D3D up as a whole DB either through replication or scheduled =3D backups across the =3D3D WAN to DR and/or multiple other = data centers. How about that Brian, a free worldwide architecture analysis! Long live Internet lists and Open source! 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 Ron Oglesby Sent: Tuesday, May 11, 2004 7:28 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: high availability Very possible. Depending on the number of servers at the sites. If he is talking, 8,10 maybe even 15 or 20 he would be ok across the WAN =3D3D = =3D (assuming 3.0 and good network pipes that aren't already tight) Even = though its =3D =3D3D not really Citrix's recommended situation since for years = now they have had =3D =3D3D IMA start time problems. But if he is talking real farms in the 50, 100, or more server per site. = =3D =3D3D I wouldn't risk it.=3D3D20 Then again With 3.0 I would really being Eyeing multi-farms sharing a license server.=3D3D20 Ron Oglesby Senior Technical Architect Microsoft MVP - Windows Server =3D3D20 RapidApp, Chicago Mobile 815 325-7618 Office 312 372-7188 e-mail roglesby@xxxxxxxxxxxx =3D3D20 -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On = =3D =3D3D Behalf Of Steve Greenberg Sent: Tuesday, May 11, 2004 7:34 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: high availability Sounds to me like this solution would be overly complex with 8 =3D3D3D = =3D3D production sites around the world. What about a larger single SQL =3D = cluster at HQ and then a DR cluster instead (i.e. hit SQL over the wan) ? With = MF =3D 3.0 the =3D3D =3D3D3D IMA traffic should be greatly reduced and Zone no = longer =3D update each =3D3D other unless there is a specific cross zone = request.... Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax=3D3D3D20 steveg@xxxxxxxxxxxxxx -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On = =3D =3D3D =3D3D3D Behalf Of Ron Oglesby Sent: Tuesday, May 11, 2004 9:37 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: high availability There are two ways to do it. Merge replication (not supported by Citrix) = =3D =3D3D =3D3D3D and Transactional replication. The change to a subscriber = (remote =3D SQL =3D3D DB) is really passed to the Publisher (master copy) to verify that there is no conflict with the change. The change is incorporated at the publisher, = =3D =3D3D =3D3D3D then replicated back to the subscriber. It's a really fast = process and =3D =3D3D works pretty well in most cases. It also gives you the "look" = of having =3D =3D3D3D =3D3D writable copies in all locations. If the = publisher is down though =3D you cant change =3D3D =3D3D3D the DB but you can get = into the CMC and look around =3D etc. But you still have to turn one of the DS DBs into a publisher if you are = =3D =3D3D =3D3D3D not going to be able to recover the primary. Ron Oglesby Senior Technical Architect Microsoft MVP - Windows Server =3D3D3D20 RapidApp, Chicago Mobile 815 325-7618 Office 312 372-7188 e-mail roglesby@xxxxxxxxxxxx =3D3D3D20 -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On = =3D =3D3D =3D3D3D Behalf Of Steve Greenberg Sent: Tuesday, May 11, 2004 11:23 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: high availability Seems to me that if you have farms around the world depending on a =3D = =3D3D3D3D =3D3D =3D3D3D single data store that it would been to be fault tolerant = in a =3D true =3D3D =3D3D3D3D =3D3D3D active-active scenario, i.e. all instances = have all the information and =3D3D can accept =3D3D3D3D =3D3D3D reads and writes. = Is this =3D possible with MS SQL??? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax=3D3D3D3D20 steveg@xxxxxxxxxxxxxx -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On = =3D =3D3D =3D3D3D =3D3D3D3D Behalf Of Lilley, Brian Sent: Tuesday, May 11, 2004 9:03 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: high availability also, if you had four marooned sites with read/write replica's of the = =3D =3D3D =3D3D3D =3D3D3D3D Data Store, how would you recover from this in terms = of =3D re-syncing the =3D3D =3D3D3D3D databases? Thanks, -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Lilley, Brian Sent: 11 May 2004 16:49 To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: high availability Big Ron,=3D3D3D3D20 When you say "SQL server", I assume you are referring to SQL based relational database servers in general and not specifically to MS SQL server. Ok, now I may be being totally over-pessimistic about =3D3D3D3D =3D3D3D publisher/subscriber replication here, but do you think it would be = =3D3D feasible to operate =3D3D3D3D something like the following: as part of a controlled maintenance =3D3D3D window, point a server to the master copy = =3D of the =3D3D datastore for the duration of updates =3D3D3D3D to the data = store? =3D =3D3D3D3D20 Are the benefits gained by having a simpler replication topology = =3D3D3D3D outweighed by the amount of effort to provide a maintenance schedule =3D = =3D3D3D =3D3D like above. I =3D3D3D3D am ultra paranoid about a single global = farm =3D replicated =3D3D =3D3D3D between 8+ servers. Would you trust the publisher/subscriber model for 8+ Data Store global single farm? Do you trust DSCHECK? Am I worrying too much? =3D3D3D3D20 thanks in advance, Brian =3D3D3D3D20 -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Ron Oglesby Sent: 11 May 2004 13:46 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: high availability Well. One thing that I can say is any location you have a Citrix server using a SQL server the DB should be read/write/. Now what do I mean by = =3D =3D3D =3D3D3D =3D3D3D3D that? I mean that you should be using a = publisher/subscriber =3D model with transactional replication/immediate updating. This will = allow the =3D3D3D3D =3D3D =3D3D3D changes from servers talking to the = subscriber to be =3D pushed up to the Publisher (master) written into the DS, then replicated to all servers. The trick with this is that any servers online are going to have changes = =3D =3D3D =3D3D3D =3D3D3D3D (of some type, print drivers added, hotfixes = added, etc). =3D And =3D3D these =3D3D3D changes =3D3D3D3D need to update the DS. So = I would not use a =3D straight push =3D3D for any =3D3D3D SQL server =3D3D3D3D with = hot online servers =3D connecting to it. Now =3D3D to use one as a =3D3D3D COLD SQL = server =3D3D3D3D you can do =3D that. But lets assume a =3D3D site loss. You = have =3D3D3D lost 50-75 servers in =3D =3D3D3D3D one site along with the =3D3D = Datastore. Now you have a =3D3D3D shipped Database to =3D =3D3D3D3D another site. And = you are going =3D3D to start installing =3D3D3D servers =3D into that site to = =3D3D3D3D get you up to =3D3D capacity. All the shipping did was =3D =3D3D3D handle = your published apps =3D3D3D3D and licenses =3D3D for the most part, since =3D = the 75 =3D3D3D servers are "gone" but remain =3D3D3D3D as =3D3D ghosts in the = DS and you =3D still have to get =3D3D3D a bunch of servers on line. Get it? Ron Oglesby Senior Technical Architect Microsoft MVP - Windows Server =3D3D3D3D20 RapidApp, Chicago Mobile 815 325-7618 Office 312 372-7188 e-mail roglesby@xxxxxxxxxxxx =3D3D3D3D20 -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On = =3D =3D3D =3D3D3D =3D3D3D3D Behalf Of Lilley, Brian Sent: Tuesday, May 11, 2004 3:10 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: high availability Big Ron, Thanks again for your response. I will be replicating a master read/write copy of the database to =3D = =3D3D3D3D =3D3D =3D3D3D perhaps 5 major regional sites and maybe a couple more at = a push. =3D =3D3D =3D3D3D3D20 Again, back to the DR hot-sites, should I make a data store present = =3D3D =3D =3D3D3D3D =3D3D3D there also? I guess it's a balance between reducing the complexity of the data store replication and having a truly 'marooned' DR site available almost immediately. Personally, from the feelings I got from this list, I would tend =3D = =3D3D3D3D =3D3D =3D3D3D towards keeping the data store replication to a minimum = and =3D allowing the =3D3D DR =3D3D3D3D scenario the Citrix grace period to = restore a data store =3D onto an =3D3D Oracle =3D3D3D box which =3D3D3D3D is = pretty straight forward. When I first asked about data store replication some weeks ago, I =3D = =3D3D3D3D mentioned replication to ten servers globally for a single farm model = =3D =3D3D =3D3D3D (and most of =3D3D3D3D the old timers winced slightly). I am = still =3D looking to =3D3D move forward with a global single farm with data store replication to a =3D =3D3D3D =3D3D reduced number, prob =3D3D3D3D 5 or = so... do you guys still hold the =3D same view? Also, can DSCHECK.EXE be trusted as a signature for health on the IMA = =3D =3D3D =3D3D3D =3D3D3D3D data store? best regards, Brian -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Ron Oglesby Sent: 10 May 2004 20:07 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: high availability Simple answer. No it does not need to be clustered. Complicated = =3D3D3D3D =3D =3D3D =3D3D3D answer... maybe.=3D3D3D3D20 I mean the real trick is how many (and what type) of changes will you = =3D =3D3D =3D3D3D =3D3D3D3D need to make if it is unavailable. In most cases your = answer =3D will be =3D3D none. We =3D3D3D =3D3D3D3D can operate without making = changes to the DS for =3D a couple =3D3D of days. If =3D3D3D that =3D3D3D3D is true = then you don't need the =3D cluster.=3D3D3D3D20 Replication or shipping of the DB/Logs is needed though for any type of = =3D =3D3D =3D3D3D =3D3D3D3D DR. Of course there are drawbacks to this too. I = mean If =3D you use =3D3D =3D3D3D3D transactional replication then when the primary = is gone you cant =3D make changes anyway (until you turn the subscriber into the publisher). So it =3D =3D3D =3D3D3D all depends.=3D3D3D3D20 Hey, I can come out and work on this with ya. It sounds fun and right up = =3D =3D3D =3D3D3D =3D3D3D3D my alley.=3D3D3D3D20 Ron Oglesby Senior Technical Architect Microsoft MVP - Windows Server =3D3D3D3D20 RapidApp, Chicago Mobile 815 325-7618 Office 312 372-7188 e-mail roglesby@xxxxxxxxxxxx =3D3D3D3D20 -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On = =3D =3D3D =3D3D3D =3D3D3D3D Behalf Of Lilley, Brian Sent: Monday, May 10, 2004 8:39 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] high availability Chaps, I need to draw on your experiences again... Does the primary IMA Data Store really need to be clustered, or is this = =3D =3D3D =3D3D3D =3D3D3D3D more complication than it is worth. KISS = principle, etc.? I appreciate that high availability is important, but isn't the = =3D3D3D3D =3D =3D3D =3D3D3D integrity of the database even more important. Without a = Data Store, =3D =3D3D what's the =3D3D3D =3D3D3D3D worse that could happen = during the 96 hours, =3D you can't =3D3D make changes?? If something was seriously wrong the master IMA Data Store cluster node = =3D =3D3D =3D3D3D =3D3D3D3D A, would we want the second cluster to take = over? Is =3D there not a further chance of corrupting data by having this nice-ity?? If the Data Store becomes unavailable, presumably an app server can = =3D3D =3D =3D3D3D3D =3D3D3D still boot from the contents of the LHC? thanks,=3D3D3D3D20 Brian =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D =3D3D3D3D3D=3D3D3D3D3D This message is for the sole use of the intended recipient. If you =3D = =3D3D3D3D received this message in error please delete it and notify us. If this message =3D3D3D3D was misdirected, CSFB does not waive any = confidentiality =3D =3D3D or privilege. CSFB retains and monitors electronic communications = sent =3D =3D3D3D through its network. Instructions transmitted over this system = are not binding =3D3D3D on CSFB until =3D3D3D3D they are confirmed by us. = Message =3D =3D3D transmission is not guaranteed to be =3D3D3D3D secure. =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D =3D3D3D3D3D=3D3D3D3D3D ******************************************************** 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 =3D3D3D3D = =3D =3D3D3D constraint to scaling up?! Get this free white paper to = understand the =3D =3D3D real =3D3D3D3D constraints & how to overcome them. SAVE MONEY = by =3D scaling-up =3D3D rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D3D3D20 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 =3D3D3D3D = =3D =3D3D3D constraint to scaling up?! Get this free white paper to = understand the =3D =3D3D real =3D3D3D3D constraints & how to overcome them. SAVE MONEY = by =3D scaling-up =3D3D rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D3D3D20 set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D =3D3D3D3D3D=3D3D3D3D3D This message is for the sole use of the intended recipient. If you =3D = =3D3D3D3D received this message in error please delete it and notify us. If this message =3D3D3D3D was misdirected, CSFB does not waive any = confidentiality =3D =3D3D or privilege. CSFB retains and monitors electronic communications = sent =3D =3D3D3D through its network. Instructions transmitted over this system = are not binding =3D3D3D on CSFB until =3D3D3D3D they are confirmed by us. = Message =3D =3D3D transmission is not guaranteed to be =3D3D3D3D secure. =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D =3D3D3D3D3D=3D3D3D3D3D ******************************************************** 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 =3D3D3D3D = =3D =3D3D3D constraint to scaling up?! Get this free white paper to = understand the =3D =3D3D real =3D3D3D3D constraints & how to overcome them. SAVE MONEY = by =3D scaling-up =3D3D rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D3D3D20 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 =3D3D3D3D = =3D =3D3D3D constraint to scaling up?! Get this free white paper to = understand the =3D =3D3D real =3D3D3D3D constraints & how to overcome them. SAVE MONEY = by =3D scaling-up =3D3D rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D3D3D20 set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D =3D3D3D3D3D=3D3D3D3D3D This message is for the sole use of the intended recipient. If you =3D = =3D3D3D3D received this message in error please delete it and notify us. If this message =3D3D3D3D was misdirected, CSFB does not waive any = confidentiality =3D =3D3D or privilege. CSFB retains and monitors electronic communications = sent =3D =3D3D3D through its network. Instructions transmitted over this system = are not binding =3D3D3D on CSFB until =3D3D3D3D they are confirmed by us. = Message =3D =3D3D transmission is not guaranteed to be =3D3D3D3D secure. =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D =3D3D3D3D3D=3D3D3D3D3D ******************************************************** 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 =3D3D3D3D = =3D =3D3D3D constraint to scaling up?! Get this free white paper to = understand the =3D =3D3D real =3D3D3D3D constraints & how to overcome them. SAVE MONEY = by =3D scaling-up =3D3D rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D3D3D20 set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D =3D3D3D3D3D=3D3D3D3D3D This message is for the sole use of the intended recipient. If you =3D = =3D3D3D3D received this message in error please delete it and notify us. If this message =3D3D3D3D was misdirected, CSFB does not waive any = confidentiality =3D =3D3D or privilege. CSFB retains and monitors electronic communications = sent =3D =3D3D3D through its network. Instructions transmitted over this system = are not binding =3D3D3D on CSFB until =3D3D3D3D they are confirmed by us. = Message =3D =3D3D transmission is not guaranteed to be =3D3D3D3D secure. =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D= 3D3D=3D3D3D3D3D=3D3D=3D 3D3D3D=3D3D3D3D3D=3D3D3D=3D3D = 3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D=3D3D3D 3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D3D3D=3D3D= 3D3D3D=3D3D3D3D3=3D D=3D3D3D3D3D=3D3D3D3D3D=3D3D3D=3D3D 3D =3D3D3D3D3D =3D3D3D3D3D=3D3D3D3D3D ******************************************************** 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 =3D3D3D3D = =3D =3D3D3D constraint to scaling up?! Get this free white paper to = understand the =3D =3D3D real =3D3D3D3D constraints & how to overcome them. SAVE MONEY = by =3D scaling-up =3D3D rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D3D3D20 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 =3D3D3D = =3D3D constraint to scaling up?! Get this free white paper to understand the = =3D real =3D3D3D constraints & how to overcome them. SAVE MONEY by = scaling-up =3D rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D3D20 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 =3D3D3D = =3D3D constraint to scaling up?! Get this free white paper to understand the = =3D real =3D3D3D constraints & how to overcome them. SAVE MONEY by = scaling-up =3D rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D3D20 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 =3D3D =3D constraint to scaling up?! Get this free white paper to understand the = real =3D3D constraints & how to overcome them. SAVE MONEY by scaling-up = rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D20 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 =3D3D =3D constraint to scaling up?! Get this free white paper to understand the = real =3D3D constraints & how to overcome them. SAVE MONEY by scaling-up = rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=3D3D3D147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=3D3D20 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 =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 =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D =3D3D =3D3D=3D3D This message is for the sole use of the intended recipient. If you =3D received this message in error please delete it and notify us. If this message =3D was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent = through its network. Instructions transmitted over this system are not binding = on CSFB until =3D they are confirmed by us. Message transmission is not guaranteed to be =3D secure. =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D =3D3D =3D3D=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 - Tarantella Secure Global Desktop Tarantella Secure Global Desktop Terminal Server Edition Free Terminal Service Edition software with 2 years maintenance. http://www.tarantella.com/ttba ********************************************************** 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 - Tarantella Secure Global Desktop Tarantella Secure Global Desktop Terminal Server Edition Free Terminal Service Edition software with 2 years maintenance. http://www.tarantella.com/ttba ********************************************************** 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 - Tarantella Secure Global Desktop Tarantella Secure Global Desktop Terminal Server Edition Free Terminal Service Edition software with 2 years maintenance. http://www.tarantella.com/ttba ********************************************************** 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