[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2636
  • Last Modified:

Microsoft Printer Migrator 3.1 not working on Windows 2003

I download Print Migrator 3.1 at
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9b9f2925-cbc9-44da-b2c9-ffdbc46b0b17
Install it on the old printer server (Windows 2003 standard 32-bit).
It 'see' all the printer drivers, but NOT the printers. I back it up and restore it to another Windows 2003 server (32-bit). Again the second Windows 2003 server 'see' all the printer drivers but not the printers.

Q#1. Why does the tool not see the printers?

Q#2. Any other (version of) printer migrator to use?

Q#3. Any settings to check (in order to make it work)?

Thanks.
0
richtree
Asked:
richtree
  • 4
  • 4
5 Solutions
 
Felix LevenCommented:
I tested the tool on 2003 Standard SP2 and it worked OK.

Print Migrator 3.1 is no longer supported by Microsoft. The Printer Migration Wizard and the Printbrm.exe command-line tool were introduced in Windows 7 to replace it. For more information about this decision, see the blog Ask the Performance Team (http://blogs.technet.com/askperf/archive/2008/10/17/why-printmig-3-1-is-retired.aspx).
0
 
rhinocerosCommented:
0
 
richtreeAuthor Commented:
Thanks for the responses. Please comment on my questions.

Q#4. Should the Print Migrator 3.1 'see' printer shares on the source machine?
Q#5. Can the Print Migrator 3.1 'restore' all the same printer shares from the source machine to the target machine?
Q#6. Did I download the wrong version of the tool or something else?
0
Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

 
Felix LevenCommented:
Q#4. All local installed printers
Q#5. Yes
Q#6. No, other Version or support available, cause the tool is discontinued.

What PrintMig can't do:

1.PrintMig was created before OEM printer manufacturers starting shipping printer drivers containing .cab files.  As a result, PrintMig 3.1 cannot restore printer drivers that have .cab files in them
2.PrintMig was created prior to Windows Server 2003 SP1 and SP2.  For clustered printing scenarios, the folder structure for the location of Print Processors changed, and thus PrintMig is unaware of these new locations
3.PrintMig only recognizes local or NetBIOS path names to separator pages (.sep files).  If you use a fully qualified name (FQDN) for the location of .sep files it will cause PrintMig to crash with an access violation
4.PrintMig cannot restore servers that include the word “Spool” in their network name, for example Spooler1 or PrintSpool
5.PrintMig does not work with 64-bit (x64 or IA64) print servers because x 64 servers were not widely deployed when PrintMig 3.1 was released
0
 
richtreeAuthor Commented:
Thank you MrGraves.
Q#7. Should the tool 'see' and 'restore' printers using TCP/IP ports?
Q#8. Should the tool 'see' and 'restore' printer shares?
Q#9. Should the tool 'see' and 'restore' network shared printers from other print server?

Thanks.
0
 
Felix LevenCommented:
Q#7 All local Printer ports

Q#8 All local printer shares

Q#9 No remote printers
 
 All local printer drivers, not including CAB files
0
 
richtreeAuthor Commented:

How to verify if a printer has .cab files?
0
 
Felix LevenCommented:
C:\WINDOWS\system32\spool\drivers\*.cab HP drivers for example
0
 
richtreeAuthor Commented:
Thank you very much.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now