Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Print Migrator did not restore all queues (2k-2k3)

Status
Not open for further replies.

XRJoe

MIS
Feb 27, 2004
76
US
Migrating from Windows 2000 cluster to Windows 2003 cluster. The backup of the 2000 cluster completed and when I look through the pm.log it says "1217 print queues enumerated" & "89 printer drivers enumerated" which is correct. However when I restore to the 2003 Cluster I only have 462 print queues and 25 print drivers.

When I look through the pm.log on the 2003 cluster the first thing I notice is only "25 printer driver enumerated". Further searching I also find:

2007:12:04 16:36:58 Copying W32X86 version 2 files to target ...
2007:12:04 16:36:58 Done.
2007:12:04 16:36:58 Copying W32X86 version 3 files to target ...
2007:12:04 16:36:59 Done.

Followed by a long list of:
Driver "DriverName": the file FileName is missing from the CAB
Bad Version 3 driver: DriverName
winerror.h - 2

And further down we find that only 462 print queues were enumerated and surprise surprise it is missing all of the print queues that used the failed drivers. Anyone have some experience with this problem?

When I look through the .CAB I do find the files that are listed as "missing". The backup pm.log looks complete so I do not think the problem lies with the backup. I have unsigned drivers setting on silently succeed for the 2003 servers. And here is a list of the drivers/printer queues that did not complete...

DRIVERS/QUEUES THAT DID NOT MIGRATE:
Any (37) Canons regardless of model
hp business inkjet 1100
hp business inkjet 2250
hp business inkjet 2600
Any (21) color laserjets regardless of model
deskjet 930c
deskjet 970
deskjet 9800
laserjet 1200
laserjet 1300
laserjet 1320
laserjet 2100
laserjet 2200
laserjet 2300
laserjet 3015
laserjet 4100
laserjet 4200L PCL 5e
laserjet 4250 (PCL and PS)
laserjet 4350
laserjet 5100
laserjet 8000
laserjet 8100
laserjet 9050
laserjet III
laserjet P2015
All (3) Konica Minolta
All (2) Lanier
Lexmark 2380
Lexmark Optra
Lexmark T630
Lexmark T632
Lexmark T644
Oki ML 320 Elite
Printronix P5000
All (5) Ricohs
All (4) Xerox Phaser 4500DT

I really appreciate any info you could throw my way regarding this.
 
When I see that, it's usually one of a couple of things.

The driver isn't supported in 2003, or
The driver isn't signed (if you install it manually, you get the driver signing prompt).

In either case, it won't install the printer.

Pat Richard
Microsoft Exchange MVP
 
The list seems fairly random when you compare it to the list of printers that did get installed. We are using mostly postscript drivers (don't know if that matters) but I will look into both of those suggestions and report with any findings.
 
Anyone else have any ideas? I am burnt out here.

The drivers that did not migrate are signed and are supported under 2003 as far as I can tell. I am able to install the printers manually with no errors or warnings (most of the drivers are already packaged with 2003 i.e. Laserjet 4100 PS).

I copied over the driver files manually to the shared drive space, E:\PrinterDrivers, and still the same results.
 
Anyone?

I have to manually install 760 printers if I cannot get this to work...
 
XRJoe,
I had the same problem and find out a workaround. You should try installing the drivers manually first, and then restore the CAB file.
The error message still will be logged, but the queue will be created correctly.

Regards

Martin

 
you can just copy the registry keys to create the printers from the cluster key.

You would be doing yourself a big favour to update all the drivers for 2003 instead of migrating as you will strike a lot of problems down the track. I've done a fair bit of migration from nt4/2000 to 2003 and print issues are always a ton of drama if you try to migrate them. Easier to have a nice clean set of drivers.

Also if you have any special print monitors you will need to put on prior to migration.
 

I've seen several problems of this type...

Here are some of the more common things to try.

1. HP TCP/IP Port does not migrate with the
Printmig-Tool by design(Thanks MS). You could go in and
recreate all to ports to Standard TCP/IP ports by hand.

workaround install HP WEBJETADMIN (wja80-3470-s3-en.exe) and don't forget JAVA Runtime (jre-1_5_0_06-windows-i586-p.exe).

2. Kernal mode drivers disabled in 2003

workaround

First you have to change "Disallow installation of printers using kernel mode drivers" to "Disabled" on your 2003 print server

Use the Group Policy Object Editor. You find this value under:
+ Local Computer Policy
++ Computer Configuration
+++ Administrative Templates
++++ Printers

3. printers use their own print monitors. (Cannon, Xerox, lexmark)

workaround load the drivers for them before you restore the print migration backup file. Just loading one type of printer should do the trick. If you haven't done it, just load drivers and rerun restore.

4. once you have done 1-3 then restore the print migration backup file and and most if not all printers will come up online/ready for you.

5. All so make sure you have a list/printout of the printers that were offline on the old print server. Some have been dead for a long time and no one deleted them.

Dave
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top