Re: using Terminal server for applications management
- From: Laurent Dumont <utilisateur@xxxxxxxxxxxx>
- Date: Mon, 24 Nov 2008 12:10:51 +0100
Thanks for you answer.
You're right, they find that 2 sessions are'nt enough to work, because there are tree to work, and sometime i have to get a session too.
They are doing application management using stuff like cygwin (unix like shell), non-remote GUI self made applications and other stuff like that...
I agree with you when you tell that it is risky to install terminal services, but without proof, like microsoft paper or something like that, they don't want to trust me....
I have to confess that actually on Windows 2k, they already use terminal services without any troubles, and they dont understand that, because of a migration on windows 2003, they can not use terminal services any more, except because they changed the IT Manager :)
So I have to prove that it is a real bad idea to do that, and get some proofs...
Thanks,
Laurent
Vera Noest [MVP] a écrit :
I would certainly *not* install Terminal Services on a server which has any other role, like being a database server, domain controller, exchange server or whatever. Installing Terminal Services changes many things on the server, amongst others the way the server is tuned internally for optimal performance..
And you will also receive a warning that *all* existing software on the server can potentially stop working when you install TS. Not sure that you want that :-)
I'm not completely clear about why your team wants TS. Maybe because the default 2 administrative sessions are not enough for them? If that's the reason, I would object still more. Having more than 2 administrators working *simultaneously* on a server is in itself a dangerous situation. If they find that they need more sessions because the default 2 sessions are constantly occupied, then the solution is to learn them to logoff from their session when they are not actively working in it (rather then letting it sitting idle or disconnect from it), and configure the server with a short (say 5 minutes) time-out on disconnected and idle sessions.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
Laurent Dumont <utilisateur@xxxxxxxxxxxx> wrote on 21 nov 2008 in
microsoft.public.windows.terminal_services:
Hello,
I'm not a user of Terminal server in "application" mode, but I
have some questions to ask, and any help would be appreciated.
Many of our systems are managed with terminal server
"administration" mode (remote desktop), but one of the teams ask
me to install terminal server CALs to manage they complex
application.
Theses server are installed with W2k3 R2 SP2
If we do not take care of the CALs cost, is there some good
reasons to refuse the activation of terminal services? Could you
give me links to microsoft web site to justify it?
Thanks for your help.
Laurent Dumont
- Follow-Ups:
- Re: using Terminal server for applications management
- From: Jeff Pitsch
- Re: using Terminal server for applications management
- References:
- using Terminal server for applications management
- From: Laurent Dumont
- Re: using Terminal server for applications management
- From: Vera Noest [MVP]
- using Terminal server for applications management
- Prev by Date: Re: Restrict w2k3 server to console only connections (session 0)
- Next by Date: Terminal services 2008 - MAC users
- Previous by thread: Re: using Terminal server for applications management
- Next by thread: Re: using Terminal server for applications management
- Index(es):
Relevant Pages
|
Loading