Print Migrator 3.0

  • Thread starter Thread starter DK
  • Start date Start date
D

DK

Has anyone been able to actually get this utility to work? It sure
seems to back up ad restore like a champ (From NT 4.0 (SP6a) to
Windows 2000 (SP4), but when you stop the print services on the NT
machine, printing most certainly does not resume from the 2000 server.
Is there something I am missing, or does this utility still lack in
functionality? I just want to pull printers off of my NT box and set
them up on the 2000 server so my wide spread users still have printing
capability without visiting each and every machine.
 
I think I get what you are attempting to do. If this is not your scenario
please let me know.

The tool is designed to move the printers. It does not change the server
name.

current NT4 SERVER1, new Win2k SERVER2

run printmig to backup the NT4 configuration of SERVER1

restore the cab to SERVER2 (verify that the printers work)

rename SERVER1 (to an unused name)

rename SERVER2 to SERVER1

after the reboot you'll see connections magically appear. This can take 30
minutes as DNS registration replicates across the domain and the old IP
address translation directs to the new IP.


--
Alan Morris
Microsoft Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Alan - Thanks for the response....but renaming the new server that is
to house the printers will not be an option. I wanted to move them
from Server1 to Server2, and then be able to (as painlessly as
possible) direct printing to the new server, and remove Server1 from
the picture altogether (without renaming the new server, as it has a
name for it and its functions already). I'll check Active Directory
settings to see if I can use any GPO help to maybe recreate the
printers after they have been moved to the new one. Not sure why I
thought the Migrator tool would be able to do this for me. If you
know of any least painful ways to move about 10 printers to a new
server and change anywhere from 40-100 computers that point to those
printers, that would be extremely useful information!
 
You can attempt to alias the server but this will still require that Server1
be taken off the network. Then all printers on Server 2 can be accessed by
connecting to \\Server1 or \\Server2. I am pretty sure you need SP3
installed for aliasing to be supported by the print subsystem.

Changing the clients:
try rundll32, this can delete an existing connection and add a new
connection.
rundll32 printui.dll,PrintUIEntry /?
http://support.microsoft.com/default.aspx?scid=kb;EN-US;189105
How to Add Printers with No User Interaction in Windows XP

--
Alan Morris
Microsoft Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

DK said:
Alan - Thanks for the response....but renaming the new server that is
to house the printers will not be an option. I wanted to move them
from Server1 to Server2, and then be able to (as painlessly as
possible) direct printing to the new server, and remove Server1 from
the picture altogether (without renaming the new server, as it has a
name for it and its functions already). I'll check Active Directory
settings to see if I can use any GPO help to maybe recreate the
printers after they have been moved to the new one. Not sure why I
thought the Migrator tool would be able to do this for me. If you
know of any least painful ways to move about 10 printers to a new
server and change anywhere from 40-100 computers that point to those
printers, that would be extremely useful information!



"Alan Morris\(MSFT\)" <[email protected]> wrote in message
I think I get what you are attempting to do. If this is not your scenario
please let me know.

The tool is designed to move the printers. It does not change the server
name.

current NT4 SERVER1, new Win2k SERVER2

run printmig to backup the NT4 configuration of SERVER1

restore the cab to SERVER2 (verify that the printers work)

rename SERVER1 (to an unused name)

rename SERVER2 to SERVER1

after the reboot you'll see connections magically appear. This can take 30
minutes as DNS registration replicates across the domain and the old IP
address translation directs to the new IP.


--
Alan Morris
Microsoft Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
Click to expand...
Click to expand...
 
Back
Top