I migrated print services from a Win2003-SP1 cluster resource to a
stand-alone server Win2003R2 using the printer migration tool. The process
went well with only a few wrinkles. Print services are up and folks are
printing successfullly.

However, the bulk of PrintQueue objects are still leaves of the two cluster
nodes. These node machines have not been decomissioned yet because I'm
afraid it will destroy the published printer objects. Is there a procedure I
can follow to move the PrintQueue objects to the production server?

Thanks for any suggestions.

--Geoff

With some gentle experimentation, I may have answered my own question. Can
it be as simple as just moving the objects?

I moved one PrintQueue object from the old server object to the new. As a
check, I tried to "Remove from directory" the printer via the Print
Management console. Sure enough, the PrintQueue object was removed from its
new location. I chose "List in directory," and the PrintQueue object
reappeared in the new location.

Who would have thought it would be /that/ easy..

--Geoff



"Geoff Duke" <Geoff.Duke.INVALID@uvm.edu> wrote in message
news:3146315E-2AA1-43C0-99AB-7A430AB033DF@microsoft.com...

This proccess is taken care of by the Printer Pruner Behaviour

All of the PrintQueue objects published by print servers on the same site as
a given domain controller (DC) may be detected as orphaned and deleted, even
though the corresponding printers are available in the domain.

When this occurs, Printer Pruner writes a System event for each PrintQueue
object that is detected as an orphan. This can accumulate rapidly for sites
with large numbers of published print queues. If there are many published
printers on the site, the System event log may become filled with Printer
Pruner events

Printer Pruner detects that a given PrintQueue object is orphaned by
contacting the print server and comparing the Printer object to the Active
Directory PrintQueue object. Because Printer Pruner runs only on DCs, if a
DC is taken off the network, Printer Pruner is unable to contact any print
servers and marks all published printers as being orphaned. By default,
Printer Pruner deletes orphaned printers after checking three times, waiting
eight hours between checks. Therefore, by default, a DC would have to be
removed from the network and run continuously for at least 24 hours before
PrintQueues objects are deleted.

--
Regards
Christoffer Andersson
Executive Consultant - TrueSec
Microsoft MVP - Directory Services

----------------------------------------------------------------
http://www.chrisse.se - Active Directory Resources

"Geoff Duke" <Geoff.Duke.INVALID@uvm.edu> wrote in message
news:FF343E52-388E-4020-9EF1-8FBF3AFC059A@microsoft.com...