[THIN] Re: Default Printers & Mandatory Profiles

  • From: "Angus Macdonald" <Angus.Macdonald@xxxxxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Mon, 16 Jul 2007 08:44:18 +0100

I'll write a quick bit of documentation and post it for download
somewhere. It shouldn't take long.
Angus

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Latham, Mark
Sent: 13 July 2007 19:48
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Default Printers & Mandatory Profiles



I would like further information on this please!

We have a 4.5 farm and Many printers and this would be ideal for our
setup.

 

Thanks!

 

Mark Latham

PC Support Specialist

MIS Department

Mercy Regional Medical Center

1010 Three Springs Blvd.

Durango, CO 81301-5089

Voice    970.764.1352

Fax       970.764-1374

marklatham@xxxxxxxxxxxxxxxx

 

PLEASE NOTE:  (1) This message and any files transmitted with it may
contain federally protected health information, and/or information that
is otherwise privileged, confidential, or proprietary.  If you are not
the intended recipient of this message, you are not permitted to use,
copy, or forward it, in whole or in part.  Please notify the sender of
the error by reply email, disregard the foregoing message, and delete it
immediately.  (2) Although it is a violation of federal law for any
person to intentionally intercept an electronic communication without
consent, email sent through the Internet is potentially subject to
interception by third parties. Please notify the sender of this message
if it was sent unencrypted, and you prefer to receive electronic
communications in an encrypted format.

   <http://cert.startcom.org/> Free SSL Secured By StartCom  

 

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Angus Macdonald
Sent: Friday, July 13, 2007 2:08 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Default Printers & Mandatory Profiles

 

We use a simple utility with an MSSQL back end. Clients are assigned up
to 3 NT print queues ( \\server\share <file:///\\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.  

 

GIF image

Other related posts: