I have an issue with a HP M605 and HP M425 drivers that are not displaying correctly in server 2016. I have verified that the drivers work correctly on Win 10. The problem started yesterday. No changes were made to the RDP server they're using or the print server that controls this printer. So far I've: Made sure that the attributes are correct in ADSI Edit. Because it works on Win 10 I didn't see any reason to change anything. Verified it's not a user, gpo, or print server issue by creating a test user, test printer, test ou, and test printer all from scratch. The problem continues on Server 2016. Verified AD replication is working correctly. Verified the printer is listed in AD. I typically just share them but I listed it for testing. The correct share name shows up in the printer properties. The name the user sees is the driver. Unshared the printer, reset print spooler, shared it. Renamed printer Tested printer by manually connecting via print server and GPO. Same problem shows up. There is a recent update waiting to install. I'm going to run that tonight and reboot. I'm at the end of my rope here and I can't seem to find any good info on Server 2016 printer name issues. Has anyone seen this before? I'm also going to run updates on our print server and reboot it tonight as well.

Hi, I have done a lab test and found it is a by design behavior on server 2016 if you add a shared printer with the specific driver . The printer name will display as the driver name. But if the printer driver is a universal driver (such as HP Color LaserJet 1600 Class Driver) which is listed in the driver list, then it will display the printer name correctly. So, this problem should come from the printer driver. You can try another universal driver for a test. Thanks, Eleven ---------- If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

So far wiping and reloading the affected machines with the latest 21H1 SEEMS to be fixing the issue for me, I don't want to claim it's a good fix but is working in some areas.

The issue is still persisting with my company. However, we experienced two different models that were not of the original 3 started producing the same or similar issue as of yesterday. We had a plan to upgrade our Server 2019 last night anyways to Version 1809 Build 17763.2330 (KB5007266) as we saw it would fix some printer problems. Issue was not resolved with it and made some of our printers change our one-sided print preference to two-sided. Weirdly enough it was the HP LaserJet M501 that started printing the error sheet with the M501 PCL - 6 driver. With the server updated and machines updated to V 21H2 Build 19044.1387 (KB4023057) AND updates from HP Support Assistant the share name still breaks or an error sheet prints after the print job (both issues depending on a specific driver). HOWEVER, upon curiosity, my colleague installed Windows 11 to test its features. I've installed the problematic Lanier and HP M428 printers I've mentioned previously and tested both of the problematic drivers. The share name nor error sheet produced. I've tried my best to use all of the methods I've used to break and test, but it would not budge. This ultimately proves that within our environment our: server version, desktop version, group policies, and printer drivers are not the cause of the breaks that happen within Windows 10 and that it is the OS.

This has been a fascinating bug to watch. One of my earlier comments on this thread mentioned that the (at the time) Insider Previews for Win10 21H2 did not reproduce the issue. Well, now that Win10 21H2 is out, the final build does reproduce the issue. So that's fun... However, same as @Morgan Cotten , I can't seem to reproduce it on Win11 either. Everything shows up with their share name as expected.

Has anyone come up with a resolution or workaround? We are experiencing this issue on 2019 Server. RICOH printers. All the printers are the same driver. It's literally driving my staff to madness. We have to manually install the printers on each laptop. I have had it come up correctly on FRESH windows 10 installs. Just weirdness.

Server 2016 Displays Driver Name Of Shared Printer Instead Of Share Name

Joe Hinkle 141

I have an issue with a HP M605 and HP M425 drivers that are not displaying correctly in server 2016. I have verified that the drivers work correctly on Win 10.

The problem started yesterday. No changes were made to the RDP server they're using or the print server that controls this printer.

So far I've:

Made sure that the attributes are correct in ADSI Edit. Because it works on Win 10 I didn't see any reason to change anything.
Verified it's not a user, gpo, or print server issue by creating a test user, test printer, test ou, and test printer all from scratch. The problem continues on Server 2016.
Verified AD replication is working correctly.
Verified the printer is listed in AD. I typically just share them but I listed it for testing.
The correct share name shows up in the printer properties. The name the user sees is the driver.
Unshared the printer, reset print spooler, shared it.
Renamed printer
Tested printer by manually connecting via print server and GPO. Same problem shows up.

There is a recent update waiting to install. I'm going to run that tonight and reboot. I'm at the end of my rope here and I can't seem to find any good info on Server 2016 printer name issues. Has anyone seen this before?

I'm also going to run updates on our print server and reboot it tonight as well.

Anonymous

2020-12-04T04:39:00.17+00:00

Hi,

Can you share the screenshots showing the printer drivers used in the print server and the problematic 2016 server? Are they the same on both servers?

How did you add the shared printer on the server 2016? Have you tried to run "\IP address", or add a printer on control panel to add the printer?

Thanks,
Eleven
Chandler, Andrew 6 Reputation points

2021-03-18T16:58:17.807+00:00
Hi @Joe Hinkle

Came across your post because we're seeing this exact same thing with a small number of HP printers and Server 2012 R2 print servers.

Printers install fine via GPO, but after some amount of time or first reboot, a couple printers change their name in Control Panel to the name of the driver. Printer names show up correctly in applications' print dialogs.

Updating the type 3 drivers used by these shares to their latest version did not change this behavior.

We have 1,000+ printer shares, hundreds of which are device-specific type 3 HP drivers. Not all shares exhibit this symptom by a long shot, so I question this being "as designed" as mentioned by @Anonymous .

Affected clients for now seem to only be Win10 20H2. I can't reproduce this problem on a Win10 1909 machine even with current updates (build 18363.1441).
Chandler, Andrew 6 Reputation points

2021-03-18T19:52:58.647+00:00

