[gptalk] Re: ad printer publishing

  • From: "Graham Turner" <gturner@xxxxxxxxxxxxxxx>
  • To: gptalk@xxxxxxxxxxxxx
  • Date: Mon, 19 Feb 2007 08:37:21 -0000 (GMT)

Tony, excellent !

Thanks again 4 help

NZ for the cricket world cup after being AUS ?? - a double cos looks like they 
will
win the Rugby 2 !


> Hi Graham
>
> To answer your questions.
>
> 1. The print server uses DNS SRV records to locate an in-site DC to
> publish the print queue.
> 2. The pruner works by compiling a list of all printQueue objects in AD.
> It then works through the list and determines (using DNS) those that are
> in-site. It then tries to contact each in-site print server to check the
> queue is available.  If it isn't, the pruner removes the printQueue
> object from AD.
>
> Print servers in sites with no DCs will be taken care of by DC auto site
> coverage.  In other words, there will be a DC (or DCs) responsible for
> the site.
>
> The behaviour is slightly strange when the pruner can't find the print
> server in DNS.  In this case the pruner simply assumes the server is
> in-site and tries to contact the print server to check the print queue
> availability.  In other words, it's free-for-all and any DC could
> potentially prune the printQueue object.  At least this was the
> behaviour in Windows 2000 AD - not sure about 2003.
>
> Cheers
> Tony
> -----Original Message-----
> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
> On Behalf Of Graham Turner
> Sent: Monday, 19 February 2007 9:04 a.m.
> To: gptalk@xxxxxxxxxxxxx
> Subject: [gptalk] Re: ad printer publishing
>
> Tony, sorry 4 delay in this thread
>
> have just a couple more questions on this if that is ok
>
> 1. the printad.doc implies that the DC chosen as target for publish is
> 'random DC in the print (server's) domain - is this process not site
> aware say as logon server discovery. ?
>
> 2. read somewhere that the pruning process only works for print servers
> in same site as the DC - is this correct ?
>
> would i read this as the DC only removing printer objects for printers
> in its own site ?
>
> if this is the case, how is the scenario of having sites in which there
> are print servers & no DC's managed
>
> do we fall back to mechanisms such as site coverage as in the login
> server case ?
>
> GT
>
>
>> Hi Graham
>>
>> The "Allow printers to be published"  setting should be applied to the
>
>> OUs containing member computers.  When enabled or not configured the
>> "List in directory" option is visible.  When disabled it is not.  You
>> would only apply it to the Domain Controllers OU if you wanted to
>> control this option for print queues on DCs.  The setting takes
>> priority over the setting "Automatically publish new printers in
>> Active Directory".
>>
>> The pruning behaviour runs as a thread within the spooler service on
>> DCs.  In other words if your spooler service is not running on the DC
>> you won't see any pruning. It's not well documented. :-(
>>
>> For more information have a look at the following resources:
>>
>> http://www.microsoft.com/windows2000/docs/printad.doc
>>
>> http://support.microsoft.com/?kbid=234270
>>
>> http://www.windowsitpro.com/Windows/Articles/ArticleID/41104/pg/1/1.ht
>> ml
>>
>> Tony
>>
>> -----Original Message-----
>> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
>> On Behalf Of Graham Turner
>> Sent: Tuesday, 06 February 2007 3:49 a.m.
>> To: gptalk@xxxxxxxxxxxxx
>> Subject: [gptalk] ad printer publishing
>>
>> i am possibly in danger of slipping OT with this, as not stricty GP
>> processing but anyways ,,
>>
>> seems there are a whole load of policies that relate to the publishing
>
>> / pruning / searching of printer objects that are written to AD
>>
>> docs seem a little unclear as to what types of Windows host (DC,
>> member server, end user workstation) each one of these policies apply
>>
>> it would seem to be further complicated by the fact DC's can be print
>> servers too !
>>
>> i suppose you could get away with defining the policies at domain
>> level, but you should be able to apply policies at the OU level which
>> contains each type of host ??
>>
>> before we go into the specifics of some of these policies i have this
>> table as to what type of host processes each policy;
>>
>> allow printers to be published - DC
>> automatically publish new printers in AD - print server (member
>> server) allow pruning - DC printer browsing - ??
>> prune printers .. - DC
>> pruning interval - DC
>> pruning retry - DC
>> pruning priority - DC
>> check published state - print server (member)
>>
>> QU2  - are the DC policies dependent on the spooler service running on
>
>> the DC even though it doesn't have any printers ??
>>
>> Help as alwways gladly received
>>
>> G
>>
>> ***********************
>> You can unsubscribe from gptalk by sending email to
>> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
>> OR by logging into the freelists.org Web interface. Archives for the
>> list are available at http://www.freelists.org/archives/gptalk/
>> ************************
>>
>>
>> No Viruses were detected in this message.
>> HealthIntelligence eMail Filter Service
>>
>>
>>
>> This email or attachment(s) may contain confidential or legally
>> privileged information intended for the sole use of the addressee(s).
>> Any use, redistribution, disclosure, or reproduction of this message,
>> except as intended, is prohibited. If you received this email in
>> error, please notify the sender and remove all copies of the message,
>> including any attachments. Any views or opinions expressed in this
>> email (unless otherwise stated) may not represent those of
> HealthIntelligence (HIQ Ltd).
>>
>> http://www.healthintelligence.org.nz
>>
>> (1H_S1)
>>
>> No Viruses were detected in this message.
>> HealthIntelligence eMail Filter Service
>> ***********************
>> You can unsubscribe from gptalk by sending email to
>> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
>> OR by logging into the freelists.org Web interface. Archives for the
>> list are available at http://www.freelists.org/archives/gptalk/
>> ************************
>>
>
>
> ***********************
> You can unsubscribe from gptalk by sending email to
> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR
> by logging into the freelists.org Web interface. Archives for the list
> are available at http://www.freelists.org/archives/gptalk/
> ************************
>
>
> No Viruses were detected in this message.
> HealthIntelligence eMail Filter Service
>
>
> No Viruses were detected in this message.
> HealthIntelligence eMail Filter Service
> ***********************
> You can unsubscribe from gptalk by sending email to 
> gptalk-request@xxxxxxxxxxxxx
> with 'unsubscribe' in the Subject field OR by logging into the freelists.org 
> Web
> interface. Archives for the list are available at
> http://www.freelists.org/archives/gptalk/
> ************************
>


***********************
You can unsubscribe from gptalk by sending email to 
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by 
logging into the freelists.org Web interface. Archives for the list are 
available at http://www.freelists.org/archives/gptalk/
************************

Other related posts: