arstacey
November 18th, 2004, 05:15 PM
This will be long so please be patient with me.
Problem 1. I have 52 computers that log into a server running Windows Server 2003 using TS. Normally everything works fine but occasionally they will begin printing to another printer on a computer in another city. Does anyone know of a way to make sure that a single computer can only be redirected to a single printer?
Is there any way to assign sessions so that when a user logs in, that user logs into TS using the same session every time and their printer connects to that session and that session only?
Are there any third party programs that would do this for me?
Problem 2. Most of our computers can log in to TS and stay in all day, but a few locations will lose their connection and be unable to get back in without logging off TS and then logging in again. This causes a major problem as their TS Desktop may be frozen in which case they must contact me to go in and manually log them off. I know in Server 2000 you could make changes to the keep alive requests to help with this but can fing no instructions on how to do this with 2003. This instructions for 2000 do not work (the registry keys listed aren't in 2003).
I have exhausted all my resources and am hoping one of you may have an answer.
Thanks!
Problem 1. I have 52 computers that log into a server running Windows Server 2003 using TS. Normally everything works fine but occasionally they will begin printing to another printer on a computer in another city. Does anyone know of a way to make sure that a single computer can only be redirected to a single printer?
Is there any way to assign sessions so that when a user logs in, that user logs into TS using the same session every time and their printer connects to that session and that session only?
Are there any third party programs that would do this for me?
Problem 2. Most of our computers can log in to TS and stay in all day, but a few locations will lose their connection and be unable to get back in without logging off TS and then logging in again. This causes a major problem as their TS Desktop may be frozen in which case they must contact me to go in and manually log them off. I know in Server 2000 you could make changes to the keep alive requests to help with this but can fing no instructions on how to do this with 2003. This instructions for 2000 do not work (the registry keys listed aren't in 2003).
I have exhausted all my resources and am hoping one of you may have an answer.
Thanks!