Terminal Server as an afterthought

  • Thread starter Thread starter David J. Stewart
  • Start date Start date
D

David J. Stewart

I hate to post such an involved article but I need to set the foundation for
you to understand my questions. Hopefully I can get some of them answered.

We run a seven server shop and have 5 major campuses located around the
state which connect by T1 Point-to-Point WAN. Two locations connect through
VPN (one DSL, the other cable). Our application server hosts 3 applications
and IIS (intranet) and SQL server.One of our applications is our financial
app. We are finally to the point where we have convinced the CFO to allow
our Area Directors (campuses around the state) to access this application fo
better help them manage their budgets. Come to find out, this application
does not support WAN networks. We will have to use Terminal Services to
allow the Area directors to access the application. Needless to say I have a
host of questions. I hope I can get some of them ansered here.

1) Will I have to un-install all of our applications, configure Terminal
Services, then re-install the applications

2) can IIS (intranet) co-exist with Terminal Services

3) will our users have to use Terminal Services to access all of the
applications, or can some applications be accessed as normal and just
selected apps be accessed through Terminal Services

4) I understand that if we are using Windows 2000 pro we will not have to
purchase Terminal Server licenses

I am sure there are a lot more issues to condider but these are the ones
that jump into mind. Any help would be greatly appreciated.

David Stewart
(e-mail address removed)
 
1. This depends on where you install Terminal Server. Normally you don't install it in a server that does other things, i.e. hosts database services, DC, Exchange... Normally you setup a new machine, install TS, install applications that access backend databases & file/print services. Since database servers usually don't have the fron end for the application installed on the server, connecting to this machine for TS wouldn't help you anyway. Think of a Terminal Server as a multi-user workstation, not a server that holds user data. The terminal server is located where the data is, not where the users are

2. IIS can happily co-exist with TS

3. Users can access one application or the entire Terminal Server Desktop and run applications on their local PC simultaneously

4. If the Terminal Server is Windows 2000 & clients are 2000 or XP Pro then no Terminal Services CAL is required, as the Terminal Services Licensing Service will issue them free licenses form its' built-in pool. If the server is 2003, then all connections require 2003 Terminal Server CALs & 2003 Windows CALs

2000 Licensing FAQ
http://www.workthin.com/tsls2k.ht

2003 Licensing FAQ
http://www.workthin.com/tsls2k3.ht

Terminal Services how-to articles, includes planning, installation, configuration..
http://www.workthin.com/tshta.ht

Books on TS: (I highly recommend reading one of these or hiring a server based computing consultant before proceeding
http://www.workthin.com/tsbooks.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co



----- David J. Stewart wrote: ----

I hate to post such an involved article but I need to set the foundation fo
you to understand my questions. Hopefully I can get some of them answered

We run a seven server shop and have 5 major campuses located around th
state which connect by T1 Point-to-Point WAN. Two locations connect throug
VPN (one DSL, the other cable). Our application server hosts 3 application
and IIS (intranet) and SQL server.One of our applications is our financia
app. We are finally to the point where we have convinced the CFO to allo
our Area Directors (campuses around the state) to access this application f
better help them manage their budgets. Come to find out, this applicatio
does not support WAN networks. We will have to use Terminal Services t
allow the Area directors to access the application. Needless to say I have
host of questions. I hope I can get some of them ansered here

1) Will I have to un-install all of our applications, configure Termina
Services, then re-install the application

2) can IIS (intranet) co-exist with Terminal Service

3) will our users have to use Terminal Services to access all of th
applications, or can some applications be accessed as normal and jus
selected apps be accessed through Terminal Service

4) I understand that if we are using Windows 2000 pro we will not have t
purchase Terminal Server license

I am sure there are a lot more issues to condider but these are the one
that jump into mind. Any help would be greatly appreciated

David Stewar
(e-mail address removed)
 
Back
Top