Gale, You are correct about Meditech using the client connecting versus the server. In the process Meditech takes the client name from the RDP session and this is what it uses. If you launch Meditech on the Terminal Server from an RDP session right click the top window bar and do About and you should see the client name. If not there is a DTS that needs to be dropped so that Meditech picks up this name.
As far as printing the best thing that I found is to use your Microsoft Windows Print server and script the clients with the correct printers. To do this you need to create your laptops/thin clients with public login accounts or if you have your individual nurses log in put them into a group. For example: laptop1 is assigned to 4 east. The login for the account is 4eastlaptop1. Put this into a Windows Group called 4east. Create a log in script on the terminal server using a couple of Microsoft tools Con2prt.exe and ifmember.exe (Copy them into the system32 directory under windows). When the user logs in ifmember.exe will look to see if they are in the 4east group and assign it \\printserver\4east printer and set it as default. See script example below: ifmember.exe "domain\4east" if not errorlevel 1 goto skip4east con2prt.exe /cd \\printserver\4east :skip4east Again this will set the 4east printer as the default printer for this user. One caveat that I have seen with thin clients and the client/location dictionary is to make sure the hostname on the thin clients is consistent with your client dictionary. If they are uppercase in MT client dictionary make sure they are uppercase on the thin client. I have seen issues especially with OE and STOs not printing to HERE if this is how you have them setup. Hope this helps. John John Stone Technical Services Manager Fairmont General Hospital 304-367-7389 [EMAIL PROTECTED] "Is there anything else I can do for you?" -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Freeman, Gale Sent: Friday, October 20, 2006 11:07 AM To: Derrick Goode; [email protected] Subject: RE: [MEDITECH-L] (no subject) We havent started restricting our nurses by location yet , but we will be. We just started using the Thin clients also . Its my understanding the printing process looks at the client your using for the printers, not the Server. If you restrict by location , you shouldn't have a problem if your client being used is in the Location dictionary in the same location as the patient being worked on. If the patient is on 4 East, For example, but the laptop being used is in the dictionary as being on 3 East, then the system wont let the nurse in if she/he is restricted by location. It basically means only let the user See the patients that are on same location as this computer. If the client is in 4 East location dictionary and the patient is there too, then there wont be an issue. We have problems here with mobile laptops that staff move to different floors , but don't tell the IS Dept, and I am worried that it will be a problem because the dictionary wont be updated . The nurses will get frustrated because they don't have any idea that the computer isnt set up for That location. Let us know how it works out for you. Galey -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derrick Goode Sent: Wednesday, October 18, 2006 11:40 AM To: [email protected] Subject: [MEDITECH-L] (no subject) We would like to use Thin Clients for our NUR applications which will be connecting via Citrix servers. When you restrict nurses by location how do you control Printing for (HERE) type of Reqs for both NUR and OE? How do you control access for the nurses since all PC are managed in the Location dictionary ? Best way to go about this? Thanks, Derrick Goode Elk Regional Health Center 763 Johnsonburg Rd. St.Marys PA 15857 F - 814-788-8076 W- 814-788-8661 All messages should be posted in plain text. HTML will be converted to attachments. The meditech-l web site is MTUsers.com _______________________________________________ meditech-l mailing list [email protected] http://mtusers.com/mailman/listinfo/meditech-l ====================================== All messages should be posted in plain text. HTML will be converted to attachments. The meditech-l web site is MTUsers.com ______________________________________ meditech-l mailing list [email protected] http://mtusers.com/mailman/listinfo/meditech-l ====================================== All messages should be posted in plain text. HTML will be converted to attachments. The meditech-l web site is MTUsers.com ______________________________________ meditech-l mailing list [email protected] http://mtusers.com/mailman/listinfo/meditech-l
