We use a simple utility with an MSSQL back end. Clients are assigned up to 3 NT print queues ( \\server\share) in the database, which the utility queries at startup. If a match is found for the client name, the utility makes a Win32 API call to map the printer, falling back to CON2PRT to set the default or if the API call fails. It includes other functionality to map queues only if the specified driver exists on the Citrix box but that's the core of it. It's fairly tightly integrated into our environment at the moment but I'd be happy to share it and information with any interested parties. -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of James Hayes Sent: 13 July 2007 03:47 To: thin@xxxxxxxxxxxxx Subject: [THIN] Default Printers & Mandatory Profiles Every since our switch from roaming profiles to mandatory profiles (Provision Networks Meta-Profile), our users have had to set their default printers every morning. Now this may not seem like a big deal but to our users they would rather shove bamboo under their fingernails than do this every morning. We have tried to make it easier for by using DABCC's default printer tool but they still had to set it every time they logged in. We have used Citrix printer policies to automatically set printers but we have too many locations with too many printers to make this effective. What I would like to know is there a way or a tool that will allow our users to set their default printer once and then not have to worry about it again? So that it is retained login after login. Any help would be most appreciated.