none
Print Server migration from w2k3 to win7

    Question

  • We tried to migrate the ques from w2k3 to a w2k8, and win7 but had alot of errors. I had to add most of them myself, still have a handful to still add.

    We tried the migration to w2k8 64x, but you have to have x64 drivers and some of the printers we have do not make a x64 printer driver. That is why we are using win7.  Not a fun project.

    Our old print server must be replaced do to issues it has been having.  Now that the new server is built, what are the steps for a smooth transition to swap out the servers?

    Tuesday, July 19, 2011 6:02 PM

Answers

  • That's a Windows 95 driver.  If you have some 95/98 machines still around. You will need provide a 2003 machine that will support the the software distribution for these clients.  Or just have the 98 machines load their own drivers.  If you have no 98 machine, delete the print driver from 2003.

    HP has 32bit and 64bit drivers for the 4250 on Windows update. 


    Alan Morris Windows Printing Team
    • Marked as answer by Bruce-Liu Friday, July 29, 2011 6:26 AM
    Wednesday, July 20, 2011 11:56 PM

All replies

  • Hi,

     

    You can use the Printer Migration Wizard or Print Management.

     

    For more information, please refer to these articles:

     

    How to back up and then restore printers when you upgrade from Windows Server 2003 to Windows Server 2008

    http://support.microsoft.com/kb/938923

     

    Migrate Print Servers

    http://technet.microsoft.com/en-us/library/cc722360.aspx

     

    Hope this helps.

     

    Regards,

    Bruce

    Wednesday, July 20, 2011 1:59 AM
  • What vendor is not providing 64bit drivers for your printers?  If you have older devices and can access a x64 Server or x64 Pro CD, install the drivers off that source.

    Windows 7 has a 10 client limit, it is not designed to act as a server.  If you have under 10 machines on your network you will be fine. 

     If you get error 2 using printbrm to export printers, the language monitor on the 2003 print server has been editted in the registry.  Look for the solution I have posted previously.  If you are getting any other error during backup or the issue is on restore, send along the errors.


     

    Alan Morris Windows Printing Team


    Wednesday, July 20, 2011 7:21 AM
  • Thx Bruce

    I did use this method to migrate, but had serious problems with the transfers.  No only that, but for some odd reason, we could only access the old print server from one computer (Win7) via the print mgmt.  We tried to access it on another win 7 and w2k8 machine, but had no luck.  From the Win 7 PC we could access it from, we had alot of errors with HP and Lexmark drivers and therefore was not able to get a complete back up.  After multiple times of trying, we were able to get one decent back up that had about half the printers.

    Wednesday, July 20, 2011 12:33 PM
  • Lexmark t620 do not make an x64 driver, there might have been another or two, but i dont recall.  We have a bunch of the t620 printers still being used.  We are replacing them slowly with ho 4015, as most of the t620 have died.

    When we tried to do the back up the way Bruce mentioned, we did get alot of errors, we got a backup that had about half the printers and we installed the rest.  I still have to add another 10 or 20, but that is another mess. Unless of course i get still some how get a good back up of my w2k3 machine.

    Wednesday, July 20, 2011 12:38 PM
  • I have set up a new w2k8 r2 x64 box and made it a print server.  I was able to add the current w2k3 printer server to it as well as the win7 box i created.

    I tired to export from the w2k3 and got the same errors (error (3)) for 27 drivers.  I tried to import the file when it was done, but nothing came over.

    Any ideas?

    Wednesday, July 20, 2011 4:56 PM
  • error

         3 ERROR_PATH_NOT_FOUND

    I'd say ditch the old drivers.  Preinstall the latest x64 driver that has the same name as the 32bit driver used in the printer definition, then restore.  Or you can switch the drivers the queue uses to a new driver name using the command line tool and a configuration xml.  Here's technet article on this  http://blogs.technet.com/b/askperf/archive/2009/02/20/two-minute-drill-printbrm-and-the-configuration-file.aspx 


    Alan Morris Windows Printing Team
    Wednesday, July 20, 2011 8:17 PM
  • Thx alan

    What about my antique printers that don't have x64 drivers?

    FYI here is what the log said.

     

    Log Name:      Application

    Source:        Microsoft-Windows-PrintBRM

    Date:          7/20/2011 12:14:46 PM

    Event ID:      87

    Task Category: (3)

    Level:         Error

    Keywords:      Classic

    User:          N/A

     

    Description:

    Printbrm.exe (the Printer Migration Wizard or the command-line tool) failed to backup driver HP LaserJet 4250 PCL5e (Windows 4.0). The backup process will continue, skipping this driver. Error: 0x80070040. The specified network name is no longer available.

    .

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-PrintBRM" Guid="{CF3F502E-B40D-4071-996F-00981EDF938E}" EventSourceName="PrintBrm" />

        <EventID Qualifiers="49154">87</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>3</Task>

        <Opcode>0</Opcode>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2011-07-20T16:14:46.000000000Z" />

        <EventRecordID>377</EventRecordID>

        <Correlation />

        <Execution ProcessID="0" ThreadID="0" />

        <Channel>Application</Channel>

        <Security />

      </System>

      <EventData>

        <Data Name="DriverName">HP LaserJet 4250 PCL5e</Data>

        <Data Name="DriverArchitecture">Windows 4.0</Data>

        <Data Name="Error">0x80070040. The specified network name is no longer available.

    </Data>

      </EventData>

    </Event>

     

    Wednesday, July 20, 2011 10:54 PM
  • That's a Windows 95 driver.  If you have some 95/98 machines still around. You will need provide a 2003 machine that will support the the software distribution for these clients.  Or just have the 98 machines load their own drivers.  If you have no 98 machine, delete the print driver from 2003.

    HP has 32bit and 64bit drivers for the 4250 on Windows update. 


    Alan Morris Windows Printing Team
    • Marked as answer by Bruce-Liu Friday, July 29, 2011 6:26 AM
    Wednesday, July 20, 2011 11:56 PM