Another piece of info -- I upgraded my 20H2 VM exhibiting this bug to the latest Insider Dev build. I can now no longer reproduce this behavior.

So it seems that this is a quirk with 20H2, or one of its cumulative updates. (Possibly 2004 too since it only differs from 20H2 by an enablement package... but I have not tested it)
Morgan Cotten 6 Reputation points

2021-12-08T22:41:16.013+00:00

The issue is still persisting with my company. However, we experienced two different models that were not of the original 3 started producing the same or similar issue as of yesterday. We had a plan to upgrade our Server 2019 last night anyways to Version 1809 Build 17763.2330 (KB5007266) as we saw it would fix some printer problems. Issue was not resolved with it and made some of our printers change our one-sided print preference to two-sided. Weirdly enough it was the HP LaserJet M501 that started printing the error sheet with the M501 PCL - 6 driver. With the server updated and machines updated to V 21H2 Build 19044.1387 (KB4023057) AND updates from HP Support Assistant the share name still breaks or an error sheet prints after the print job (both issues depending on a specific driver).

HOWEVER, upon curiosity, my colleague installed Windows 11 to test its features. I've installed the problematic Lanier and HP M428 printers I've mentioned previously and tested both of the problematic drivers. The share name nor error sheet produced. I've tried my best to use all of the methods I've used to break and test, but it would not budge.

This ultimately proves that within our environment our: server version, desktop version, group policies, and printer drivers are not the cause of the breaks that happen within Windows 10 and that it is the OS.

Accepted answer

Anonymous

2020-12-08T08:13:04.603+00:00

Hi,

I have done a lab test and found it is a by design behavior on server 2016 if you add a shared printer with the specific driver. The printer name will display as the driver name.

But if the printer driver is a universal driver (such as HP Color LaserJet 1600 Class Driver) which is listed in the driver list, then it will display the printer name correctly.

So, this problem should come from the printer driver. You can try another universal driver for a test.

Thanks,
Eleven

----------

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

13 additional answers

Justin Vaughn 1 Reputation point

2021-09-26T13:11:28.683+00:00

So far wiping and reloading the affected machines with the latest 21H1 SEEMS to be fixing the issue for me, I don't want to claim it's a good fix but is working in some areas.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Morgan Cotten 6 Reputation points

2021-12-08T22:37:04.277+00:00

The issue is still persisting with my company. However, we experienced two different models that were not of the original 3 started producing the same or similar issue as of yesterday. We had a plan to upgrade our Server 2019 last night anyways to Version 1809 Build 17763.2330 (KB5007266) as we saw it would fix some printer problems. Issue was not resolved with it and made some of our printers change our one-sided print preference to two-sided. Weirdly enough it was the HP LaserJet M501 that started printing the error sheet with the M501 PCL - 6 driver. With the server updated and machines updated to V 21H2 Build 19044.1387 (KB4023057) AND updates from HP Support Assistant the share name still breaks or an error sheet prints after the print job (both issues depending on a specific driver).

HOWEVER, upon curiosity, my colleague installed Windows 11 to test its features. I've installed the problematic Lanier and HP M428 printers I've mentioned previously and tested both of the problematic drivers. The share name nor error sheet produced. I've tried my best to use all of the methods I've used to break and test, but it would not budge.

This ultimately proves that within our environment our: server version, desktop version, group policies, and printer drivers are not the cause of the breaks that happen within Windows 10 and that it is the OS.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Chandler, Andrew 6 Reputation points

2021-12-08T23:13:52.92+00:00

This has been a fascinating bug to watch. One of my earlier comments on this thread mentioned that the (at the time) Insider Previews for Win10 21H2 did not reproduce the issue. Well, now that Win10 21H2 is out, the final build does reproduce the issue. So that's fun...

However, same as @Morgan Cotten , I can't seem to reproduce it on Win11 either. Everything shows up with their share name as expected.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Nikole Goodrich 1 Reputation point

2022-04-11T14:20:01.19+00:00

Has anyone come up with a resolution or workaround? We are experiencing this issue on 2019 Server. RICOH printers. All the printers are the same driver. It's literally driving my staff to madness. We have to manually install the printers on each laptop. I have had it come up correctly on FRESH windows 10 installs. Just weirdness.
Please sign in to rate this answer.
Tyler 6 Reputation points

2022-04-13T21:43:56.82+00:00

We use a lot of Ricoh printers in our environment too. We tried implementing V4 drivers to mitigate the issue but that did not go well either. We basically abandoned the print server and started deploying printers through SCCM via Powershell scripts. Since you are using Ricoh printers, you could also look at building software packages for the printers using Ricoh's driver packager:

https://www.ricoh-usa.com/en/products/pd/software/device-set-up-and-management/device-usage-and-monitoring/ricoh-printer-driver-packager-nx

It can export a printer install to MSI or EXE. Again these could be deployed using SCCM or another endpoint management solution. Hope this helps.

Nikole Goodrich 1 Reputation point

2022-04-14T13:28:14.053+00:00

Thanks for the information. That is what I am coming to the conclusion of doing. I found PDQ has a blog but advertises their scenario of adding a printer via PS. I'm inclined to believe a script can be made without third party invention.

The other work around if I could figure it out is the Registry Edit portion. The location where it fails is here: HKLM>System>Currentcontrolset>ENUM>SWD>PRINTENUM> {Key}> ConfigFlags SET to 0. The printers will show up after a reboot correctly.

Each printer has a special {key} so you can't just add this to GPO, it'll not replicate correctly.

Here's another post I was watching for sometime last year. Still has traction.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Server 2016 Displays Driver Name Of Shared Printer Instead Of Share Name

13 additional answers

Your answer