Re: setup default printer machine wise

On Feb 2, 11:59 am, "Priya Raghavan [MSFT]"
<priy...@xxxxxxxxxxxxxxxxxxxx> wrote:
Hi,

Could you please confirm if this is the issue you are facing:

Client A has Printer A. User A logs from Client A to the TS server and the
redirected Printer A is the default printer on the session.
Client B has Printer B. User A logs from Client B to the TS server and the
default printer on the session is ??

When User A connects from Client B, then only the printers present on Client
B should be available on the session. He should not even see Printer A on
the session.

Also, what are the client and server OS ?
Does the server setting on Terminal Services Configuration allow multiple
sessions per user or just a single session per user ?

--

Thanks,
Priya.
TS Team Blogs:http://blogs.msdn.com/ts/

This posting is provided "AS IS" with no warranties, and confers no rights.

"neerajgs" <neera...@xxxxxxxxx> wrote in message

news:1170387865.334408.249150@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



Hi:

We have a large office with a thin client environment. Each of these
thin clients have printers - about 50 in all - attatched to them
(printing to standard tcp/ip port).

Time to time users need to move around from one department to another.
When ever they log in using another another client, their session is
transferred to that client. So far so good.

Issue is their default printer still remains the one attatched to
their own client.

How can we set it up, so that when a terminal server/rdp user logs in
using any thin client, the default printer is set to that particular
printer attatched to that particular thin client.

Also, is it possible to have a common address book for all users, so
all can access contacts using Outlook or Outlook Express?

Regards,
Neeraj- Hide quoted text -

- Show quoted text -

Hi Priya:

Thanks for your response. You have got that right. When User A logs in
from client B (with Printer B connected to it) he should see only the
Printer B connected to it without seeing Printer A during the session.

As I said earlier, it is a thin client environment (without hard disks/
Flash Module/DOM/anything else for that matter) and the operating
system of the server i.e. Windows 2003 server is seen on the login
screen.

The settings restrict each user to one session instead of multiple
sessions.

Appreciate your effort.

Regards,
Neeraj


.

Relevant Pages

  • Re: DHCP Problem
    ... Unable to contact a DHCP server. ... The client computer's logs are a mess due to not being able to renew ip ... Denied Connections started showing up in the ISA logs seconds ...
    (microsoft.public.backoffice.smallbiz)
  • Re: SSL/TLS & renegotiation and Internet Explorer
    ... When IE closes the connection with the server and prompts the user to choose ... recovery logic the SSL session is discarded. ... If the user only has one suitable client certificate, ...
    (microsoft.public.security)
  • Re: RDP Printing by station
    ... flagged as non-printing stations can not print for ANY users. ... multiple NIC's on the terminal server. ... I'd then just have to ensure that the client stations that are ... session is limited to NIC # 1. ...
    (microsoft.public.windows.terminal_services)
  • Re: VPN Error 733, Event Log Error 20050 with SBS 2003
    ... Is there anyone from Microsoft who has the tools to decypher the logs I ... client to the server, but not the other way around. ... as far as I'm aware you can't reinstall RRAS (I think you could ...
    (microsoft.public.windows.server.sbs)
  • SSL and IPS (was RE: ssh and ids)
    ... How many simultaneous SSL sessions can be tracked?" ... I assume you're talking about a case in which the client constantly ... If you walk the possible session id space and ... The server chooses the session ID, ...
    (Focus-IDS)