We've got some 60 users spread across 3 RDS Servers all using Server 2008 R2. All users stick to their own RDS Server, only changing if there is an issue preventing them from connecting to it, and they use one of the others. All users see all of the print queues.
We set up all of the print queues in Print Management and then deployed them from there to a GPO using the 'per user' setting, but have noticed that there is quite a performance hit from how the printers were set up in our old 2003 server, where we had all printers set up as local printers. Performance hit as in - when they first log in it takes a while to populate all 25 print queues (yes 25 for 60 users - we have managed to cut this down from 40-50-odd in the old 2003 enviro!), and also if they do a resource intensive job, such as running a report that populates an Excel spreadsheet with data from our SQL Server - the report takes about 30secs to run. About 30 secs to 2 mins after the report has been finished - or they have logged onto the server they printers appear again.... gradually. Physical printing wise - there are no issues. Often if a user's default printer doesn't appear within a given timeframe, it will select the first printer on the list..... to the annoyance of the user!
So, how can I improve the speed at which printers populate? In terms of what processing is done, is the a difference between deploying by computer and deploying by user? From my reading I understand that when you update printer preferences it will by default auto update - by user it will do this for each user - does it do the same per computer? Or does it just do it once per computer? Is there anywhere else that we can gain performance in the GPO?
Please note - I'm not looking for 'stab in the dark' answers - I'm after informed, experienced advice in this field. We seem to be pioneers with this in our own circle of IT providers - but I can't believe that there isn't more experienced knowledge out there that we can tap!