Re: Terminal Services member server??

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 10/01/04


Date: Fri, 1 Oct 2004 12:46:40 -0400

Ralph Andersen wrote:
> I have an install of SBS2K3 STD,1 Nic, Cisco Firewall,
> with a SQL member server (WS2K3). The Cisco firewall also
> provides a full time AES-128 VPN (T1 line) to a second
> location with 5 users. Two of these users actually travel
> site to site so really only 3 full time users.
> This works well except for our inventory program that
> connects via ODBC to the SQL database. It work fine, just
> the response time leaves a little to be desired (at least
> when my boss compares it to the speed of Solatire cards
> shuffling or EBay.)
> Rather than tackle SQL replication to put a SQL box at
> the second location, I'm looking at adding a member
> server for Terminal Services APP mode.
> My questions are:
> Do I just need to buy W2K3 Server /5 user and install it
> on a new machine to get TS?

Yes, with Terminal Server licenses also.

> I'm also curious, if my VPN were to go down, can multiple
> users use RWW to connect to the TS box and would this be
> in app mode?

Yes, it should be.

> How much horsepower should I be looking at for the TS
> box? I'm sure at lease 2 gig of ram but not sure if a
> typical single 2.6 Ghz P4 would be enough. The only
> program being ran would be the inventory software, it has
> a 43 Mb exe and honestly needs at least a good 2.0 Ghz
> workstation for it to not seem like you're waiting on it.
> This is for an aviation parts database so it's moving a
> ton of data for each record.

How many users do you expect to connect at once? Dual processor would be
nice, but may not be needed....memory is the biggie.

> I use SBS TS in Admin mode all the time, what important
> things do I need to know about TS APP mode???

Licensing is the main thing - and printing. See
http://www.workthin.com/tsp.htm for help with that. Also note that there's a
good TS newsgroup at m.p.windows.terminal_services.

> I have good infrastructure with dell 3324 switches with
> the 2 Gig ports to the servers with 1K nics, SQL box is
> more than enough machine for 5 concurrent users, all XP
> clients with good Ram/CPU. I welcome suggestions on how
> to impliment and optimize this, I have a fairly open
> checkbook on this as long as the performance at the
> remote site improves. TIA,
>
> -Ralph



Relevant Pages

  • RE: Fulltext failure on a 2 node cluster
    ... Server full-text search resource online: "SQL Cluster Resource 'Full Text' ...
    (microsoft.public.sqlserver.clustering)
  • Re: HELP PLEASE ~ ???
    ... You mentioned that it went ahead and added a SQL ... SQL Server 2000 database for all my data. ... find the connectionString in the newly recreated SQLExpress database. ... The connection string specifies a local Sql Server Express instance ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Multi-Channel Raid VS SAN Storage
    ... A 5~6 years old server is a very old server. ... As I mentioned, the server is one node in a cluster environment, and SQL is ... We actually are running RAID 1+0 and our aplication is definately more ... needs it's own SAN device, or at least a dedicated IO channel on the SAN. ...
    (microsoft.public.sqlserver.setup)
  • Re: Multi-Channel Raid VS SAN Storage
    ... A 5~6 years old server is a very old server. ... As I mentioned, the server is one node in a cluster environment, and SQL is ... We actually are running RAID 1+0 and our aplication is definately more ... needs it's own SAN device, or at least a dedicated IO channel on the SAN. ...
    (microsoft.public.sqlserver.setup)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... After you uninstall SQL 2005, the instance which you upgraded will not go ... Uninstall and then reinstall ISA server. ... Uninstall and then reinstall the Monitoring component. ... Tools to Maintenance, change Monitoring component to Install, and then ...
    (microsoft.public.windows.server.sbs)