Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 2275629 - Last Review: February 21, 2011 - Revision: 4.1
Windows Server 2003 Server Print Queue Migration
Microsoft Professional Advisory Services is a support option that provides short-term, proactive, consultative support beyond break-fix product maintenance needs. This includes working with the same technician for assistance with issues like product migration, code review, or new program development and is a remote, phone-based support option. This service is typically used for shorter engagements, and is designed for developers and IT professionals who do not require the traditional onsite consulting or sustained account management services that are available from other Microsoft support options.
For additional information on Microsoft Advisory Services, including on how to engage, refer to this Microsoft web page:
http://support.microsoft.com/gp/AdvisoryService
(http://support.microsoft.com/gp/AdvisoryService)
This Advisory Services scenario is designed to assist customers who are in the proactive planning stages of migrating print queues between print servers.This advisory will focus on the migration of print queues between separate print servers.
Discussions topics will include:
- Documenting and taking inventory of the printer queues, drivers and ports to be migrated.
- Choosing a printer queue migration method.
- Cleaning the print spooler environment:
o  Converting 3rd party printer drivers to in-box printer drivers when possible.
o  Updating other 3rd party printer drivers from manufacturer websites.
o  Removing 3rd party port monitors.
o  Removing 3rd party print processors.
o  Removing kernel mode (version 2) drivers.
- Installing 64-bit drivers prior to cross-architecture migration.
- Manually creating any print queues that were not automatically migrated.
Scoping questions
Out of Scope
- This deliverable will not include installation or configuration of a clustered server or virtual print resource.
- This deliverable will not include upgrading the operating system of an existing print server.
- This deliverable will not include replacing an existing print server.
- This deliverable will not include break-fix troubleshooting of individual print queues that fail to migrate automatically with the Print Management Console (PMC) or the PrintBRM.exe command line tool.
- This deliverable will not include deploying or remapping printer queues to client machines.
- This deliverable will not include migration of custom forms or color profiles.
- This deliverable will not include migration of print queues between print servers in a workgroup.
- This deliverable will not include editing any .XML files used in automated print queue migration.
Included with Scope
- Installation of the Print Server role on a target standalone Windows Server 2008 or Server 2008 R2 as needed.
- Conversion of LPR ports to Standard TCP/IP Ports (Standard Port Monitor).
- Cleaning the print key and simplifying the print configuration on the source server prior to print queue migration.
- Migrating print queues to/from cluster virtual print resources.
- Migrating print queues between cross-processor architectures, specifically from x86 print servers to x64 print servers.
Scoping questions- Do you already have a standalone server or clustered virtual print resource target ready?
a.      No: Stop. The scope of this offering does not include setting up a new Windows server or configuring a virtual print resource.
b.     If yes, then continue with the following questions.
- Are you using a non-Web edition SKU of the Windows Server product?
a.      No: Stop. Web editions of Windows Server do not include print server functionality.
b.     If yes, then continue with the following questions.
- Have you already upgraded your print servers to the desired operating systems?
a.      No: Stop. The scope of this offering does not include operating system upgrades.
b.     If yes, then continue with the following questions.
- Are all servers involved in print queue migration running with the latest service pack? The servers to be concerned with are the source server(s), the target server(s) and potentially an additional machine running Print Management Console or PrintBRM.exe remotely.
a.      No: Stop. Having your servers running the most current updates is important for their stability and to provide greatest chance of consistency when migrating printer queues.
b.     If yes, then continue with the following questions.
- Is your source print server currently running without any errors?
a.      No: Stop. Break-fix incidents should be used to correct any errors prior to attempting migration of printer queues.
b.     If yes, then continue with the following questions.
- Are you have access to a domain administrator account in your environment?
a.      No: Stop. You must have domain admin privileges to migrate print queues.
b.     If yes, then continue with the following questions.
- Is your goal to troubleshoot errors previously experienced with Print Management Console or PrintBRM.exe?
Yes: Stop. Break-fix incidents should be used to correct specific errors.
Below is a list of self-help resources or this scenario. These resources may also be used by Microsoft Support Engineers during an Advisory Services engagement.
Self Help Topics:
Microsoft TechNet: Choosing a Print Server Migration Method
(http://technet.microsoft.com/en-us/library/cc780640(WS.10).aspx)
Microsoft TechNet: Migrate print servers
(http://technet2.microsoft.com/WindowsVista/en/library/b030067b-effa-4e6b-a47d-d61debaf90621033.mspx?mfr=true)
KB 938923 - How to back up and then restore printers when you upgrade from Windows Server 2003 to Windows Server 2008
(http://kbalertz.com/Feedback.aspx?kbNumber=938923)
Why PrintMig 3.1 is Retired
(http://blogs.technet.com/askperf/archive/2008/10/17/why-printmig-3-1-is-retired.aspx)
Additional Topics:
Windows Vista Print Management Step-by-Step Guide
(http://technet.microsoft.com/en-us/windowsvista/aa905094.aspx)
Print Migration Events
(http://technet2.microsoft.com/windowsserver2008/en/library/19e4636d-478d-4d68-ba56-548ea31b90911033.mspx?mfr=true)
Print Management for IT Pros
(http://windowshelp.microsoft.com/Windows/en-US/Help/018ea158-ed4c-4cf5-a95c-2eccc09dc2ad1033.mspx)
KB 962998 - Error message when you try to export printers to a file on a Windows Server 2008-based cluster node: "Windows encountered errors during the migration process"
(http://kbalertz.com/Feedback.aspx?kbNumber=962998)
KB 971428 - The restored printer is shown as FILE port instead of USB port after you use the Printbrm.exe command-line tool to export the printer settings of a non- SPM or non- LPR printer with USB port to a new computer in Windows Vista or in Windows Server 2008
(http://kbalertz.com/Feedback.aspx?kbNumber=971428)
KB 883789 – You may not see the Printers and Faxes icon in Windows Explorer on a remote computer, and you may not be able to add a printer to a remote computer by using a command-line tool in Windows Server 2003
(http://kbalertz.com/Feedback.aspx?kbNumber=883789)
"If the computer that is running Windows Server 2003 does not have any local shared printers, the RPC endpoint for the spooler is not created."
Ask the Performance Team blog
(http://blogs.msdn.com/askperf/)
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See
Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.
APPLIES TO
- Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
- Microsoft Windows Server 2003 R2 Datacenter x64 Edition
- Microsoft Windows Server 2003 R2 Datacenter x64 Edition with Service Pack 2
- Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
- Microsoft Windows Server 2003 R2 Enterprise x64 Edition
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Datacenter without Hyper-V
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 Enterprise without Hyper-V
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Server 2008 R2 Service Pack 1
- Windows Server 2008 R2 Standard
- Windows Server 2008 R2 Standard without Hyper-V
- Windows Server 2008 Service Pack 2
- Windows Server 2008 Standard without Hyper-V
- Windows Server 2008 Datacenter
- Windows Server 2008 Enterprise
- Windows Server 2008 Standard
| kbproadvisory kbinfo kbsurveynew kbtshoot kbnofix kbprowindowsserver KB2275629 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate