We recently moved away from a 2008 Print Server to a 2008 R2 print server. We deploy our printers via GPP to our Session Host farm and they are ILT'd based on various factors. Occasionally, we will have end users call in saying they cannot print their document. This happens with different applications: Word, Excel, Adobe. The fix is to remove the printer from their session and then just re-add the same printer. I do have Point and Print restrictions in place: Forcing users to only print to 1 print server and 'do not show warnings....' is set for the bottom 2 options.
The move to the new Print Server was not a migration from the 2008 server. I installed all new print queues on the 2008 R2 server. I've set each print driver on the new print server to 'Isolated' in the Driver Isolation column and do not have any Group Policy set for PDI.
Could someone explain why occasionally users have to remove the printer device and then re-add the same printer in order to print?
Edit - I should also note that this issue is occurring on different Session Hosts in the farm and occurring from different printers using different drivers (Canon/HP).
Edit #2 :-) - I also want to say that the session appears to print the document, in the fact that the printing balloon appears in the users system tray and the document name/file size appears in the print queue on the Print Server, but nothing prints to the printer. I'm not sure at this point if the document name disappears from the print queue on the Print Server.