1

We have the following setup:

Windows 2012r2 Remote desktop server (x1) Windows 2012r2 Print server

Network printers are added once to the print server
Printers are installed to users remote desktop session by them navigating to \print_server and right clicking to connect to a printer.

Sometimes (and it seems to be only affecting one printer) we are getting print failures.

When I investigate the user, I can see that the same printer appears to have multiple versions of itself listed, but not duplicated in the control panel.

See screenshot. (domain name blanked out)

Duplicate printer display

I cannot see duplicate printers in the print server, its only listed once, and it only seems to happen to one or two users.

I don't have any group policies in place to push printers, or logon scripts.

Its a fairly simple setup as we only have approx 30 staff and only about 10 of them use our network etc.

Some additional information:

  • We only allow a user one session, they always reconnect to it
  • print redirection is off on the connections (so not a local instance of the printer)
  • We get the issue that the printer will not print until deleted, and re-added - gives various errors, even though it shows as connected / on etc.
Alex Hellier
  • 131
  • 5
  • I wonder if they are just from remote sessions that have not been logged off – Drifter104 Dec 17 '15 at 13:33
  • @Drifter104, how would this be? Its only showing on one or two users. They are not re-directed printers.? – Alex Hellier Dec 17 '15 at 13:34
  • Maybe they are just bad a logging off. Simple answer be to look to see if they have multiple sessions open – Drifter104 Dec 17 '15 at 13:39
  • We have rds set to reconnect to the same session and only 1 session per user? – Alex Hellier Dec 17 '15 at 13:42
  • That's the type of information that belongs in the question – Drifter104 Dec 17 '15 at 13:49
  • I found this: http://social.technet.microsoft.com/Forums/windowsserver/en-US/71d06204-3735-4473-8bc9-20be9e19090e/ The problem seems to have something do to with client side print rendering. The fix recommended was to delete the print server out of the "Servers" key in this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\Servers – Art.Vandelay05 Dec 17 '15 at 14:54
  • Then restart the spooler service, which greys out all the offending printers in "Devices and Printers". After that its just a matter of deleting the greyed out printers from your "Devices and Printers" control panel. Note: I have not tested this. I am only relaying information gleaned from a discussion. – Art.Vandelay05 Dec 17 '15 at 14:54
  • @Art.Vandelay05 , thanks, I too saw that , but was hesitant to start hacking around in the registry as it was not quite the same issue as I have had - I may give it a go after the christmas rush if I don't find another solution. Thanks – Alex Hellier Dec 17 '15 at 15:05
  • You're welcome. I understand your hesitation to hacking around in the registry since the situation isn't exactly the same as yours. – Art.Vandelay05 Dec 17 '15 at 15:08
  • Your screenshot has everything blacked out so there's no way for us to know what's what. Are the other printer "instances" being redirected via RDS to the user sessions? – joeqwerty Dec 17 '15 at 17:48
  • @joeqwerty -> I just blanked out the domain name, the other printers are fine. Its just the **KH Despatch** printer, which, when you select properties, shows exactly the same text, multiple time. – Alex Hellier Dec 17 '15 at 17:53

0 Answers0