Re: Printers not appearing in Active Directory unless I reboot server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks

It would still be nice to find why the AD objects are getting removed.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"Bruce Lautenschlager" <brucel.spamless@xxxxxxxxx> wrote in message
news:OFRcNkr2HHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
Alan -

Thanks for your help. All seems to be well now that I edited that setting.

Bruce

"Bruce Lautenschlager" <brucel.spamless@xxxxxxxxx> wrote in message
news:u92NMAJ1HHA.1344@xxxxxxxxxxxxxxxxxxxxxxx
Alan -

Thanks - I'll change it as soon as I return from vacation next week and
post results.

Bruce

"Alan Morris [MSFT]" <alanmo@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23jZxaPv0HHA.5980@xxxxxxxxxxxxxxxxxxxxxxx
Yes on the print server.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Bruce Lautenschlager" <brucel.spamwho@xxxxxxxxx> wrote in message
news:esrVuKH0HHA.3600@xxxxxxxxxxxxxxxxxxxxxxx
Hey - now we're talking...

Locally for that server, it's Not Configured. I suppose I should change
that
to Enabled with a 30 minute interval?

Should I change that locally or on the domain? Since it's Not
Configured, I
would think locally would work, and I already hate that a handful of my
users are publishing local printers in AD...

Bruce


"Alan Morris [MSFT]" <alanmo@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OaCHM8G0HHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
The spooler checks if the printers are in the AD only at init time or
if
defined by policy. Unpublish and publish should do the trick but
since it
is not set the policy to verify and publish periodically.

gpedit.msc

Computer Configuration
Administrative Templates
Printers
Check Published state


The spooler will verify the printers are published and if not "should"
publish them.

Please let me know if this addresses the issue. I forwarded the info
to
the
group who tests the Service Packs

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Bruce Lautenschlager" <brucel.spamless@xxxxxxxxx> wrote in message
news:uOt86m6zHHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

"Bruce Lautenschlager" <brucel.spamless@xxxxxxxxx> wrote in message
news:e48WBe5zHHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
Bump - any suggestions? I've got my admin creating printers, Event
ID 9
shows up, but no Event ID 36 showing it's published to AD?

If I reboot, it'll publish it in AD. And if I create printers
within a
short time after rebooting, it will publish them very quickly.

It's like it "goes to sleep" after a few days....

Thanks,
Bruce


"Bruce Lautenschlager" <brucel.spamless@xxxxxxxxx> wrote in message
news:%23Q3ObLQtHHA.3640@xxxxxxxxxxxxxxxxxxxxxxx
That was already setup (by default), and you are correct about
looking
for Event ID 36, and there is the problem.

I have System Events showing the printer is created (Event ID 9)
and
long periods of time (30-45 minutes) where no other events are
logged,
but server operation is normal. Once I reboot, I get the Event ID
36
for
the printer that generated the Event ID 9 earlier and the printer
is
published.

Thanks,
Bruce


"Alan Morris [MSFT]" <alanmo@xxxxxxxxxxxxxxxxxxxx> wrote in
message
news:O5V4zsPtHHA.4476@xxxxxxxxxxxxxxxxxxxxxxx
I should not have stated notifications. the correct verbage is

Log spooler information events.

There should be an event 36 when publishing the printers.
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers
no
rights.

"Bruce Lautenschlager" <brucel.spamless@xxxxxxxxx> wrote in
message
news:%23pRYrpDtHHA.2752@xxxxxxxxxxxxxxxxxxxxxxx
Oops - one more thing - when I look at the Sharing tab of each
printer
after creation, the " List in the directory" is already
checked...

Bruce

"Bruce Lautenschlager" <brucel.spamless@xxxxxxxxx> wrote in
message
news:%23nVZehDtHHA.3504@xxxxxxxxxxxxxxxxxxxxxxx
If you're referring to the Group Policy setting "Automatically
publish new printers in Active Directory" that is currently set
to
"Not configured", but I assumed that since I told it during the
creation of the printer that I wanted it shared it would
publish it
in AD (and obviously it does at some point).

Okay, so I enabled "Show informational notifications for local
printers" since "Show information notifications for network
printers"
was already enabled, and also I assume since the printers are
really
viewed as local printers using standard TCP/IP ports - that
should
be
enabled anyway if for nothing else than informational reasons.

