Several setup questions, security, bandwidth, licensing...

Hi,
Sorry about all the questions, but...
1. How strong is the security in Terminal Server 2003? Should I run it
through a VPN or not? (see question 4, the VPN seems to suck up bandwidth)
2. How much bandwidth would a session take? How do you figure what you need
for 20 users? These users would only be going into an access database, not
much else. The database(s) are pretty small.
3. How would you calculate the memory requirements on the server? Same use
as above.
4. How would you handle the licensing on the Access end. Each user already
has MS Office on their laptop, they are using a PIX firewall and VPN client
to get to the server where the databases are stored, but Access is not
installed on the server yet. The performance is pretty bad, hence the shift
to Terminal Services.
5. Should I install Access before I install Terminal Server? or Terminal
Server, then put it into install mode and install Access?
6. How will the other applications such as Veritas and Symanted work after
I put the server into Terminal Server?
Any suggestions/insite/help is GREATLY appricated. Thank you.
- Wayne

1. RDP is secure, so ony use a VPN if creating permanent links between
office, or if using SSL VPN to avoid RDP traffic from being blocked
(uncommon, but it does happen, and would happen with IPSec or PPTP VPN as
well)

http://www.sessioncomputing.com/security.htm

2. Bandwidth is usually around 20-30Kbps per concurrent connection, plus
bandwidth for printing to client printer or copying files to the client.
Highly graphic apps can use over 100Kbps, i.e. Windows Media Player or Flash
Animation. You can test and track the bandwidth with System Monitor Control.

3. Test your apps to see how they scale.

http://www.sessioncomputing.com/scaling.htm

4. If the client has an equal or higher version of Office or the specific
office app you're using already installed on their client, no additional
office license is required. You must be able to prove this in a BSA Audit.

http://www.sessioncomputing.com/applications.htm
http://www.sessioncomputing.com/licensing.htm

5. Apps are installed after TS. See the applications URL above.

6. http://www.sessioncomputing.com/anti-virus.htm
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.sessioncomputing.com


"Wayne" wrote:

> Hi,
> Sorry about all the questions, but...
> 1. How strong is the security in Terminal Server 2003? Should I run it
> through a VPN or not? (see question 4, the VPN seems to suck up bandwidth)
> 2. How much bandwidth would a session take? How do you figure what you need
> for 20 users? These users would only be going into an access database, not
> much else. The database(s) are pretty small.
> 3. How would you calculate the memory requirements on the server? Same use
> as above.
> 4. How would you handle the licensing on the Access end. Each user already
> has MS Office on their laptop, they are using a PIX firewall and VPN client
> to get to the server where the databases are stored, but Access is not
> installed on the server yet. The performance is pretty bad, hence the shift
> to Terminal Services.
> 5. Should I install Access before I install Terminal Server? or Terminal
> Server, then put it into install mode and install Access?
> 6. How will the other applications such as Veritas and Symanted work after
> I put the server into Terminal Server?
> Any suggestions/insite/help is GREATLY appricated. Thank you.
> - Wayne
>