How to manage a farm of terminal servers

  • Thread starter Thread starter Jassi
  • Start date Start date
J

Jassi

Guest
Hi,

We are planning to install 5 Windows 2003 Terminal Servers.How can we manage
all 5 using a single interface?This could help a user to select and login to
any of these servers
--
thanks
 
Re: How to manage a farm of terminal servers

You mean a load-balanced farm?
Check this out:

243523 - Using Terminal Server with Windows Load Balancing Service
http://support.microsoft.com/?kbid=243523

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SmFzc2k=?= <Jassi@discussions.microsoft.com> wrote on 14
feb 2008 in microsoft.public.windows.terminal_services:

> Hi,
>
> We are planning to install 5 Windows 2003 Terminal Servers.How
> can we manage all 5 using a single interface?This could help a
> user to select and login to any of these servers
 
Re: How to manage a farm of terminal servers

Hi,

No we don't need a load-balanced farm.

All the servers are independent.... What we need is an application or
technology that provides a centralized control on all the servers (i.e. it
shows all the terminal
servers in the network, what all users are logged on to each terminal
servers, allows us to change the user credentials etc).

I am not sure but I think one way is to make them a part of an Active
Directory and manage them using the Terminal Services Manager. Am I correct?

And can you suggest any other way to do that?
--
thanks
Jusvinder

"Vera Noest [MVP]" wrote:

> You mean a load-balanced farm?
> Check this out:
>
> 243523 - Using Terminal Server with Windows Load Balancing Service
> http://support.microsoft.com/?kbid=243523
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?SmFzc2k=?= <Jassi@discussions.microsoft.com> wrote on 14
> feb 2008 in microsoft.public.windows.terminal_services:
>
> > Hi,
> >
> > We are planning to install 5 Windows 2003 Terminal Servers.How
> > can we manage all 5 using a single interface?This could help a
> > user to select and login to any of these servers
>
 
Re: How to manage a farm of terminal servers

Yes, that's the standard setup. TS Manager will see all terminal
Servers in the domain, and you will be able to manage all sessions.
You can also install the 2003 AdminPack on an XP client which is a
member of the same domain, and manage the sessions from the XP
client.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?SmFzc2k=?= <Jassi@discussions.microsoft.com> wrote on 15
feb 2008:

> Hi,
>
> No we don't need a load-balanced farm.
>
> All the servers are independent.... What we need is an
> application or technology that provides a centralized control on
> all the servers (i.e. it shows all the terminal
> servers in the network, what all users are logged on to each
> terminal
> servers, allows us to change the user credentials etc).
>
> I am not sure but I think one way is to make them a part of an
> Active Directory and manage them using the Terminal Services
> Manager. Am I correct?
>
> And can you suggest any other way to do that?
 
Re: How to manage a farm of terminal servers

Thanks for your help.

I have one more question. If the Terminal Servers are not part of the AD or
AD doesn't exist, but they belong to same network.

Then whether TS Manager will be able to display the list of all the Terminal
Servers in the same network?

--
thanks
Jusvinder

"Vera Noest [MVP]" wrote:

> Yes, that's the standard setup. TS Manager will see all terminal
> Servers in the domain, and you will be able to manage all sessions.
> You can also install the 2003 AdminPack on an XP client which is a
> member of the same domain, and manage the sessions from the XP
> client.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?SmFzc2k=?= <Jassi@discussions.microsoft.com> wrote on 15
> feb 2008:
>
> > Hi,
> >
> > No we don't need a load-balanced farm.
> >
> > All the servers are independent.... What we need is an
> > application or technology that provides a centralized control on
> > all the servers (i.e. it shows all the terminal
> > servers in the network, what all users are logged on to each
> > terminal
> > servers, allows us to change the user credentials etc).
> >
> > I am not sure but I think one way is to make them a part of an
> > Active Directory and manage them using the Terminal Services
> > Manager. Am I correct?
> >
> > And can you suggest any other way to do that?
>
 
Re: How to manage a farm of terminal servers

I'm not sure, but I think it could work. My Terminal Servers (which
are members of an AD) are *not* published in the AD Catalog, like an
Enterprise TS Licensing Server can be published.

