We have a Windows 2012 R2 RDS farm with 3 RDSH servers, and network printers on a dedicated print server. Printers are deployed to users (User Configuration) via GPP Printers (apply once). Every once in a while, some random user will start having a problem printing to the main network printer (PRINT1) that everyone uses the most. When the issue happens, the user cannot print to PRINT1 at all. Most apps will act as if the job was sent, but nothing prints and no job is created. Notepad gives the following error: A StartDocPrinter call was not issued.
A key fact is that when the issue happens, it is only for that user and only the specific RDSH they were on. Other users can print to PRINT1 on the same RDSH server with the affected user, and the affected user can print to PRINT1 on the other RDSH servers. The issue remains for the affected user even if user logs off and on the affected RDSH. When the issue starts for a user, it starts in the middle of the session, not when they first logon. In other words, they would be printing fine to PRINT1 throughout the day, and the problem pops up in the middle of the workday without them having logged off and on. The affected user can print to other network printers on the same print server. The only way to fix is to delete and re-add the printer for the user.
We have roaming user profiles and redirected folders. Local profiles are removed from RDSH servers upon logoff. The problem doesn't seem to be just with the user because otherwise it would follow them to other RDSH servers, and the problem is not just with a RDSH server because other users do not have a problem on that server. We've tried removing and recreating the printer on the print server.
What printer setting/configuration is getting corrupted that is a combination of a user config and computer config? This is quite confusing. Any ideas what might be going on?