Velocity Reviews

Velocity Reviews (http://www.velocityreviews.com/forums/index.php)
-   Windows 64bit (http://www.velocityreviews.com/forums/f46-windows-64bit.html)
-   -   Print Server Migration 32bit to 64bit (http://www.velocityreviews.com/forums/t544397-print-server-migration-32bit-to-64bit.html)

=?Utf-8?B?anQ=?= 10-15-2007 03:58 PM

Print Server Migration 32bit to 64bit
 
I have 300+ plus printers that need to be moved over to a 64bit 2003 Server
O.S.

What would be the easiest way to tackle this? Should I focus on importing
all the printers to the new server and then go through the process of adding
drivers for each printer?

From what I've read, printmig.exe is not the correct tool to use for
migrating from a 32bit os to a 64bit os. Would using printmanagemnt.msc from
a Vista machine do the trick?

I'm not sure how a situation like this affects end users, will I have to
come up with a way to remap printers after migrating to 64bit version?

Thanks in advance

jt





Charlie Russel - MVP 10-15-2007 08:34 PM

Re: Print Server Migration 32bit to 64bit
 
If you've got that many printers to deal with, you'll want to script the
entire thing. This will take a bit of extra work up front to create the WMI
script, but once you've done it, it's easy to test it before you finalize.

To avoid having to remap everyone's printers, the easiest solution is to use
exactly the same names for the printer shares, and then name the new server
the same name as the old server. (Obviously, they can't both be on the same
network at the same time while they share a name!)

Again, getting all this right will take some time to completely debug your
script, but a whole lot less time than it would take to do it all by hand.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"jt" <jt@discussions.microsoft.com> wrote in message
news:28E1B92A-C9B5-407A-B5B9-6231FBA2EA3E@microsoft.com...
>I have 300+ plus printers that need to be moved over to a 64bit 2003 Server
> O.S.
>
> What would be the easiest way to tackle this? Should I focus on importing
> all the printers to the new server and then go through the process of
> adding
> drivers for each printer?
>
> From what I've read, printmig.exe is not the correct tool to use for
> migrating from a 32bit os to a 64bit os. Would using printmanagemnt.msc
> from
> a Vista machine do the trick?
>
> I'm not sure how a situation like this affects end users, will I have to
> come up with a way to remap printers after migrating to 64bit version?
>
> Thanks in advance
>
> jt
>
>
>
>



Alan Morris [MSFT] 10-15-2007 09:08 PM

Re: Print Server Migration 32bit to 64bit
 
The first thing to do is install the 64 bit drivers onto the 32bit server.
If you already accomplished this to enable Point and Print for the 64bit
clients, you can backup the 32bit server using Vista printbrmui.exe This
will backup the 32 and 64 bit drivers.

Restore the printers to the 64 bit server and verify everything migrated
properly

If you have any printers that do not have 64 bit drivers, you will need to
determine if there is a compatible 64bit driver available.

printbrm will only migrate Standard TCP/IP Ports

--
Alan Morris
Windows 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.

"Charlie Russel - MVP" <charlie@mvKILLALLSPAMMERSps.org> wrote in message
news:8CE0EEF8-8B13-4E34-B386-2AEB5945D15B@microsoft.com...
> If you've got that many printers to deal with, you'll want to script the
> entire thing. This will take a bit of extra work up front to create the
> WMI script, but once you've done it, it's easy to test it before you
> finalize.
>
> To avoid having to remap everyone's printers, the easiest solution is to
> use exactly the same names for the printer shares, and then name the new
> server the same name as the old server. (Obviously, they can't both be on
> the same network at the same time while they share a name!)
>
> Again, getting all this right will take some time to completely debug your
> script, but a whole lot less time than it would take to do it all by hand.
>
> --
> Charlie.
> http://msmvps.com/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "jt" <jt@discussions.microsoft.com> wrote in message
> news:28E1B92A-C9B5-407A-B5B9-6231FBA2EA3E@microsoft.com...
>>I have 300+ plus printers that need to be moved over to a 64bit 2003
>>Server
>> O.S.
>>
>> What would be the easiest way to tackle this? Should I focus on importing
>> all the printers to the new server and then go through the process of
>> adding
>> drivers for each printer?
>>
>> From what I've read, printmig.exe is not the correct tool to use for
>> migrating from a 32bit os to a 64bit os. Would using printmanagemnt.msc
>> from
>> a Vista machine do the trick?
>>
>> I'm not sure how a situation like this affects end users, will I have to
>> come up with a way to remap printers after migrating to 64bit version?
>>
>> Thanks in advance
>>
>> jt
>>
>>
>>
>>

>




=?Utf-8?B?anQ=?= 10-15-2007 09:13 PM

Re: Print Server Migration 32bit to 64bit
 
Thanks very much for the reply. Is there a known tool to assist with this
type of scripting? Maybe something that's related to prnadmin.dll?


jt


"Charlie Russel - MVP" wrote:

> If you've got that many printers to deal with, you'll want to script the
> entire thing. This will take a bit of extra work up front to create the WMI
> script, but once you've done it, it's easy to test it before you finalize.
>
> To avoid having to remap everyone's printers, the easiest solution is to use
> exactly the same names for the printer shares, and then name the new server
> the same name as the old server. (Obviously, they can't both be on the same
> network at the same time while they share a name!)
>
> Again, getting all this right will take some time to completely debug your
> script, but a whole lot less time than it would take to do it all by hand.
>
> --
> Charlie.
> http://msmvps.com/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "jt" <jt@discussions.microsoft.com> wrote in message
> news:28E1B92A-C9B5-407A-B5B9-6231FBA2EA3E@microsoft.com...
> >I have 300+ plus printers that need to be moved over to a 64bit 2003 Server
> > O.S.
> >
> > What would be the easiest way to tackle this? Should I focus on importing
> > all the printers to the new server and then go through the process of
> > adding
> > drivers for each printer?
> >
> > From what I've read, printmig.exe is not the correct tool to use for
> > migrating from a 32bit os to a 64bit os. Would using printmanagemnt.msc
> > from
> > a Vista machine do the trick?
> >
> > I'm not sure how a situation like this affects end users, will I have to
> > come up with a way to remap printers after migrating to 64bit version?
> >
> > Thanks in advance
> >
> > jt
> >
> >
> >
> >

>


Charlie Russel - MVP 10-15-2007 11:52 PM

Re: Print Server Migration 32bit to 64bit
 
Alan has pointed you to one I didn't know about for some of it - the drivers
question. For the rest? A good place to start is the Microsoft ScriptCenter.
http://www.microsoft.com/technet/scr...r/default.mspx

I see one in there for listing all published printers, for example. It's VB,
not PowerShell, but hey, you can always convert it if you need to...

http://www.microsoft.com/technet/scr....mspx?mfr=true

there are lots of others.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"jt" <jt@discussions.microsoft.com> wrote in message
news:670CBD8D-EB20-44FC-BE75-C34968A97730@microsoft.com...
> Thanks very much for the reply. Is there a known tool to assist with this
> type of scripting? Maybe something that's related to prnadmin.dll?
>
>
> jt
>
>
> "Charlie Russel - MVP" wrote:
>
>> If you've got that many printers to deal with, you'll want to script the
>> entire thing. This will take a bit of extra work up front to create the
>> WMI
>> script, but once you've done it, it's easy to test it before you
>> finalize.
>>
>> To avoid having to remap everyone's printers, the easiest solution is to
>> use
>> exactly the same names for the printer shares, and then name the new
>> server
>> the same name as the old server. (Obviously, they can't both be on the
>> same
>> network at the same time while they share a name!)
>>
>> Again, getting all this right will take some time to completely debug
>> your
>> script, but a whole lot less time than it would take to do it all by
>> hand.
>>
>> --
>> Charlie.
>> http://msmvps.com/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>>
>> "jt" <jt@discussions.microsoft.com> wrote in message
>> news:28E1B92A-C9B5-407A-B5B9-6231FBA2EA3E@microsoft.com...
>> >I have 300+ plus printers that need to be moved over to a 64bit 2003
>> >Server
>> > O.S.
>> >
>> > What would be the easiest way to tackle this? Should I focus on
>> > importing
>> > all the printers to the new server and then go through the process of
>> > adding
>> > drivers for each printer?
>> >
>> > From what I've read, printmig.exe is not the correct tool to use for
>> > migrating from a 32bit os to a 64bit os. Would using printmanagemnt.msc
>> > from
>> > a Vista machine do the trick?
>> >
>> > I'm not sure how a situation like this affects end users, will I have
>> > to
>> > come up with a way to remap printers after migrating to 64bit version?
>> >
>> > Thanks in advance
>> >
>> > jt
>> >
>> >
>> >
>> >

>>




All times are GMT. The time now is 06:19 AM.

Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.