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

Question

question

JoeHinkle-7763 asked Dec 3, '20 NikoleGoodrich-1294 commented Apr 14, '22

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

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:
1. 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.
2. 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.
3. Verified AD replication is working correctly.
4. Verified the printer is listed in AD. I typically just share them but I listed it for testing.
5. The correct share name shows up in the printer properties. The name the user sees is the driver.
6. Unshared the printer, reset print spooler, shared it.
7. Renamed printer
8. 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.

windows-server-2016 windows-server-print

· 4

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ElevenYu-MSFT · Dec 04, 2020 at 04:39 AM

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

0 ·

ChandlerAndrew-3733 · Mar 18, 2021 at 04:58 PM

Hi @JoeHinkle-7763

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 @ElevenYu-MSFT.
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).

0 ·

screenshot-2021-03-18-110843.png (382.7 KiB)

ChandlerAndrew-3733 ChandlerAndrew-3733 · Mar 18, 2021 at 07:52 PM

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)

0 ·

screenshot-2021-03-18-144507.png (287.6 KiB)

MorganCotten-1205 · Dec 08, 2021 at 10:41 PM

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.

0 ·

Answer 1 · 2020-12-08T08:13:04.603Z

ElevenYu-MSFT answered Dec 8, '20 ElevenYu-MSFT edited Dec 8, '20

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.

image.png (78.9 KiB)

image.png (69.5 KiB)

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 2 · 2020-12-07T14:01:39.163Z

JoeHinkle-7763 answered Dec 7, '20 JoeHinkle-7763 edited Dec 7, '20

It doesn't matter how you add the printer it always shows up as the driver name whether its GPO, manually using the UNC path, or powershell.

The name of the printer is correct in all the configs. It's just the display name in Windows. I have verified it only does this on the 2016 servers. I've also ran win updates and verified it does not help on both the RDP and print server.

55.png (52.5 KiB)

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 3 · 2020-12-08T13:46:47.677Z

JoeHinkle-7763 answered Dec 8, '20 ElevenYu-MSFT commented Dec 9, '20

Thank you for your response. I'll try another driver and see what we can do. This will have to be scheduled for after hours work and due to holidays coming up it may take a bit for us to get up to date.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ElevenYu-MSFT · Dec 09, 2020 at 01:28 AM

OK, if you have any further update, you can post it in this thread.

0 ·

Answer 4 · 2021-06-05T17:18:26.567Z

ACE336-0053 answered Jun 5, '21 JustinVaughn-2196 commented Sep 24, '21

Any luck with this? Seeing the same issue with the HP Universal Print drivers and Ricoh universal drivers where it displays the printer by the driver version and not the share name. It also takes a while for the printers to install. It started on Win 10 2004 and 20H1, on both new and upgraded installs. This print server is hosted on Server 2019, but we saw the same behavior on Server 2012 R2.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JustinVaughn-2196 · Sep 24, 2021 at 05:45 PM

I am seeing this issue on Windows 10 21H1 with HP printers shared from Server 2012R2 printer server, and contrary to the other user, the HP Universal Print Driver show as the printer name

0 ·

Answer 5 · 2021-06-30T17:09:59.033Z

HGRitticuss answered Jun 30, '21

ElevenYu placed an answer yet I have questions onto why this is even happening in the first place by design. Our servers were updated to Windows Server 2019 two weeks ago. I have one user out of 40 in our office that are affected by this issue. The rest of the users are getting the printers by name not driver so I cannot see this being “by design” when the rest of the staff in the office have the three RICOH printers mapped exactly by the name given in the Share this Device properties.

EDIT: I failed to mention that if this one particular user goes into any Microsoft Office product the printers show up correctly there - no driver is shown.

Double Edit: go to https://docs.microsoft.com/en-us/answers/questions/117586/windows-10-2004-printer-displaying-issue.html for the real reason this doesn't work. It's either RICOH or Microsoft. Both companies need to communicate to each other, already.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 6 · 2021-06-30T17:15:27.153Z

ChandlerAndrew-3733 answered Jun 30, '21 JustinVaughn-2196 commented Sep 24, '21

I've resigned myself to just waiting on Win10 21H2 and Win11 to fix this in due time, since this bug has not been been reproducible in either's Insider preview. If it's still ongoing this long and already fixed in previews, I doubt it gets backported to 21H1/20H2/2004.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JustinVaughn-2196 · Sep 24, 2021 at 05:46 PM

I cannot consistently reproduce this issue at all, but we are seeing it a lot in one lab, it's very baffling but it's happening in Windows 10 21H1 and agree, hopefully it's fixed soon

0 ·

Answer 7 · 2021-08-18T20:45:24.763Z

MorganCotten-1205 answered Aug 18, '21 JustinVaughn-2196 commented Sep 24, '21

