We have a server 2008r2 terminal server farm consisting of 3 members. Our users are connecting via web to access programs, they do not use RDP for a desktop experience.
Most of our users have local usb printers, which with a combination of RD easy print and defined drivers are able to have their default printer re-directed to their sessions without too much hassle.
The problem is that some of our users do not have a locally connected printer, instead they have a networked printer for their use.
The issue is that when we had these defined locally they were not performing correctly - trays were not translating across, duplexing units were not working, printing multiple copies wasn't working. So instead we had the printers defined on the terminal server and people are able to print quite happily.
The problem is that the default printer is not able to be defined for these users and is a source of frustration.
I have tried logging in to an RDP session as the user and defining the default printer in the list but this does not stick on new sessions. I understand that this is because default printers and redirection is on a per session not per user basis now.
I have also tried unchecking the box in AD environment tab and unchecking the 'default to main client printer' box but this also appears to have no effect.
In my searching I have heard mention of GPOs and registry entries but none seem to correlate to this specific issue.
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows\SessionDefaultDevices\<SESSION_SID>
For example, would suggest that there is not a way to define on a per user basis what their default printer is going to be.
In summary:
Terminal server environment accessed through RDweb, users not using local printers are unable to define a default printer that is listed on the terminal servers.
Hope someone can help with this issue.