Printer Deployment - Customise print server name?

Moltuae

Rest In Peace
Reaction score
3,669
Location
Lancs, UK
Info:

Windows Server 2012 R2 domain environment with numerous physical and virtual servers.

Users access their virtual desktops and remote apps via collections of Server 2012 R2 VMs.

I'm adding the print server role to an existing virtual server (2012 R2) that has other roles and a server name that relates to those existing roles. The printers are to be listed in the directory and deployed on a per user basis.

The question:

So, is there a way to customise the print server name that appears to the end user (eg to just 'Server') or, preferably, remove the print server's name all together? It's unnecessary information for the end user, it looks untidy and the name will likely just confuse these particular end users. I would prefer to just have the printer name (eg A4 Colour Laser) without the "on ... " (see below):

HrxB9ct.jpg






Also, what's the best way to tie users to specific deployed printers so that they only see the printers they need to use? Would creating printer groups in AD work for this, by making users member of the relevant groups?


Thanks
 
Well, both actually. If you use a GPO to automatically deploy printers then you don't have to worry about how they are listed as users won't have to worry about installing the correct one or why it's listed that way. Although some applications may still show the server name as part of the printer name.
 
If you use a GPO to automatically deploy printers then you don't have to worry about how they are listed as users won't have to worry about installing the correct one or why it's listed that way. Although some applications may still show the server name as part of the printer name.
Ah, you mean if the users are searching for and adding printers themselves, right? That's not what I mean. I'm not planning to leave users to add printers themselves, quite the opposite. I'm already deploying the printers from the printer server (using Print Management) on a per user basis and the plan is to restrict access to only the printers they use/need. It's the list of printers and their names, those presented to the user when he/she goes to print, that I'd like to simplify. I'd like the list to contain only the printers available to them, with simple names like 'A4 Colour Laser Printer'.
 
Doesn't Print Management tie the printers to a GPO when you use deploy in the print management console? And I'm sure you can set the printer name in the GPO.
 
Doesn't Print Management tie the printers to a GPO when you use deploy in the print management console? And I'm sure you can set the printer name in the GPO.
Thanks.

Good suggestion. It does but it appears that it only sets the printer name, not the "on Server_xyz" part. Oddly though, I can view the GPO that Print Management has created but I can't edit it since there's no 'Printer Connections' under 'User Configuration -> Policies -> Windows Settings' o_O




EDIT: I think I may have found which way I need to go with this; GPP:
https://deployhappiness.com/deploying-printers-with-group-policy-preferences/

https://community.spiceworks.com/to...he-on-server-portion-of-network-printer-names
 
Last edited:
Why do you not want it to show the server name? I think it makes sense that it shows that info so you know where the printer is being deployed from. Otherwise at a glance it just looks like a locally configured printer and may confuse someone trying to assist with troubleshooting. Its even more helpful in an environment that has multiple print servers so you know which server to check when you have issues. I think if you connect to any shared printer it will always display the name of the machine that it resides on. I dont use GPP a whole lot but I would assume if you setup a printer with GPP using the share name you would see the same results. If you use GPP to configure printers via IP address you are essentially telling the PC's that the GPP applies to to configure a bunch of local printers in which case you cant centrally manage print jobs or monitor print logs.
 
Got it working how I wanted it ..... well, sort of.

Haven't found a way to hide the server but I'm able to rename it, which is probably better in some ways.

Why do you not want it to show the server name?
The reasons for wanting to hide/rename it are rather petty really: The print server role has been added to an existing server that performs a few other, unrelated roles and the server's name reflects those roles. Seeing that server's name under each printer name was bugging me (I'm a bit OCD with things like that) and I felt it looked unprofessional, would likely confuse users or cause them to question it: "Why does my printer say it's 'on the-super-duper-server' ?".

Anyway, here's what I did:

  • Added the printers to Print Management in the usual way, but without Deployment.
  • Created a DNS CNAME Alias of PrintServer1, pointing to the server acting as the print server.
  • Used GPP to deploy the printers using \\PrintServer1\[printername].
  • Used Item-Level Targeting to specify which users/groups to deploy the printers to.

At this point the printers won't work using the server alias. To fix this, I ran this reg command (and had to reboot the print server for it to take effect):
Code:
reg add HKLM\SYSTEM\CurrentControlSet\Control\Print /v DnsOnWire /t REG_DWORD /d 1

Need to add more printers and do further testing yet, but it seems to be working:

wPIzW1X.jpg
 
I would caution against targeting specific users in a GPO. Simply because when you create a new user (who isn't a part of a group you targeted) and they need access to a printer, it would be a pain to go into the GPO to add them (and to remember all what you need to add them to). I would create resource groups for the printers, and then make groups or users members of the resource groups for the printers they need.
 
I would create resource groups for the printers, and then make groups or users members of the resource groups for the printers they need.
Thanks. That's probably how I will do it in the final production configuration. Still just testing yet.
 
Last edited:
Back
Top