Most Administrators are familiar with the Printer Migration tool (PRINTMIG.EXE). This tool has been retired and is no longer supported by Microsoft. The Printer Migration Wizard (PRINTBRMUI.EXE) and the PRINTBRM.EXE command-line tool were introduced to replace it.
Scoping the Issue:
When scoping issues concerning Printer Migration / Backup and Recovery, the following questions are useful in narrowing down the scope of the issue:
Is PrintBRM failing during the backup or restoration of printers, or is there a problem with the printer configuration after restoring printers?
What is the Operating System and Service Pack Level of the source and target server?
Has the print registry key been cleaned up on the source server? (KB 260142)
Have all Kernel Mode Print Drivers (NT4/version-2) been removed from the source server?
Have all LPR Ports been converted to Standard TCP/IP Ports on the source server?
If migrating from x86 to x64, is there a corresponding x64 print driver installed on the source server for every x86 print driver? (NOTE: It practice, it is often quicker to recreate queues manually in cross-architecture printer migration scenarios.)
If the source or destination is a cluster, are you specifying the cluster virtual machine name?
Are there any events that occurred in the event log?
If restoring printers, does the problem occur to more than one target Print Server?
Are you using PrintBRM from a command prompt or GUI? Locally or remotely?
In all instances, collecting either
with the General, Internet and Networking, Business Networks and Server Components diagnostics, or a Performance-oriented MSDT manifest must be done.