When I did this, I installed both 32 & 64 bit drivers on the 2003 server for all queues before exporting. This way, I did not need to worry about the NOBIN switch. The drivers migrated too.
The "Pharos Queue" port cannot be migrated. After you install the Uniprint system, you have the option to take control over the print queues with the Print Migration Assistant. Let us know how it goes...
I guess the Print Migration Assistant for Windows 2008 is a MMC snap-in and PRINTBRM is the command-line equivant. I want to migrate the printers to the new server and leave the old server running. Does the Print Migration Assistant allow this migration without disrupting the current server? My thoughts are I can get everything ready on the new server up until the renaming then pick my downtime to transfer the database and rename the new server and use the NameSyncTool.
You got it. That is absolutely correct.
The Printer Migration Wizard transferred over the Pharos Queues but I had to manually set them to the "Pause" state for Pharos. I also found that I needed to export the registry setting [HKEY_USERS],[.Default],[Printers] so that Pharos would recognize the physical printers once again. After a few struggles, I was able to successfully migrate from Windows 2003 32bit to Windows 2008 R2. Now on to Uniprint 8.3.
I am in the same boat this summer migrating from Windows 2003 to 2008 R2. I am testing a migration strategy right now. I will be using the PRINTBRM as well. I'll let you know if I run into any issues or solutions.
Don't forget about any scripts that you might be running. Windows 2008 will now be in Program Files (86) which I need to modify my scripts. But my scripts are for SignUp.
I have already set up a Win2k8 64 bit print server in our Pharos configuration; but on that server I had created new printers and queues, so I didn't have to worry about printer migration.
I had run into the issue with the scripts you point out, and instead of modifying my scripts (since I want to use the same scripts across our Win2k3 and Win2k8 servers), I used the Junction utility from Sysinternals to create a junction point under c:\program files to point to the Pharos directory under c:\program files (86):
C:\Program Files>junction pharos
Junction v1.06 - Windows junction creator and reparse point viewer
Copyright (C) 2000-2010 Mark Russinovich
Sysinternals - www.sysinternals.com
C:\Program Files\pharos: JUNCTION
Substitute Name: c:\Program Files (x86)\pharos
Here's a link to the Junction utility: