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> 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 > 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
