[THIN] Re: SV: Selecting default printer
- From: Spriggs Jon <Jon.Spriggs@xxxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Thu, 16 Dec 2004 15:04:11 -0000
How easy is it to move the OU of a device or user? Do you have any examples
of VBScript or JavaScript that do this?
Jon Spriggs
--
The presence of a "Fujitsu" address does not imply or assume that Fujitsu
Services, Fujitsu or any other company containing the Fujitsu name uses or
endorses this product. This email is purely a personal opinion.
-----Original Message-----
From: Braebaum, Neil [mailto:Neil.Braebaum@xxxxxxxxxxxxxxxxx]
Sent: 16 December 2004 14:53
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: SV: Selecting default printer
Well the reason why I do things the way I do thing being that Active
Directory, or any directory for that matter, is supposed to be the
*repository* for this information - that's *why* you have a directory.
Your rejection of the concept is based around the idea that printers (or
other objects) must be grouped by the same rationale as users or computers -
that's not what I do. In some instances, it may be appropriate - depending
on what your rationale is for grouping objects in AD, but where I am,
computers are grouped for particular reasons, users are grouped separately
for other reasons, and the same for printers.
Secondly, I wanted to get away from the tired old cliché of having countless
groups and printers in login scripts as well as in the domain database.
And seventeenthly, I wanted to have a rationale whereby printer mapping was
achieved by means of physical location of the computer - as opposed to
either computer, or more likely - user group membership.
And lastly - whatever you use, is only as good as the information being
maintained. For my scenario (using the location field of the computer
object, to point to an OU where the printers for that location are grouped),
I wrote a HTA / GUI utility for the PC maintainers, here, so that new (or
rebuilt) PCs can be configured for all things that are pertinent ie OU
location for application deployment, group membership for exceptions to
application deployment, and location field contents - to point to OU
groupings of printers, for printer mappings.
Neil
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Matthew Shrewsbury
> Sent: 16 December 2004 14:25
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: SV: Selecting default printer
>
> Personally I don't think mapping printers by OU is a great
> idea. It would all depend on your OU structure but in our
> case I often have many users in an OU and they often only
> want maybe one or two printers.
>
> I map printers by group. Anyone in the P-HPLJ5SI gets that
> printer. Group has location and printer description. Add as
> many P- groups as you want to get all your printers...if you
> remote them from the P- groups next logon removes the printer.
>
> It does not set the default printer the user has to do
> that...or go with the default which sets the first printer
> mapped as the default printer. Once the user sets the default
> printer it stays set.
>
> I wrote this script in WSH JavaScript.
>
> Matthew Shrewsbury, MCSE+Internet MCSE 2000 CCA
> Network Administrator
>
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Braebaum, Neil
> Sent: Thursday, December 16, 2004 9:04 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: SV: Selecting default printer
>
> Well firstly (accepting that a DC isn't the ideal choice for
> print serving ;-)), presumably your print server publishes
> it's printers in AD? They are normally then grouped under the
> computers container object.
>
> You can then move / place them to wherever you would prefer
> them to reside in AD. They could be grouped with users
> (presumably OUs) or computers (again presumably OUs) or
> arbitrarily as in my example - when the computer object
> location field points to the printer objects that are appropriate.
>
> Neil
>
> > -----Original Message-----
> > From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]
> > On Behalf Of Spriggs Jon
> > Sent: 16 December 2004 13:50
> > To: thin@xxxxxxxxxxxxx
> > Subject: [THIN] Re: SV: Selecting default printer
> >
> >
> > OK, I've got a site with three different departments (Site LON,
> > Dept. A B and C) and a site with two different departments (Site
> > EDI, Dept. A and C). LON/A has 25 staff and two printers, LON/B has
> > 5 staff and 1 printer and LON/C has 10 staff and 1 printer. EDI/A
> > has 10 staff and 3 printers, EDI/C has 5 staff and uses EDI/A's
> > printer. Each team has a manager, EDI/A also comprises of the
> > helpdesk called EDI/A/Helpdesk, who want to use just 1 of the 3
> > printers.
> >
> > Currently, our login script checks the OU of the staff
> > (company.local/member servers/terminal
> > servers/users/site/dept) and the DC they've authenticated
> > against to check which site they're at. Once it's got that,
> > it checks that against a series of text files to see which
> > printers they should be mapping against. If there's already a
> > printer mapped as default (checks Registry Key
> > HKCU\Software\Microsoft\Windows
> > NT\CurrentVersion\Windows\DefChanged), it removes all the
> > printers and maps all those that OU should have access to. If
> > the default printer that was there before is not one of the
> > printers that OU uses, it prompts for a new default printer
> > from the text file.
> >
> > So, how do you tidy that up, so that it's a bit less unwieldy
> > (currently 430 lines of code)? All our printers are created on the
> > local W2K DC (LONDC01 or EDIDC01), and as a result, it doesn't
> > appear we can also add them in the AD, as they are already created
> > on the DC.
> >
> > Any advice or guidance would be *really* helpful...
> >
> > Thanks,
> >
> > Jon Spriggs
***********************************************
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 SeamlessPlanet.com Domain Names
Register your .com domain name for as low as $7.85
One of the lowest prices on the web! Part of The Kenzig Group.
http://www.seamlessplanet.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm ThinWiki community - Awesome SBC Search
Capabilities! http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
********************************************************
This Weeks Sponsor SeamlessPlanet.com Domain Names
Register your .com domain name for as low as $7.85
One of the lowest prices on the web! Part of The Kenzig Group.
http://www.seamlessplanet.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Awesome SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
