Relocating a networked printer to a different location & name chan

[Q]

Hey everyone, I'm not sure I'm at the right place for this..

Here is my issue.

We have a print server with 23 networked printers. We are relocating a
computer lab to a different location and the printer that belongs to that lab
is being relocated as well. Our printers are named based on building/room
number.

My question is, what is the best way "best practice" on renaming the printer
and having all the Windows XP clients (300 of them) updated with the updated
printer name?


Thanks
Quinton

 

[Alan Morris [MSFT]]

renaming the printer will break the connection from the client. There are a
couple of scripts available that will look for the old server name and
printer, delete the connection, then add the new connection to the machine.

for just the one connection, I suggest the scripts included in XP in
system32 to delete the connection, then add the new. You can set it as
default at the same time. If you set this up as a logon script you need to
run this in user context.

prnmngr -d -p "\\server\printer"

prnmngr -ac -p "\\server\NEWprinter"


cscript %windir%\system32\prnmngr.vbs /?
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

Usage: prnmngr [-adxgtl?][c] [-s server][-p printer][-m driver model]
[-r port][-u user name][-w password]
Arguments:
-a - add local printer
-ac - add printer connection
-d - delete printer
-g - get the default printer
-l - list printers
-m - driver model
-p - printer name
-r - port name
-s - server name
-t - set the default printer
-u - user name
-w - password
-x - delete all printers
-xc - delete all printer connections
-xo - delete all local printers
-? - display command usage

Examples:
prnmngr -a -p "printer" -m "driver" -r "lpt1:"
prnmngr -d -p "printer" -s server
prnmngr -ac -p "\\server\printer"
prnmngr -d -p "\\server\printer"
prnmngr -x -s server
prnmngr -xo
prnmngr -l -s server
prnmngr -g
prnmngr -t -p "\\server\printer"


--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Q]

Thank your for your reply Alan, much appreciated!

I will give it a shot.

Quinton

 

[Q]

Hi Alan,

I'm running into an issue when testing this...

When I execute the script while logged into the computer it works without
issues. When I set it up to run as a start up script, the script executes,
but when I login, nothing has changed. (the old printers are still there)

I wasn't at this particular company when the computer image was created, but
I'm suspecting that the printers were added to the Default user profile, and
whenever someone logs in, the profile is being copied therefore adding the
printers to the person logging in.

Could this be whats actually happening? If so, what would I have to do to
get it to work?


Regards
Quinton

 

[Alan Morris [MSFT]]

It's possible the network is not fully initialized when the script kicks in.
If you have Fast User Logon enabled I'd almost guarantee it. If the
printers where added as per machine connections using rundll32 and printui
interfaces, the printers will be sitting in the registry under

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Connections

you will need to use rundll32 to remove them



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Q]

Hi Alan, we run startup scripts all the time, so the network has to be fully
initialized. (We copy stuff to the PC's all the time)

I checked the registry and there is no /connections.

We have a profile called "make profile" which we alter, then copy it to the
Default user profile. I am currently logging in as the make profile account,
making the necessary printer adjustments, then logging out, then taking the
ntuser.dat file and copying it to

 

[Q]

The ntuser.dat file replacement seem to be working on my initial test. I have
to do a few more tests to make sure everything is ok.