>Hi Al,
>
>Thanks for responding! This is a rather complicated problem that has been going on for a while but I'll try to distill it to the essentials.
>
>Absolutely everything in the environment is 32 bit. I don't know what version TS is, but it runs on Server 2003 and has for about a year, Workstations run XP SP2. All but 2 of the workstations show \\DC1\LASER in the APrinters() list except the 2 that are having trouble. Those have something like LASER ON DC1 (FROM FK0PBCX1) IN SESSION 18. Technically this is the same printer, but it would appear that the spooler is having trouble figuring that out. The print setup is much like you describe for 2b--printers are accessed from the server; nothing on the workstation is accessible once the user logs into TS. (That creates other problems but I'll save those are for another day!)
>
>I am pretty sure the problem is not with the printers themselves. The app has worked in its present configuration for over a decade and that printer has been used without error for a couple of years.. The problem started at with the first printjob on August 20 after Office 2010 was installed over the weekend. Under automation, the app calls the Word Print Setup Dialog to send printjobs to the selected printer. What has changed, apparently, is that while previous versions of Word would accept "Printer = Device" in that dialog, 2010 wants "Printer == Device". The spooler appears to have trouble finding the proper queue for jobs sent from the 2 non-conforming workstations. To me, it would seem easier to fix the problem at the workstation end than try to get Microsoft to modify their code :-) However, IT says the workstations can't be changed. I'm not sure why, except that I've observed that the fellow doesn't seem to be very energetic.
>
>So here's my question to you: is IT right that there is no way these workstations could use the \\DC1\LASER reference for that printer?

If the problem machines show, in a TS session, their printer as "LASER ON DC1 (FROM FK0PBCX1) IN SESSION 18", then that's an example of 2a, not 2b (assuming "FK0PBCX1" is the name of a problem workstation). The Remote Desktop client on those machines is still set to the default, which is to redirect print jobs back to the workstation. The appropriate options should be set in Remote Desktop on those problem machines so print jobs are not redirected back to the workstation.

Within the TS session, it should still be possible to set the printer to \\DC1\LASER rather than the above. However, if the TS sessions are locked down, the user may not be able to do that.