I don’t know if that would work, but I think it would. Normally when users connect to a server\print-share if the printer drive is newer than what is already installed or doesn’t match what is on the workstation, the workstation gets updated.
From: Don Kuhlman [mailto:drkuhl...@yahoo.com] Sent: Friday, June 17, 2011 4:52 PM To: NT System Admin Issues Subject: Re: Printer/Print server migration from 2003 32 bit to 2008R2 64 bit Glenn, does that mean as long as the share names match, then the users will still be able to print (no user impact) without re-creating their existing printers, even if the backend drivers are 64 bit and may be differently named? That would be great - because now I've just noticed a new issue - it looks like the concept of exporting the hklm\system\currentcontrolset\lanmanserver\shares key to grab the shares isn't working going from 32 bit to 64 bit. I may have to manually recreate all the shares too now. Thanks much! Don ________________________________ From: Glen Johnson <gjohn...@vhcc.edu> To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com> Sent: Fri, June 17, 2011 3:19:35 PM Subject: RE: Printer/Print server migration from 2003 32 bit to 2008R2 64 bit That’s what we did. Match share names, although we are still running both servers. I never thought that maybe I could shutdown the old 32 bit server, rename the 64bit server same as the old one and be golder. Might have worked, but we are too far along not to try it. From: Don Kuhlman [mailto:drkuhl...@yahoo.com] Sent: Friday, June 17, 2011 4:12 PM To: NT System Admin Issues Subject: Re: Printer/Print server migration from 2003 32 bit to 2008R2 64 bit Thanks Glen. That's exactly what I'm seeing now - I've tried to download every flavor of 64 bit drivers from the mfg web site, then install them on the 32 bit server and it keeps failing - comes back with something to the effect that "the specified location does not contain the driver xxxx xxxxx xxxxx for the specified processor architecture" I wonder if I should try to install the 64 bit drivers on the 64 bit server and then make sure the names match (if I can do that) and then try the migration again? Don ________________________________ From: Glen Johnson <gjohn...@vhcc.edu> To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com> Sent: Fri, June 17, 2011 3:00:38 PM Subject: RE: Printer/Print server migration from 2003 32 bit to 2008R2 64 bit My experience has been that the x32 and x64 bit drivers have to be the same name and version, but my experience was on a 64bit server. We were never able to get the x64 drivers to work on an x32 server. From: Don Kuhlman [mailto:drkuhl...@yahoo.com] Sent: Friday, June 17, 2011 2:52 PM To: NT System Admin Issues Subject: Re: Printer/Print server migration from 2003 32 bit to 2008R2 64 bit Thanks John. I went hunting for 64 bit versions of HP, and Lanier drivers to download and install on the 2003 server, but when I go into Printers to add drivers after extracting these "universal" drivers that said 64 bit, the server is telling me that these aren't the right files for the selected architecture, and then it dies. Wierd, as both HP and Lanier sites said these were the drivers for the specific printer model - eg a "Universal" driver for 64 bit. Don ________________________________ From: John Cook <john.c...@pfsf.org> To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com> Sent: Fri, June 17, 2011 12:04:28 PM Subject: RE: Printer/Print server migration from 2003 32 bit to 2008R2 64 bit IIRC that is correct, it’s been a while since I did it. John W. Cook System Administrator Partnership For Strong Families 5950 NW 1st Place Gainesville, Fl 32607 Office (352) 244-1610 Cell (352) 215-6944 MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4 From: Don Kuhlman [mailto:drkuhl...@yahoo.com] Sent: Friday, June 17, 2011 12:57 PM To: NT System Admin Issues Subject: Re: Printer/Print server migration from 2003 32 bit to 2008R2 64 bit Thanks Cameron. Actually we're not having problems with the file server rename/file copy piece, it's getting the printers from the old server to come over to the new server. What I'm seeing seems to indicate that we have to install 64 bit drivers on the old server for each particular printer that exists and then do the migration that way to make the printers come over to where the 64 bit server will re-create or import them. Don ________________________________ From: Cameron <cameron.orl...@gmail.com> To: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com> Sent: Fri, June 17, 2011 10:25:50 AM Subject: Re: Printer/Print server migration from 2003 32 bit to 2008R2 64 bit Why not just use a new name for the server? If you are using a login script, tis easy enough to change user by user...and takes the pressure off of you. Just a thought... On Fri, Jun 17, 2011 at 11:11 AM, Don Kuhlman <drkuhl...@yahoo.com<mailto:drkuhl...@yahoo.com>> wrote: Hi folks. Happy Friday. At the new gig now and have been assigned another project which I haven't worked on before. We're migrating a 2003 32 bit Windows file/print server to 2008R2. I've never had to move printers/print servers before because we never used Windows Print servers at old j0b. My question is this - to migrate printers/print drivers from 32 bit 2003 server to 64 bit 2008R2, do you have to first put 64 bit drivers on the old server that has the 32 bit drivers, and do they have to have the exact same names as the existing 32 bit drivers in order to migrate successfully to 64 bit? Thanks! Here is the background (long) synopsis... I've been researching this since yesterday, and haven't come up with a solid answer that is clear. I've got a server migration scheduled for this weekend and the printers are a major part of it, so I'm hoping the list can point me in the right direction. I've built the new 2008 server, gave it a temporary name, etc. Plan is to ship it to the site, migrate the data, shares, permissions, and printers, then rename the old one, rename the new one to the old one's name, and be done. While tyring to do the printer piece, I used printmig to backup and restore the printers from the 32 bit box to the new 64 bit box. However, the new 2008 R2 server isn't importing or restoring any of the printers - I guess because they are all 32 bit drivers but not sure. So in my research I see that you can use Printbrm.exe on 2008 to try it, or the Print Migration features of the 2008 Print Management role. The printer migration tool is also failing - errors like 0x80070705 and 0x80070c6 are showing on that tool. I checked around and ended up on the MS Print blogs here - http://technet.microsoft.com/en-us/library/dd379557(WS.10).aspx and another site here - http://blogs.technet.com/b/print/archive/2009/08/17/print-services-migration-guide.aspx This was listed as a tip in the blog - As a best practice, you need to install a driver with the same name as the native architecture. To add the x86-based driver to the x64-based destination server, use the x86-based client to remotely open the x64-based server using Windows Explorer and navigate to the remote printer folder and add the driver. To install an x64-based driver on the x86-based source server, use the x64-based client to remotely open the x86-based server using Windows Explorer and navigate to the remote printer folder and add the driver. Any thoughts would be appreciated! Don K ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ________________________________ CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
