printmig.exe, W2003 x64, sharing....

Has anybody had any luck with printmig.exe going from 32-bit Windows to
64-bit? Current print server is Windows 2000 server - printmig.exe works
fine going from this box to another W2k or W2k3 x86 box, but won't work
right on x64. It creates the TCP/IP ports but doesn't install any of the
drivers.no errors are given. I'd seen a forum post suggesting that manually
installing the equivalent x64 drivers *first* (even to dummy ports) would
work - tried that, no dice.

If I can't use printmig or similar to migrate, no big deal - I can manually
create the printers again if I have to. But even so, I'm still having
problems with the 'additional drivers' tab in the share properties - I check
x86 and direct the path to the correct folder where I've downloaded &
extracted the 32-bit driver, and it says it's invalid. I've never used W2003
x64 to share printers before, so I may be missing something obvious.

Target ew server is running Windows Storage Server 2003 R2 (x64) if that
makes any difference. All clients are XP Pro SP2 (32-bit).

 

Hello Lanwench [MVP - Exchange],

Check the answers from Alan Morris about adding the 64bit version drivers
to the print server and then use printbrmui.exe from Vista to backup and
restore.

http://www.velocityreviews.com/forums/t544397-print-server-migration-32bit-to-64bit.html

http://www.velocityreviews.com/foru...igrate-printers-from-32bit-to-64bit-w2k3.html

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Has anybody had any luck with printmig.exe going from 32-bit Windows
> to 64-bit? Current print server is Windows 2000 server - printmig.exe
> works fine going from this box to another W2k or W2k3 x86 box, but
> won't work right on x64. It creates the TCP/IP ports but doesn't
> install any of the drivers.no errors are given. I'd seen a forum post
> suggesting that manually installing the equivalent x64 drivers *first*
> (even to dummy ports) would work - tried that, no dice.
>
> If I can't use printmig or similar to migrate, no big deal - I can
> manually create the printers again if I have to. But even so, I'm
> still having problems with the 'additional drivers' tab in the share
> properties - I check x86 and direct the path to the correct folder
> where I've downloaded & extracted the 32-bit driver, and it says it's
> invalid. I've never used W2003 x64 to share printers before, so I may
> be missing something obvious.
>
> Target ew server is running Windows Storage Server 2003 R2 (x64) if
> that makes any difference. All clients are XP Pro SP2 (32-bit).
>

 

Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de> wrote:
> Hello Lanwench [MVP - Exchange],
>
> Check the answers from Alan Morris about adding the 64bit version
> drivers to the print server and then use printbrmui.exe from Vista to
> backup and restore.
>
> http://www.velocityreviews.com/forums/t544397-print-server-migration-32bit-to-64bit.html
>
> http://www.velocityreviews.com/foru...igrate-printers-from-32bit-to-64bit-w2k3.html
>
Thanks so much, Meinolf. That looks very promising.

 

Printmig.exe will work if the x64 print drivers using the same name are
preinstalled on the server before the restore. Any drivers that do not have
a matched name x64 print driver cannot be restored.

You can work around this by changing the driver in use by the Win2k Server
to another driver that does have a matching 64 print driver, then backing up
and restoring.




--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

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

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:eisuCyw0JHA.4272@TK2MSFTNGP06.phx.gbl...
> Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de> wrote:
>> Hello Lanwench [MVP - Exchange],
>>
>> Check the answers from Alan Morris about adding the 64bit version
>> drivers to the print server and then use printbrmui.exe from Vista to
>> backup and restore.
>>
>> http://www.velocityreviews.com/forums/t544397-print-server-migration-32bit-to-64bit.html
>>
>> http://www.velocityreviews.com/foru...igrate-printers-from-32bit-to-64bit-w2k3.html
>>
> Thanks so much, Meinolf. That looks very promising.
>

 

Alan Morris [MSFT] <alanmo@online.microsoft.com> wrote:
> Printmig.exe will work if the x64 print drivers using the same name
> are preinstalled on the server before the restore. Any drivers that
> do not have a matched name x64 print driver cannot be restored.
>
> You can work around this by changing the driver in use by the Win2k
> Server to another driver that does have a matching 64 print driver,
> then backing up and restoring.

Thanks, Alan. The drivers for x64 were not the same name (there was no way
around that; they were the only current drivers for that OS available). So I
wound up reinstalling all the printers manually on the 2003 x64 box and am
in good shape now - there weren't that many.
>
>
>
>
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
> message news:eisuCyw0JHA.4272@TK2MSFTNGP06.phx.gbl...
>> Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de> wrote:
>>> Hello Lanwench [MVP - Exchange],
>>>
>>> Check the answers from Alan Morris about adding the 64bit version
>>> drivers to the print server and then use printbrmui.exe from Vista
>>> to backup and restore.
>>>
>>> http://www.velocityreviews.com/forums/t544397-print-server-migration-32bit-to-64bit.html
>>>
>>> http://www.velocityreviews.com/foru...igrate-printers-from-32bit-to-64bit-w2k3.html
>>>
>> Thanks so much, Meinolf. That looks very promising.