Hey folks, it’s Yong Rhee once more. Today’s post is a short, but an important one for Print Server administrators. If you’ve ever administered a Print Server, the chances are that you’ve probably had to perform a print server migration as well. Whether that migration is to a Windows Server 2003 or Windows Server 2008 machine, printer migrations always seem to somehow get very messy and complicated. Printing issues are more of a helpdesk headache as well – more than logon or application issues. So as an administrator, how can you migrate printers without causing a printing outage in your environment? Let’s take a look Most Windows printer administrators have either heard of or used the Print Migrator tool (PrintMig).

PrintMig 3.0 was released back in May of 2002, and version 3.1 was released in September 2003. By comparison, Windows Server 2003 was released in March of 2003, Windows Server 2003 SP1 was released in March 2005, and Windows Server 2003 SP2 was released in February 2007.

Nov 18, 2003 Has anyone else expereince problems with Printmig.exe version 3.1 not working correctly on Windows 2000 Terminal Server and Citrix Metaftame XPe. Tag: PrintBRM Migrating Print. PRINTBRM. Crack Delta Force 2 Extreme there. EXE is the replacement for the now-retired PrintMig 3.1 utility. PRINTBRM.EXE is located in the%systemroot% System32 Spool. Feb 01, 2018 Printmig 3.1 error. Discussion in 'Microsoft Windows 2000 Printing' started by Guest, Oct 19, 2005. Master Key Ebook. Microsoft Print Migrator Free Download - Automates the backup and restore of print configuration data on print servers.

So, the operating system has been secured and updated, but the PrintMig tool has not been updated in over five years. Hmmm, that makes you stop and think for a second, doesn’t it? Here’s five other reasons that Print Migrator 3.1 is not as robust of a migration solution as it once was: • PrintMig was created before OEM printer manufacturers starting shipping printer drivers containing.cab files.