But on the other hand, you might not have enough permissions to see
the other servers, as there is no common account database, and your
login account on one server will have no rights on the other servers.
You'll have to try this out, I have never done it (who wants to be
without an AD?)

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SmFzc2k=?= <Jassi@discussions.microsoft.com> wrote on 15
feb 2008 in microsoft.public.windows.terminal_services:

> Thanks for your help.
>
> I have one more question. If the Terminal Servers are not part
> of the AD or AD doesn't exist, but they belong to same network.
>
> Then whether TS Manager will be able to display the list of all
> the Terminal Servers in the same network?
 
Re: How to manage a farm of terminal servers

If you're using windows 2003 Terminal Services Manager (TSAdmin), you can
manually connect to the machine you want, and add them to a group. Please
keep in mind that the user account you use must have proper permissions to
the machine you try to connect with tsadmin.
Thanks
Soo Kuan



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

"Jassi" <Jassi@discussions.microsoft.com> wrote in message
news:B324D22D-6D07-41D2-AE1A-1561B4DEF1F7@microsoft.com...
> Thanks for your help.
>
> I have one more question. If the Terminal Servers are not part of the AD
> or
> AD doesn't exist, but they belong to same network.
>
> Then whether TS Manager will be able to display the list of all the
> Terminal
> Servers in the same network?
>
> --
> thanks
> Jusvinder
>
> "Vera Noest [MVP]" wrote:
>
>> Yes, that's the standard setup. TS Manager will see all terminal
>> Servers in the domain, and you will be able to manage all sessions.
>> You can also install the 2003 AdminPack on an XP client which is a
>> member of the same domain, and manage the sessions from the XP
>> client.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?SmFzc2k=?= <Jassi@discussions.microsoft.com> wrote on 15
>> feb 2008:
>>
>> > Hi,
>> >
>> > No we don't need a load-balanced farm.
>> >
>> > All the servers are independent.... What we need is an
>> > application or technology that provides a centralized control on
>> > all the servers (i.e. it shows all the terminal
>> > servers in the network, what all users are logged on to each
>> > terminal
>> > servers, allows us to change the user credentials etc).
>> >
>> > I am not sure but I think one way is to make them a part of an
>> > Active Directory and manage them using the Terminal Services
>> > Manager. Am I correct?
>> >
>> > And can you suggest any other way to do that?
>>
 
Re: How to manage a farm of terminal servers

Thanks for your help.
--
Regards
Jassi


"Soo Kuan Teo [MSFT]" wrote:

> If you're using windows 2003 Terminal Services Manager (TSAdmin), you can
> manually connect to the machine you want, and add them to a group. Please
> keep in mind that the user account you use must have proper permissions to
> the machine you try to connect with tsadmin.
> Thanks
> Soo Kuan
>
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Jassi" <Jassi@discussions.microsoft.com> wrote in message
> news:B324D22D-6D07-41D2-AE1A-1561B4DEF1F7@microsoft.com...
> > Thanks for your help.
> >
> > I have one more question. If the Terminal Servers are not part of the AD
> > or
> > AD doesn't exist, but they belong to same network.
> >
> > Then whether TS Manager will be able to display the list of all the
> > Terminal
> > Servers in the same network?
> >
> > --
> > thanks
> > Jusvinder
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Yes, that's the standard setup. TS Manager will see all terminal
> >> Servers in the domain, and you will be able to manage all sessions.
> >> You can also install the 2003 AdminPack on an XP client which is a
> >> member of the same domain, and manage the sessions from the XP
> >> client.
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> *----------- Please reply in newsgroup -------------*
> >>
> >> =?Utf-8?B?SmFzc2k=?= <Jassi@discussions.microsoft.com> wrote on 15
> >> feb 2008:
> >>
> >> > Hi,
> >> >
> >> > No we don't need a load-balanced farm.
> >> >
> >> > All the servers are independent.... What we need is an
> >> > application or technology that provides a centralized control on
> >> > all the servers (i.e. it shows all the terminal
> >> > servers in the network, what all users are logged on to each
> >> > terminal
> >> > servers, allows us to change the user credentials etc).
> >> >
> >> > I am not sure but I think one way is to make them a part of an
> >> > Active Directory and manage them using the Terminal Services
> >> > Manager. Am I correct?
> >> >
> >> > And can you suggest any other way to do that?
> >>
>
>
 
Back
Top