But will that do anything besides put more entries in System
Event
Viewer? Or are you saying that I have to restart the Print
Spooler
service in order to publish the printers more effectively in
AD?

Thanks much for the prompt reply,
Bruce

"Alan Morris [MSFT]" <alanmo@xxxxxxxxxxxxxxxxxxxx> wrote in
message
news:O3B60gCtHHA.2004@xxxxxxxxxxxxxxxxxxxxxxx
It's not the reboot, it the spooler restart that is causes the
printers to be published. Enable printer informational
notifications Printers Folder, File, Server Properties,
Advanced

Check the eventlog when you add a new printer. I assume you
have
the policy set to publish printers by default set to enabled.

When the spooler starts, the spooler will perform an ldap
query
for
the printer if it has the published bit set. When the spooler
does
not find it in the AD, the spooler will republish.

I never liked making DC print servers. I think it is not
recommended somewhere.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and
confers
no
rights.

"Bruce Lautenschlager" <brucel.spamless@xxxxxxxxx> wrote in
message
news:OjNiK2AtHHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
Odd problem. Here's my setup:

5 Windows 2000 Server Domain Controllers with AD in native
mode.
Previously, AD printing wasn't an issue, but I only had a few
printers (20 or so), and they were installed on one of the
DCs.
Most file and printing was hosted by NetWare. No replication
problems, no Group Policy problems...life is good. The few AD
printers I had appeared in AD in a minute or so after
creation,
and
worked as designed, for what little use they got.

But now I'm migrating all services to AD, and I created a new
server just for printing. Windows Server 2003 R2 SP2 (joined
domain
as a member server) running an IBM HS20 blade with 4GBs of
RAM
and
a 60GB RAID volume. I love the Print Management console and
was
looking forward to moving 200 or so NetWare printers into
AD -
when
I showed my network admin how great it was, so was she.

Here's the rub. After a few days of running, if I create a
new
printer on that server it won't appear in AD. Previous ones
don't
disappear, it's just that newly installed ones won't appear.
Unless
you reboot the server. The only way a workstation can connect
to
the printer is to do an Add Printer and type in the printer
name.
It connects and can be printed to just fine. But you can't
browse
for it in any way. I can't find it in ADUC, either.

Ditto for changes made to existing printers. They don't
"advertise"
in AD, but if you install the printer on the local
workstation,
the
changes (driver, description, etc.) are evident.

I have REPLMON running watching all my DCs, with no errors
present.
No errors in Event Viewer on the server hosting the printer.
And
like I said, if I reboot the server (not just logout, or
restart
the printer spooling service), the printers populate in AD
just
fine, and people can search for them by browsing the
directory.
Obviously rebooting it once it goes into production isn't
feasible.
And it wasn't necessary when I installed printers on one of
my
Window 2000 DCs.

Any help would be greatly appreciated. I certainly would hope
I
don't have to make the print server a DC...

Thanks,
Bruce Lautenschlager
Bethesda Healthcare System





























.

Relevant Pages

  • Re: Remove printers
    ... Search the Microsoft Knowledge Base here: ... Alan Morris wrote: ... Admin Templates / Printers / Allow pruning of published printers ... Determines whether the domain controller can prune (delete from Active ...
    (microsoft.public.windows.server.scripting)
  • Re: Printers not appearing in Active Directory unless I reboot server
    ... If you are using multiple domains where the print server is on one domain ... Windows Printing Team ... Search the Microsoft Knowledge Base here: ... I am experiencing the same problem: printers does not show up in AD ...
    (microsoft.public.win2000.printing)
  • Re: Network printing - HowTo?
    ... Windows Printing Team ... Search the Microsoft Knowledge Base here: ... Guess I'm wondering if sharing my network printers off of a server ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Connecting to Networked Printer via USB Port
    ... Alan Morris ... Windows Printing Team ... and Ethernet port can be enabled at the same time. ... When HP printers used ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Automatically adding new printers with Print Manager
    ... Alan Morris ... Windows Printing Team ... I have both Sharp copier/printers and a host of HP printers. ... "Failure to initialize" ...
    (microsoft.public.windows.server.general)