[THIN] Re: Best way to deal with Printers at different locations and travelling exec's
- From: "Craig Cameron" <craig.cameron@xxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 18 Jun 2004 15:18:44 +0100
I like the sound of the second route. All our printer names are consistent with
their locations.
This would simplify the selection of the available printers at the location,
and hopefully solve some of the mapping problems we currently encounter hard
coding the ones required.
Will try this.
Thanks
Craig
-----Original Message-----
From: Braebaum, Neil [mailto:Neil.Braebaum@xxxxxxxxxxxxxxxxx]
Sent: 18 June 2004 15:05
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Best way to deal with Printers at different
locations and travelling exec's
I do printer mappings based on physical location.
In Active Directory, I use the location field for a computer object, to
contain an OU name. This OU contains the printers that are relevant to
the physical location where the PC is (I also wrote a HTA so that our
computer deployers can maintain computer objects, so that computer
objects / accounts can be created / moved to relevant OUs (software
deployment reasons), any group membership(s) the computers needs (again
for software deployment reasons), and set the location field to an
appropriate OU name for the location of the PC).
The login script I wrote uses the PC name, interrogates the computer
object in AD, accesses the location field, opens the OU that this
location field points to, enumerates all the printers in that OU, and
maps to them. Hence, printer mappings based on physical location of PC,
rather than security group mappings.
Well that's how I currently do it ;-)
I also use more simplistic rationale for Winterm only locations, where
the location has a networked printer. I use printer names / queues with
the same name as the Winterm name, and I simply map using this criteria
(within Citrix sessions) when the user logs in.
Neil
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Craig Cameron
> Sent: 18 June 2004 11:58
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Best way to deal with Printers at different
> locations and travelling exec's
>
> Any ideas you guys have would be helpful.
>
> Scenario :
>
> WAN - 9 sites.
>
> Central site has multiple Terminal Servers(2K) to which
> clients at each site connect(RDP).
>
> Printers at each site are on own print servers.
>
> Security settings for printers set by user groups/OU for
> location members.
>
> i.e. Sheffield users can only see Sheffield printers.
>
> Problem : We have a number of Corporate users who travel from
> site to site. Using security groups we can give them either -
> No access to any of the printers, or access to all printers
> at all sites regardless of where they log on (this has
> resulted in confidential documents being printed at another
> site!!) - Users are losers. Nuff said.
>
> Anyway, we have tried to use logon scripts (we can pick out
> the location easily by IP address) to add and remove the
> printers dynamically on location but this tends to be a
> little unreliable.
>
> Question is should I persist with logon scripts as being the
> only way or is there a simple or complicated alternative that
> I've missed???
***********************************************
This e-mail and its attachments are confidential
and are intended for the above named recipient
only. If this has come to you in error, please
notify the sender immediately and delete this
e-mail from your system.
You must take no action based on this, nor must
you copy or disclose it or any part of its contents
to any person or organisation.
Statements and opinions contained in this email may
not necessarily represent those of Littlewoods.
Please note that e-mail communications may be monitored.
The registered office of Littlewoods Limited and its
subsidiaries is 100 Old Hall Street, Liverpool, L70 1AB.
Registered number of Littlewoods Limited is 262152.
************************************************
********************************************************
This weeks sponsor Vizioncore, Inc.
--> vc-iMonitor - Performance Monitoring, Control & Reporting
--> vc-iControl - Desktop & Start Menu Management & Reporting
--> vc-iMapper - Drive, Printer & COM Management & Reporting
http://vizioncore.com/products.html
**********************************************************
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 e-Mail is confidential and is intended for the addressee only. If you are
not the intended recipient, you must not disclose or use any information
contained in it. If you received this e-Mail in error, please contact the
sender immediately and delete the document. This e-Mail is for information
purposes only and is not intended to be relied upon or used as a substitute for
the medical advice of physicians. Specific advice should always be sought on
any individual matter, in particular matters relating to the addressee's health
and any symptoms that may require diagnosis or medical attention.
********************************************************
This weeks sponsor Vizioncore, Inc.
--> vc-iMonitor - Performance Monitoring, Control & Reporting
--> vc-iControl - Desktop & Start Menu Management & Reporting
--> vc-iMapper - Drive, Printer & COM Management & Reporting
http://vizioncore.com/products.html
**********************************************************
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
Other related posts:
