Printers not appearing in Active Directory unless I reboot server

  • Thread starter Thread starter Bruce Lautenschlager
  • Start date Start date
B

Bruce Lautenschlager

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
 
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.
 
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 said:
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 said:
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
Click to expand...
Click to expand...
 
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 said:
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 said:
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 said:
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
Click to expand...
Click to expand...
Click to expand...
 
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 said:
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 said:
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 said:
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.

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
Click to expand...
Click to expand...
Click to expand...
 
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 said:
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 said:
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 said:
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

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.

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
Click to expand...
Click to expand...
Click to expand...
 
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 said:
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 said:
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 said:
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

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

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.

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
Click to expand...
Click to expand...
Click to expand...
 
I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

Bruce Lautenschlager said:
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 said:
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 said:
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.

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

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

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.

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
Click to expand...
Click to expand...
Click to expand...
 
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 said:
I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

Bruce Lautenschlager said:
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 said:
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


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.

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

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

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.

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
Click to expand...
Click to expand...
Click to expand...
 
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 said:
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 said:
I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

Bruce Lautenschlager said:
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


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


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.

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

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

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.

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
Click to expand...
Click to expand...
Click to expand...
 
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 said:
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 said:
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 said:
I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

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


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


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.

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

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

message
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.

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
Click to expand...
Click to expand...
Click to expand...
 
Alan -

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

Bruce

Alan Morris said:
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 said:
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 said:
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.

I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

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


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


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.

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

message
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

message
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.

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
Click to expand...
Click to expand...
Click to expand...
 
We have also started having this problem with our new servers running Windows 2003 R2 with SP2. Is there perhaps something with R2 or SP2?

Has anyone been able to determine what is actually causing the problem?
 
Alan -

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

Bruce

Bruce Lautenschlager said:
Alan -

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

Bruce

Alan Morris said:
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 said:
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


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.

I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

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


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


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.

message
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

message
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

message
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.

message
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
Click to expand...
Click to expand...
Click to expand...
 
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 said:
Alan -

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

Bruce

Bruce Lautenschlager said:
Alan -

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

Bruce

Alan Morris said:
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.

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


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.

I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

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


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


message
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.

message
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

message
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

message
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.

message
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
Click to expand...
Click to expand...
Click to expand...
 
Hi,
I am experiencing the same problem: printers does not show up in AD
after I check the "publish in AD" checkbox.

Additionally I receive this strange error, which may be somehow
related:

The kerberos client received a KRB_AP_ERR_MODIFIED error from the
server host/cluster-node-01.domain.loc. The target name used was
cluster-print. This indicates that the password used to encrypt the
kerberos service ticket is different than that on the target server.
Commonly, this is due to identically named machine accounts in the
target realm (domain.loc), and the client realm. Please contact your
system administrator.


Did not try to enable the GP setting described above. May be will try
later today.

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.




Alan -
Click to expand...
Thanks for your help. All seems to be well now that I edited that setting.
Bruce
Click to expand...

Bruce Lautenschlager said:
Alan -
Thanks - I'll change it as soon as I return from vacation next week and
post results.
Bruce
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.
Hey - now we're talking...
Locally for that server, it'sNotConfigured. I suppose I should change
that
to Enabled with a 30 minute interval?
Should I change that locally or on the domain? Since it'sNot
Configured, I
would think locally would work, and I already hate that a handful ofmy
users are publishing local printers in AD...
Bruce
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
isnotset 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 ifnot"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.
I should add, restarting the spooler servicedoesthe same thing as
rebooting...
Any help appreciated.
Bump - any suggestions? I've got my admin creating printers, Event
ID 9
showsup, 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
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 theprinteris 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
theprinterthat generated the Event ID 9 earlier and theprinter
is
published.
Thanks,
Bruce
message
I shouldnothave 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.
message
Oops - one more thing - when I look at the Sharing tab of each
printer
after creation, the " List in thedirectory" is already
checked...
Bruce
message
If you're referring to the Group Policy setting "Automatically
publish new printers inActiveDirectory" that is currently set
to
"Notconfigured", but I assumed that since I told it during the
creation of theprinterthat I wanted it shared it would
publish it
in AD (and obviously itdoesat some point).
Okay, so I enabled "Showinformational notifications for local
printers" since "Showinformation 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
message
It'snotthe reboot, it the spooler restart that is causes the
printers to be published. Enableprinterinformational
notifications Printers Folder, File, Server Properties,
Advanced
Check the eventlog when you add a newprinter. 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
theprinterif it has the published bit set. When the spooler
does
notfind it in the AD, the spooler will republish.
I never liked making DC print servers. I think it isnot
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.
message
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 fewAD
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
printeron 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
theprinteris to do an AddPrinterand type in theprinter
name.
It connects and can be printed to just
Click to expand...
Click to expand...

...

skaityti daugiau »- Sl pti cituojam tekst -

- Rodyti cituojam tekst -
Click to expand...
 
If you are using multiple domains where the print server is on one domain
and the clients are on another. Authentication happens on the primary
domain first. Check if there are duplicate machine names on the other
domain.

--
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.

Hi,
I am experiencing the same problem: printers does not show up in AD
after I check the "publish in AD" checkbox.

Additionally I receive this strange error, which may be somehow
related:

The kerberos client received a KRB_AP_ERR_MODIFIED error from the
server host/cluster-node-01.domain.loc. The target name used was
cluster-print. This indicates that the password used to encrypt the
kerberos service ticket is different than that on the target server.
Commonly, this is due to identically named machine accounts in the
target realm (domain.loc), and the client realm. Please contact your
system administrator.


Did not try to enable the GP setting described above. May be will try
later today.

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.




Alan -
Click to expand...
Thanks for your help. All seems to be well now that I edited that
setting.
Bruce
Click to expand...

Bruce Lautenschlager said:
Alan -
Thanks - I'll change it as soon as I return from vacation next week and
post results.
Bruce
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.
Hey - now we're talking...
Locally for that server, it'sNotConfigured. I suppose I should change
that
to Enabled with a 30 minute interval?
Should I change that locally or on the domain? Since it'sNot
Configured, I
would think locally would work, and I already hate that a handful of
my
users are publishing local printers in AD...
Bruce
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
isnotset 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 ifnot"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.
I should add, restarting the spooler servicedoesthe same thing as
rebooting...
Any help appreciated.
message
Bump - any suggestions? I've got my admin creating printers,
Event
ID 9
showsup, 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
message
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 theprinteris 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
theprinterthat generated the Event ID 9 earlier and theprinter
is
published.
Thanks,
Bruce
message
I shouldnothave 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.
message
Oops - one more thing - when I look at the Sharing tab of each
printer
after creation, the " List in thedirectory" is already
checked...
Bruce
message
If you're referring to the Group Policy setting
"Automatically
publish new printers inActiveDirectory" that is currently set
to
"Notconfigured", but I assumed that since I told it during
the
creation of theprinterthat I wanted it shared it would
publish it
in AD (and obviously itdoesat some point).
Okay, so I enabled "Showinformational notifications for local
printers" since "Showinformation 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
message
It'snotthe reboot, it the spooler restart that is causes the
printers to be published. Enableprinterinformational
notifications Printers Folder, File, Server Properties,
Advanced
Check the eventlog when you add a newprinter. 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
theprinterif it has the published bit set. When the spooler
does
notfind it in the AD, the spooler will republish.
I never liked making DC print servers. I think it isnot
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.
message
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
printeron 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
theprinteris to do an AddPrinterand type in theprinter
name.
It connects and can be printed to just
Click to expand...
Click to expand...

...

skaityti daugiau »- Sl pti cituojam tekst -

- Rodyti cituojam tekst -
Click to expand...
 
I don't follow you on this one - they aren't getting removed, technically,
since they weren't getting published to begin with, correct?

FWIW, still working normally now, thanks to you.

Bruce

Alan Morris said:
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 said:
Alan -

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

Bruce

Bruce Lautenschlager said:
Alan -

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

Bruce

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.

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


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.

I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

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


message
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


message
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.

message
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

message
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

message
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.

message
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
Click to expand...
Click to expand...
Click to expand...
 
Hi, Alan,

I have a printer server that is exhibiting the same behavior. I have set the
local policy for "Check Published State" to one hour. Once I rebooted the
system, numerous printqueue objects were created for the printers that were
missing.

It has now been several weeks, and I just noted that a new printer I created
is not appearing in Active Directory. I've used dsquery * to locate all the
printqueue objects that are children of the printer, and no object exists for
the printer I created.

When I select "Remove from Directory" and "List in Directory" for this
printer, I get no error events, only EventID 9 (object was set) events. I'm
thinking that the spooler isn't creating the objects in the first place,
rather than that they are created and then removed.

Any suggestions for resolving this (other than cycle the spooler service
routinely)?

--Geoff

Alan Morris said:
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 said:
Alan -

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

Bruce

Bruce Lautenschlager said:
Alan -

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

Bruce

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.

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


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.

I should add, restarting the spooler service does the same thing as
rebooting...

Any help appreciated.

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


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


message
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.

message
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

message
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

message
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.

message
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
Click to expand...
Click to expand...
Click to expand...
 
Back
Top