We have all different setups and configs for the different clients that we have connecting to our farm. First, make sure if you are running Meditech Magic not Meditech Client/Server, that you are using the Meditech Remote Workstation version 3.24a client and not just 3.24. Version 3.24 will not pass through your client name in Meditech correctly on a terminal server if it is defined in Meditech already. The big thing to remember when talking about how Meditech "see's" the device name for any client is that if you define that client device name in Meditech or if it is already defined, than regardless of how that client gets to meditech on the Citrix server (full published desktop/Meditech as a single published app/NFuse/etc...) the device name will show as it is defined in meditech (ie radpc125.1). So generally when setting up Thin Clients on our network we will define the device name in Meditech so it would show up as it's own device name. However, we also have a large remote user community comprised of mostly different physician offices that connect via NFuse and SSL. With these types of clients, there is no possible way to have all their device names defined in meditech obviously. So when these users connect they will grab a servername.1 or servername.2 like you had mentioned in your last email. To make this work, when you first build your citrix server(s) install meditech and then immediately define the server in meditech with a large number 50,100, or however many devices available that you think you will need (we do 50) Also in general the meditech executable itself (t.exe) has not proved to be very leaky memory-wise while running on a Citrix server. However, when you tie in Windows-based programs that run as a counterpart to meditech, or are actually launched from within meditech, these apps will need to sit on your citrix servers as well, and many of these are questionable. I know the one application that we use for Patient Care Documentation has proven to be (thanks to TScale) a very leaky app that needs much virtual memory optimization, so watch out for those type of applications. Let me know if you have any other specific questions... Best of luck to you! /jL -----Original Message----- From: Taylor, George [mailto:gtaylor@xxxxxxxx] Sent: Tuesday, March 23, 2004 4:17 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Citrix and Meditech Right now we're at the beginning stages of the project, I have a test farm up and running on a couple old HP servers, but do have a Blade Center on order for the first phase of the production farm. How did you deploy to the thin clients and PCs that are in-house, PNA, ICA Web, JAVA? What is the "look and feel" for the users, web based, icons on the desktop, full remote desktop? On the thin clients what does Meditech consider it's terminal name? What about home users coming in VIA Nfuse, do they get a term name of <servername>.1, <servername>.2, etc..? Like I said, I'm at the start of it and could certainly use and details you guys want to offer!! Thanks, George =20 -----Original Message----- From: Luchette, Jon [mailto:JLuchette@xxxxxxxxxxxxxxx]=20 Sent: Tuesday, March 23, 2004 12:08 PM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Citrix and Meditech Yup, we have been running Meditech Magic on Citrix MF XP for around 2 1/2 years now. We have 6 Citrix servers, around 250 thin clients, and two Nfuse servers with CSG utilizing a hardware load balancer from F5. =20 -----Original Message----- From: Taylor, George [mailto:gtaylor@xxxxxxxx] Sent: Tuesday, March 23, 2004 12:01 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Citrix and Meditech Is there anyone out there in a Hospital that is running Meditech or Cerner via Citrix? George ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** 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 Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** 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 Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** 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 Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** 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