1

Windows Server 2008 R2 Print Server - Change Printer Names on All Client Systems

view story
linux-howto

http://serverfault.com – I have a Windows Server 2008 R2 print server set up hosting out multiple printers to my end users. I would like to change the naming convention for all of the printers hosted on the print server and want this change reflected on the client end. For example: I have a HP4000 printer named "Cottage" on the print server. I want to rename the printer "HR-1stFloor-220a" on the print server and I want this printer to appear on every client system with the new name. Simply renaming the printer on the server automatically creates a link from the old printer name to the new one, so all the clients wo (HowTos)

xskl's picture
Submitted by xskl on 09/19/2012

Stories similar to Windows Server 2008 R2 Print Server - Change Printer Names on All Client Systems

RD Easy Print Slow 1 year 5 weeks ago

I have Windows 2008 R2 RDS (Terminal Server) hosting application using remoteapp.

Migrating Print Servers 30 weeks 4 days ago

Migrating Windows 2003 print server to Windows 2008 R2 print server. I have exported/imported the printers from old server to new. For the printers that wouldn't import I manually added them and gave them the same name that they have on the old server.

Right now I have left the "List in the directory" checkbox unchecked on the new server for each printer.

I have zero experience with XenApp, so please forgive my totally noob question.

I have just installed XenApp 6.5 with rollup update 1 on 2008R2 server, and client can connect to XenApp just fine. The problem is that when they need to print something, they can't see their printer. I don't want them to print on shared printer, since mostly they work from their home or wherever they are.

On our LAN I have one particular machine that seems to be clogging up the spooler/queue every time it prints to one particular printer.

Server 2008 Print Server; Win7 Box.

Every other machine can print to this printer fine. This machine can print to other shared printers fine.

What happens when it prints is the job is spooled and sent to the printer. The job prints.

Am I supposed to install Microsoft Windows Server 2008 x64 printer drivers on my 2008 32-bit server to support Windows 7 x64 clients while supporting Windows XP 32-bit clients?

I have a Microsoft Windows Server 2008 Standard (not R2) 32-bit server with the Print Services role. I have mostly 32-bit XP clients that are able to print to the server's shared printers.

Can anyone think of a way of Re-Sharing a Shared Printer? When I connect the shared printers to Server 2008 R2, it comes up as a network printer, and settings take affect on the host (not the server) so I can't Re-Share it.

The reason I need this is I have a number of workstations that run software in which I have to hardcode the printer name.

We setup a new 64bit Print Server (Server 2008 R2) and on our previous print server we had the helpdesk as a member of the power users group, and gave them "Manager Printers" so they could change printer ports when printers went down.

it looks like there was an oversight and it wasn't added when we setup the new server.

I've added them to power users, and went into Print Server Properties in "PR

All right, this is driving me nuts.

I have an HP Color LaserJet cm1312nfi connected to the ethernet jack on a D-Link DPR-1260 wireless usb print server - so the print server acts as a wireless bridge. I can't get any Ubuntu box to print to the LaserJet. Windows XP and Vista laptops on the network print to it just fine.

It has occurred to me that a workstation can connect to a printer in two ways: 1). Printing directly to the IP of the printer with the print driver installed locally. 2).