Thanks for your response!! Yes, I have successfully setup the printers assigned on clients using the Client Printer Config Utility since that post. However, for that to work, I need to publish that application to the user and they need to manually connect to the printer. That is "too confusing" for the users of the thin clients as (admittedly) many of them are not computer savvy or even literate. I was hoping to make is seamless and transparent so no matter who logs in there, it will always connect/default to the local printer of the client; they click the print button, the report comes out. I spoke in depth with the manufacturer of the client and I'm getting the feeling more and more that this isn't going to work that smoothly. -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Angus Macdonald Sent: Thursday, July 17, 2003 5:10 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: auto creating printer with thin clients Have you assigned printers to clients using the Client Printer Config Utility (or its' equivalent in XP - we're still on MF1.8)? That should create the printer for all users of the terminal but only works for locally attached printers. For remote printers we use a small app that queries an MSSQL database for network printer to client assignments and creates the printers accordingly. You could probably do the same thing witha bit of deft Kix scripting and the Microsoft con2prt utility. -----Original Message----- From: Richard S. Hanzel [mailto:rhanzel@xxxxxxxxxxxxxxxx] Sent: 16 July 2003 19:01 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: auto creating printer with thin clients Greetings: We are using TeleVideo TeleCLIENTS with Citrix MetaFrame XPe FR2. I am having some issues getting the auto creation of printers to work with the thin clients. The application we're using does not offer a printing option, so from the application users can't choose or connect to the printer. When a users logs in, there appears to be no printer attached to the thin client. If I publish the desktop, I can get them to work by manually connecting the printer, but when another user logs on the same client, it will not allow me to "connect" to the printer again unless I publish the desktop (again) and connect manually (again). We do not want to publish desktops for users. Secondly, if the user logs in to any other client (thick or thin) is still defaults to the first thin clients printer, which is not what we'd want if the user is in another location. The ultimate plan is to have the client always attach to it's local printer, regardless of who logs on, or even if multiple users are logged on the same client. Any help/suggestions would be appreciated. Thanks, Rich Hanzel