Print Server Migration 32bit to 64bit

Discussion in 'Windows 64bit' started by =?Utf-8?B?anQ=?=, Oct 15, 2007.

  1. 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=?=, Oct 15, 2007
    #1
    1. Advertising

  2. 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" <> wrote in message
    news:...
    >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, Oct 15, 2007
    #2
    1. Advertising

  3. 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" <> wrote in message
    news:...
    > 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" <> wrote in message
    > news:...
    >>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], Oct 15, 2007
    #3
  4. 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" <> wrote in message
    > news:...
    > >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=?=, Oct 15, 2007
    #4
  5. 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/scriptcenter/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/scriptcenter/scripts/default.mspx?mfr=true

    there are lots of others.

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


    "jt" <> wrote in message
    news:...
    > 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" <> wrote in message
    >> news:...
    >> >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, Oct 16, 2007
    #5
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. =?Utf-8?B?ZWRoZWFk?=

    64bit print server - no 64bit drivers

    =?Utf-8?B?ZWRoZWFk?=, Mar 30, 2007, in forum: Windows 64bit
    Replies:
    1
    Views:
    999
    Charlie Russel - MVP
    Mar 30, 2007
  2. =?Utf-8?B?SGFyb29uIE1hbGlr?=

    DHCP Server migration to a 64 bit Clustered Server

    =?Utf-8?B?SGFyb29uIE1hbGlr?=, May 30, 2007, in forum: Windows 64bit
    Replies:
    2
    Views:
    713
    =?Utf-8?B?SGFyb29uIE1hbGlr?=
    Jun 4, 2007
  3. =?Utf-8?B?TWFsYm9ldWY=?=

    32bit aps fail on win2k3 64bit server after MS Updates

    =?Utf-8?B?TWFsYm9ldWY=?=, Aug 18, 2007, in forum: Windows 64bit
    Replies:
    13
    Views:
    735
    =?Utf-8?B?TWFsYm9ldWY=?=
    Aug 21, 2007
  4. =?Utf-8?B?V2FkZUJhcnQ=?=

    Printer Server (64bit OS and 32bit Clients)

    =?Utf-8?B?V2FkZUJhcnQ=?=, Oct 8, 2007, in forum: Windows 64bit
    Replies:
    1
    Views:
    761
    Charlie Russel - MVP
    Oct 9, 2007
  5. Jaime Barahona

    2003 server from 32bit to 64bit

    Jaime Barahona, Jan 17, 2008, in forum: Windows 64bit
    Replies:
    3
    Views:
    587
    Charlie Russel - MVP
    Jan 18, 2008
Loading...

Share This Page