Windows server 2003 print migrator 3.1

The entire risk of the use or the results from the use of this document remains with the user. All other trademarks are property of their respective owners. Welcome, guest! The things that are better left unspoken. PrintMig PrintMig 3. PrintMig is more of a backup tool The File Server Migration Toolkit isn't the perfect tool to make backups of files on a server. Which I recommend you change from its default settings Since making backups is in no way a guaranty that you can also restore, you'd have to test your backups.

All rights reserved. Metro Theme created by Jon Wigham. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Best Answer. Don Aug 1, at UTC. View this "Best Answer" in the replies below ». The window will show that it will go in progress, installing and restoring printer configuration on the machine.

If for some reason, a message box saying Missing Service just click OK. Note: Do inform the requestor about what had happened or what are the services that were missing during the restoration. Finally, a Restore complete message should be displayed once completed. Subsequent instances of the Print Migrator application will fail with an error that the temp file could not be created.

Tip: It may be necessary to stop and start the Spooler service when restoring printer configuration to a Windows NT 4 system. If the Windows NT 4 system is a Clustered print server, it will be necessary to take the spooler resource offline, then stop and start the spooler, and lastly bring the spooler resource online again.

It is important to be aware of the differences in the print subsystem across multiple versions of the Windows Server products, as well as the different configurations that may be in use.

The following sections discuss special configurations that should be given consideration when planning and deploying print servers using Print Migrator 3. Print servers should only be backed up or restored by a single instance of Print Migrator 3. Because Print Migrator will stop and start print-related services, simultaneous operations could experience corruption or failure.

Native Windows print drivers may not be restored to NT 4 systems. Windows NT 4 print drivers run in the kernel mode space of the operating system, whereas Windows systems run native print drivers in user mode. To increase backwards compatibility and better interoperability in environment Windows NT 4 and Windows and later Windows can run kernel mode drivers as well.

The end result is that it may be beneficial to continue using the Kernel Mode drivers until the clients and the servers all support User Mode print drivers. Port Name Collision? Printer port enumeration is done by the print spooler process. Print ports are loaded alphabetically, based on the name of the port monitor. It is possible that two or more ports can be using different port monitors, but have the same port name. In this case, the first port that is initialized will function correctly and subsequent ports with the same name will fail to initialize.

This is because lprmon. Printer Name Collision? The last printer written to the server with the same name as preexisting printers will be preserved. Last write wins model. Printer Share Name Collision?

If printers are restored to a server and there is an existing printer with the same printer share name, then neither of these printers will be shared. I To resolve ,select a unique share name for each printer. It may be necessary to stop and start the spooler service when restoring printer configuration to a Windows NT 4 system.

If the Windows NT 4 system is a clustered print server, it will be necessary to take the spooler resource offline, then stop and start the spooler, and lastly bring the spooler resource online again. Contact Tel: Support: support printlimit.

Contact Tel: Support: support printlimit. Share PrintLimit on Twitter.