If you print to a local printer in a Win2K Terminal Service session against a Win2K machine, the Win2K machine does not restore the default printer properly. I can't determine exactly what the pattern for selecting the new default printer is, but it does always select the same (wrong) one.

I saw (in 2000) that users of thin clients in our office would lose their default printer after they logon at home where they have a local printer. When they logon in the office to their thin client Windows would assign them the first printer (in alphabetical order) as their default printer

I haven't had this problem in a while, so maybe it's fixed in 2003. The workaround I had was to make sure there weren't any other network printers in their profile (that they didn't need) which were before their default printer (in alphabetical order

More Printing info here

http://www.workthin.com/tsp.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- wendyg wrote: ----

If you print to a local printer in a Win2K Terminal Service session against a Win2K machine, the Win2K machine does not restore the default printer properly. I can't determine exactly what the pattern for selecting the new default printer is, but it does always select the same (wrong) one.