I am having an issue where users are logging into a W2K Server via terminal services to run applications whereby their printers are mapping across fine and are completely useable, but when they log off, the mapped "session" printers will remain. Thus, when they log on again and go to print, they will have:
/__server_printer/machine/session 1
/__server_printer/machine/session 2
/__server_printer/machine/session 7
etc etc
They therefore do not know which one is the current mapping to use (only one will work).
Printers are installed locally to a file server and shared, user then logs on via Terminal services to use certain applications to another server, hope that makes sense.
At the moment, when it becomes an issue we check which session ID the user is and clean out the mapped printers that DON'T match that ID, but this is a pain in the.....right foot.
Any suggestions?
/__server_printer/machine/session 1
/__server_printer/machine/session 2
/__server_printer/machine/session 7
etc etc
They therefore do not know which one is the current mapping to use (only one will work).
Printers are installed locally to a file server and shared, user then logs on via Terminal services to use certain applications to another server, hope that makes sense.
At the moment, when it becomes an issue we check which session ID the user is and clean out the mapped printers that DON'T match that ID, but this is a pain in the.....right foot.
Any suggestions?