Unfortunately majority of our computers are on 20H2 and 21H2 with a print server on Windows Server 2019 with the printers deployed via group policy. Thinking this was only specific model of HP's printers, HP provided a universal print driver, but it acted the same as the Type 3 driver we had. So both Type 3 and Universal drivers act the same way with not showing the share name. We have also seen this on specific Konica Minolta's and Laniers. Has anyone found a resolution yet to both these problems?

universal-driver.png (27.6 KiB)

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JustinVaughn-2196 · Sep 24, 2021 at 05:47 PM

Same here and quite often the printers are taking FOREVER to install, this is very bizarre

0 ·

Answer 8 · 2021-08-20T13:24:11.757Z

DeanPoirier-8152 answered Aug 20, '21 NoahCarlisle-3062 commented Sep 1, '21

I'm seeing this as well, and only with our HP LaserJet Pro M501's. We have a number of Samsung ProXPress devices and Sharp MFP's and they are all fine.

The more critical piece to this from my perspective is that the users can't set these devices as Default Printers or look at the printer properties because the system throws an error "Printer properties cannot be displayed. The system call level is not correct."

Printers appear correctly in any application and are useable, but can't manage them at all. All of my workstations are running Win 10 20H2. I didn't really take note, but it certainly feels like this issue was introduced when I moved to 20H2.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

NoahCarlisle-3062 · Sep 01, 2021 at 07:54 PM

Dean, I was able to fix this by opening printers through the control panel, then if you just click and set on of the printers as default, the name will appear. If it is not correct, you can try setting a different one as default and then you will se it's actual share name.

0 ·

Answer 9 · 2021-09-01T19:52:23.703Z

NoahCarlisle-3062 answered Sep 1, '21 JustinVaughn-2196 commented Sep 24, '21

We are also having this same issue. Have been for about a year or so. We have the same setup as Morgan above and are using Ricoh printers.
I'm assuming no one still has a fix yet?

· 4

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MorganCotten-1205 · Sep 10, 2021 at 09:21 PM

Noah,

I have a case open with MS, but we are at a standstill with how we want to solve it.

However, what they have given me is that if you go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SWD\PRINTENUM select the folder below of the printer you want to correct (the folder's dwords will have a name FriendlyName or LocationInformation with Data of your printer's sharename), edit ConfigFlags to a value of 0. After a print spooler restart, the printer should show the correct share name.

The only catch is that once you remove the printer it removes that registry folder from PRINTENUM and when it adds back, ConfigFlags revert to a value other than 0.

To fix the catch, we tried implementing a group policy that sets a ConfigFlag on the PRINTENUM folder itself and set it to 0. Unfortunately, this doesn't override the printer's registry folder's keys. I have given them captured logs of the issue reproducing and after over a week, they didn't find anything wrong happening. It could be one of our policies denying it, a computer configuration, or something with our print server, but I doubt it as this is just now happening.

Here is another thread that is going through the same thing, but with a Ricoh printer and I wish I had known about the ConfigFlag fix they had mentioned before calling MS.
https://docs.microsoft.com/en-us/answers/questions/117586/windows-10-2004-printer-displaying-issue.html?page=3&pageSize=10&sort=oldest

0 ·

NoahCarlisle-3062 MorganCotten-1205 · Sep 13, 2021 at 01:53 PM

Great news that someone is still working on this. Thanks for your reply Morgan. I have our MSP working on this as well. Not sure where they are with it but it's been open several times over the last 6 months or so.

Using GPO was the first thought I had when reading your reply. These printers are installed every time a user logs in due to it being a group policy. So if the services need to be restarted after the registry entry is entered but after the printers are installed, then I wonder what the best way to force a restart of the print spooler after login. Sounds like it has to be lined up just right.

Hopefully MS finds what broke this and fixes it. I'm wondering if it has something to do with a network domain configuration and an update to 20H2 on Windows 10 that causes this. If it was every windows 10 update regardless of domain setup, I think it would be a bigger deal. But this wasn't that hard of an issue to find.

Please keep me posted! If I find anything I will do the same. I'm going to try some of these workarounds.

1 ·

MorganCotten-1205 MorganCotten-1205 · Sep 10, 2021 at 09:25 PM

The third page of the thread has a recent reply from someone in July that has created a schedule task to update the system's ConfigFlags every hour. I'll be putting it on my list to try, maybe it would be helpful to you.

0 ·

JustinVaughn-2196 MorganCotten-1205 · Sep 24, 2021 at 05:48 PM

This would not work for our scenario, students come into a lab 5 seconds before their class, sit down, print a job and then off to their class. We need a fix that would take effect immediately.

0 ·

Answer 10 · 2021-09-26T13:11:28.683Z

JustinVaughn-2196 answered Sep 26, '21 MorganCotten-1205 converted comment to answer Dec 8, '21

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.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question