Re: Adding Printers to AD

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: ptwilliams (ptw2001_at_hotmail.com)
Date: 01/25/05


Date: Tue, 25 Jan 2005 19:03:48 -0000


> a.. The more objects placed in Active Directory the larger the database
> grows, which can cause greater chance of corruption

You'd need an enormous database to ever need to worry about this. I'd say
this is inaccurate to say the least.

> b.. The larger the database the longer it takes for AD replication to
> complete. When you figure in some sites are on low bandwidth this could
> cause slow connectivity issues for the site during the replication
> process.

Again, unless you have an enormous AD database this isn't really an issue.
Also, you'll need to define slow links. The AD is quite efficient at
compressing and replicating over WAN links. I've run an AD over 64K lines
without any issues.

> c.. From an administrative standpoint this would be a huge task to keep up
> with due to the amount of printer changes/moves that take place

Not really. You simply ensure that the printer is un-published prior to
moving. When it's moved, you then publish it again. If you move the
computer again, there's no issue. This is only an issue if you move
printers between computers. Is that that likely?

> d.. We immediately need to change information regarding every printer,
> using the AD sites and services tool, to update the location of all
> printers for the entire network. This would also be an ongoing
> administrative process anytime a printer is changed be it deletion, name
> change, or physical move.

I don't understand this point. What are you saying? Yes, modifying the
location attribute is a pain as it's set at the printer (the software
interface on the computer that represents the physical device -in NT5.x
speak). If a printer were deleted, moved out-of-scope, etc. and the object
still remains in the AD it will be pruned after three attempts at contact.

> e.. The printers that are currently listed in AD are the ones that were
> published before this group policy was put in place. I am in the process
> of checking our Region to see if we need to remove the existing published
> printers.

What's the issue here? ;-) It's easy enough to remove these if you need
to...

-- 
Paul Williams
http://www.msresource.net/
http://forums.msresource.net/
"DLG" <deanl144@hotmail.com.nospam> wrote in message 
news:eQkn14wAFHA.3708@TK2MSFTNGP14.phx.gbl...
I asked my IS staff to add our printers to AD and they have told me the
following:
 A group policy was put in place some time ago for not publishing printers
to AD.  This is because of many technical reasons:
a..
  a.. The more objects placed in Active Directory the larger the database
grows, which can cause greater chance of corruption
  b.. The larger the database the longer it takes for AD replication to
complete.  When you figure in some sites are on low bandwidth this could
cause slow connectivity issues for the site during the replication process.
  c.. From an administrative standpoint this would be a huge task to keep up
with due to the amount of printer changes/moves that take place
  d.. We immediately need to change information regarding every printer,
using the AD sites and services tool, to update the location of all printers
for the entire network.  This would also be an ongoing administrative
process anytime a printer is changed be it deletion, name change, or
physical move.
  e.. The printers that are currently listed in AD are the ones that were
published before this group policy was put in place.  I am in the process of
checking our Region to see if we need to remove the existing published
printers.
I am skeptical of these arguments. Could someone confirm or rebut the above
the statement or point me in the direction of some documents that could
provide me with some additional perspective.
Tia
Dean


Relevant Pages

  • Re: AD Replication
    ... Source NTDS Replication ... A database error occurred while applying replicated changes ... the Active Directory database then retry the operation. ... On the source domain controller, move the object to have a ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Replication
    ... Source NTDS Replication ... A database error occurred while applying replicated changes ... the Active Directory database then retry the operation. ... On the source domain controller, move the object to have a ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID 404 Errors
    ... inherited this server from the previous IT staff here and it is riddled ... Active Directory is functioning properly and add or update this domain ... Event Source: NTDS Replication ... The replication operation encountered a database error. ...
    (microsoft.public.windows.server.active_directory)
  • Re: publishing more than one database
    ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ... Recently we have a need to publish the second database on the same SQL ... for publishing a second or third etc is no difference than publishing the ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL Replication
    ... Hi Bryan, ... This will remove the database from being a merge or transactional publishing ... > replication. ...
    (microsoft.public.sqlserver.server)