Re: How to menage feew MS TS from one console.. ?

Well, the Terminal Services Manager offer the option to connect to as many computers as you like. You shouldn't even have to login to another computer to look at the connections to it (it uses winsta to produce the list if memory servers).

If you do Action->Connect To Computer for the three computers in question, all you should need to do is right click the particular user session and select "Remote Control". If that's not enough, I'm not sure what the problem is. I've never done a forceful Remote Control, so I'm not sure what setting need to be in place ahead of time, but it should not be quite as complicated as you make it out to be.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"TTT_TTT" <bbbb@xxxxxxx> wrote in message news:Od0zuW1OHHA.4604@xxxxxxxxxxxxxxxxxxxxxxx
So when I'll need make "Remote Control" for user I'll search user... ok I'll find, next I have to login to selected server and from Terminal Service Manager take control. There is no any way to made this from one TS Manager control? So My HelpDesk Team have to "jump" between TS Menager, or just have open all three Terminal Service Manager, 3 consoles.

"Josh Rosenberg [MSFT]" <joshrose@xxxxxxxxxxxxxxxxxxxx> wrote in message news:0B234628-EAD8-4E47-B36C-D9EC17EDF397@xxxxxxxxxxxxxxxx
Well, one way of searching would be using the command line utility "qwinsta"

It won't give you control, but it will quickly enumerate the users at a remote computer without requiring a full logon.

For example, if you want to find user "foo" among servers "barA", "barB" and "barC", you could type the following command lines:
qwinsta foo /SERVER:barA
qwinsta foo /SERVER:barB
qwinsta foo /SERVER:barC

Obviously, this could be automated fairly easily with a .cmd, .bat or Perl script; if you wanted to go overboard you could have the script automatically launch mstsc connections based on where the user was found.

Does this work for you?

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"TTT_TTT" <bbbb@xxxxxxx> wrote in message news:O4V8gj0OHHA.4992@xxxxxxxxxxxxxxxxxxxxxxx
OK so: I have 3 Terminal Services all are runing at: Windows 2003 Server Standard Edition.
Some users are connected to first server, some to second and the rest are connected to third TS.
Now I'd like to find user "ThomasD", and when I connect to Terminal Servicec Manager I see only Users from this server where I'm login, I don't see users from another server ( Just I don't have access to two others servers from this console, only I have acces to user from current server where I'm login).
What shoul I do to fast find and connect to user "ThomasD" from one console (I don't know where "ThomasD" is longin (it may be firs, second or third TS). How can I manage users (I'd like to get remote control) from one Terminal Console, for all users at third TS. I don't want login manualy at each TS and search for user.
I hope that I describe this problem more clear.

Best Redgards
Bildos


"Josh Rosenberg [MSFT]" <joshrose@xxxxxxxxxxxxxxxxxxxx> wrote in message news:ea2IOX0OHHA.780@xxxxxxxxxxxxxxxxxxxxxxx
Could you please try restating/rephrasing your question and providing more details? I don't understand your precise problem, so I'm not sure how to help.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"TTT_TTT" <bbbb@xxxxxxx> wrote in message news:ORZc2fzOHHA.3552@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
I have feew Servers MS Windows 2003 Terminal Services.
I add all servers to one console. I see all servers, but I can from this console connect only to sessions users from server where I'm currently login. When I try to get acces to another server I recive Info about: "you are noe autenticated to this server", When I want to get access to sesion from another sever I have to login to this server, open Console at this server an I get acces, but I have only acces to session from current sever.
How can I configure my terminal server console to get acces for all users from all TS server from all consoles.
Do we have DC (DomainControler) ? Yes we have :)

Redgards









.

Relevant Pages

  • Re: Cannot connect to console on two servers using RDP
    ... Is there an active session at the console? ... MCSE, CCEA, Microsoft MVP - Terminal Server ... >> permit remote control, you receive the following error message: ... Click the Terminal Services folder. ...
    (microsoft.public.windows.terminal_services)
  • Re: does not permit you logon interactively
    ... Since this problem has no relation to terminal Services (you can't ... I assume that you try to logon to the console with a Domain ... member server to gain access to it. ... > console or remote logins ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Cannot connect to console on two servers using RDP
    ... Windows Server 2003 Terminal Services ... The requested session is not configured to allow ... Click the Terminal Services folder. ... > Having problems connecting to console session of Terminal ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote Access Confusion
    ... Can you still login to console as Administrator? ... > to access 192.168.16.2 from the local server or from a local workstation, ...
    (microsoft.public.windows.server.sbs)
  • Re: Licensing - Remote Desktop for Administration
    ... So this sentence says that TS licensing is independent from OS ... It is not possible to have more than one console session (for ... If you use Terminal Services, *all* normal connections need a TS ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
Quantcast