E
Ed
The current TS setup where I am is Win 2K SP2. All users
log in with the same user name & pw using Win2k Pro RDP 5.
I do not really understand any advantages for this except
to maybe print directly to anothers local printer while
they are connected to TS(except,this is not permitted).
What is now happening is when users log in, their local
default printer is created in TS but it is not always
selected as their TS default printer. It's kinda hit &
miss. So now they have to pick their printer out of the
hundreds that are there. This is usually after they have
printed and realized it went to another printer.
I believe each user should have a seperate ID for TS to
prevent this type of stuff from happening.
Is it a recommended practice to have all(hundreds) clients
log into TS with the same ID??
Any suggestions, comments??
Tks
log in with the same user name & pw using Win2k Pro RDP 5.
I do not really understand any advantages for this except
to maybe print directly to anothers local printer while
they are connected to TS(except,this is not permitted).
What is now happening is when users log in, their local
default printer is created in TS but it is not always
selected as their TS default printer. It's kinda hit &
miss. So now they have to pick their printer out of the
hundreds that are there. This is usually after they have
printed and realized it went to another printer.
I believe each user should have a seperate ID for TS to
prevent this type of stuff from happening.
Is it a recommended practice to have all(hundreds) clients
log into TS with the same ID??
Any suggestions, comments??
Tks