We can't seem to get any sort of acceptable printer management working via Windows technologies. I've come here looking to see what we did wrong, what we can do or fix to get this working, before we start homebrewing a solution.
Our Setup:
We currently have over 10 remote desktop session host terminal servers, servicing over 100 staff. Printers are physically located around the office, typically 8 staff to a printer. Staff are not assigned terminal servers in a geographical manner, so printers
must be managed on a user-by-user basis, not by computer.
We have a single 2008r2 print server with 20 or so printers.
Everything's in a single Active Directory domain, Domain and Forest functional level "Windows Server 2012 R2".
What we have tried:
Custom Group Policy:
We tried making group policies for each printer, defining "User Configuration>Preferences>Control Panel Settings>Printers". Action=replace, default=yes. Assign users to the security filtering to have this printer configured for them on
login to whatever terminal server they were assigned.
Problems:
Default printer would not always be set. Some programs would "lose" this printer, and we'd have to reconnect the printer for it to show in these programs again.These group policies would sometimes lock up the Group Policy Client Service, causing entire terminal servers to refuse logins until restarted.
Deploy with Group Policy:
We tried the standard "Deploy with Group Policy" context menu option direct from the print server Print Management pane.
Problems:
Printer would often be created as "Unspecified" device, and would be unusable. If printer was configured correctly, it would create a new, duplicate print spool after every login, which would not go away until the "Print Spooler"
service was restarted. (You'd see several identical options under the "See what's printing, Set as default printer" context menu options for a single printer)
Neither of these deployment strategies are acceptable. So, what can I do to get working printer management working?