Re: Move print queues to new server
- From: Felix <Felix@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Mar 2008 09:30:02 -0700
"David Shen [MSFT]" wrote:
Dear Customer,David,
Thank you for posting here.
According to your description, my understanding is that:
The print queue have been migrated to a new server. Your wonder whether the
users can change their direction to the queues on the new print server to
retain their existing default print queue and how it can be done by script.
If anything is misunderstood, please let me know.
Analysis and Suggestion:
======================
In Windows Server 2003 R2, there is a new Microsoft Management Console
(MMC) Print Management that enables you to install, view, and manage all of
the printers in your organization. It can be used with Group Policy to
automatically add printer connections to a computer's Printers and Faxes
folder.
Scenario A (Windows Server 2003)
1. Create a new group policy object with user logon script for deploying
printers.
2. Create a Visual Basic Script for installing the printer, save it to
SYSVOL script folder and configure it as the user logon script.
Script Template:
Set WshNetwork = CreateObject("WScript.Network")
WshNetwork.AddWindowsPrinterConnection "\\Server\printer"
WshNetwork.SetDefaultPrinter "\\Server\printer "
Scenario B (Windows Server 2003 R2)
1. In the Print Management Console, right click the shared printer listed
in the printers folder and choose to "Deploy with Group Policy"
2. In the dialog box, choose a group policy object you want to deploy with
and decide the connection type. For your issue, it should be Per User.
3. Copy pushprintconnections.vbs from "%systemroot%\PMCSnap\" to SYSVOL
script folder, and configure it as the user logon script in that group
policy.
Note:
PushPrinterConnections.vbs runs in the client side is to connect and
disconnect the printer. If you remove the printer connection settings from
the GPO, the PushPrinterConnections.vbs will remove the corresponding
printers from the client computer on the next restart or user logon.
For more reference
=================
How to Add a Default Printer Using a Visual Basic Script
http://support.microsoft.com/kb/263226
How to assign scripts in Windows 2000
http://support.microsoft.com/kb/322241
Step-by-Step Guide for Print Management
http://technet2.microsoft.com/windowsserver/en/library/312b10cb-73ec-40c7-a4
df-63dd7248d93d1033.mspx?mfr=true
Microsoft TechNet Script Center
http://www.microsoft.com/technet/scriptcenter/default.mspx
I hope all the information will be helpful.
Thanks for your time.
David Shen
Microsoft Online Partner Support
Microsoft GTSC
Thanks for your help!
I am having a similar issue. We have an old print server that was recently
migrated and in the process we also changed the queue names to meet a new
naming standard. So right now, both print servers are active and provide
connections to the same printers under different queue names.
What I would like to know is if there's a script that could take the old
printer queue connections and replace them with the new ones from the new
server so that we can eventually decommission the old server. We do not
automatically assign printers to our users by group memberships.
Is this possible?
Thanks!
.
- Prev by Date: Re: migrating from NT4 to 2003 quick outline request
- Next by Date: Re: Novell Migration
- Previous by thread: migate between window server 2003 (no R2) to 2003 R2
- Next by thread: Re: Move print queues to new server
- Index(es):
Relevant Pages
|