Remove old queues on client when already removed from server

[Guest]

Archived from groups: microsoft.public.windowsnt.print (More info?)

When I delete a printer object from my Windows 2000
computer and stop / start the print spooler, the printer
object comes back. The thing is the print queue that it
is pointing to is no longer on the NT 4.0 server; status
reads "Printer not found on server ...".

I know I can remove it from the registry but I have to
remove about 10 printers on on approximately 200 computers.

New printers were recently setup on the server and the old
ones were removed before the users could delete them from
their machines.

Any ideas?

 

[Guest]

Archived from groups: microsoft.public.windowsnt.print (More info?)

Interesting. After you delete the connection and refresh the UI (printers
folder), does the broken connection still show up? Is it still in the
registry at that time?

What if you use: rundll32 printui,PrintUIEntry /dn /n
\\server-name\printer-name

Does this command remove the connection properly?

--
Felix Maxa
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Korey" <anonymous@discussions.microsoft.com> wrote in message
news:190d301c41c0f$ae5dda50$a501280a@phx.gbl...
> When I delete a printer object from my Windows 2000
> computer and stop / start the print spooler, the printer
> object comes back. The thing is the print queue that it
> is pointing to is no longer on the NT 4.0 server; status
> reads "Printer not found on server ...".
>
> I know I can remove it from the registry but I have to
> remove about 10 printers on on approximately 200 computers.
>
> New printers were recently setup on the server and the old
> ones were removed before the users could delete them from
> their machines.
>
> Any ideas?