What Server?
Author
Discussion

welsh blackbird

Original Poster:

692 posts

274 months

Wednesday 27th July 2005
quotequote all
We are looking to inpliment a system whereby staff can work from home using Remote Desktop connections.

There will be approximately 30 active connections at any one time, all of whom will be working on an Access database.

We need a server to meet these requirements, and any advice as to a specification would be much appreciated.

Also, will a broadband connection into the server have enough bandwidth? We can only get 2 meg broadband as the local exchange cannot supply anything faster! Or would we need a leased line?

Any advice greatfully received!

spivvy

1,535 posts

284 months

Wednesday 27th July 2005
quotequote all
Numbers of ways of doing this ,but if banwidth is an issue it may be better to use terminal server and get remote users to terminal server in , loads of info here
http://nts.jhmi.edu/desktop/sourcedocs/885-1.cfm

workshy fop

761 posts

297 months

Wednesday 27th July 2005
quotequote all
I presume you do mean via terminal services, you can't connect 30 users to the same box with remote desktop.
I built a terminal services box with about the same number of clients a few months back.
It kicks the crap out of CPU and memory. This one has 2Gb ram and 2x xeons and it's quite highly utilised. I'd probably go for 4gb and 2x 3.0ghz xeons if I was doing it again and spec about 100Mb ram per user.

malman

2,258 posts

289 months

Wednesday 27th July 2005
quotequote all
Bear in mind that all flavours of ADSL have 256 upload so do your bandwidth calculations based on the fact the server will only beable to upload to the net at that rate. Check to see if SDSL is available if you need extra bandwidth.

agent006

12,058 posts

294 months

Wednesday 27th July 2005
quotequote all
An ADSL line won't be enough for terminal services. As has been said, Windows Server will only support two RDP connections before you need to buy more licenses and switch it over into full terminal services mode.
Server capacity will be fine with all but the most basic of modern servers unless you're doing heavy stuff.

robbieduncan

1,993 posts

266 months

Wednesday 27th July 2005
quotequote all
malman said:
Bear in mind that all flavours of ADSL have 256 upload so do your bandwidth calculations based on the fact the server will only beable to upload to the net at that rate. Check to see if SDSL is available if you need extra bandwidth.


Not true. My ADSL (Bulldog 8Mbit) has an advertised 400Kbs upload. I'm actually seeing nearer 450.

JamieBeeston

9,294 posts

295 months

Wednesday 27th July 2005
quotequote all
robbieduncan said:

malman said:
Bear in mind that all flavours of ADSL have 256 upload so do your bandwidth calculations based on the fact the server will only beable to upload to the net at that rate. Check to see if SDSL is available if you need extra bandwidth.



Not true. My ADSL (Bulldog 8Mbit) has an advertised 400Kbs upload. I'm actually seeing nearer 450.


Thats only LLU DSL accounts, which are primarily restricted to London (not North Wales like the Thread Starter hehe)

Its nice to have tho.

J

randlemarcus

13,646 posts

261 months

Wednesday 27th July 2005
quotequote all
agent006 said:
An ADSL line won't be enough for terminal services. As has been said, Windows Server will only support two RDP connections before you need to buy more licenses and switch it over into full terminal services mode.
Server capacity will be fine with all but the most basic of modern servers unless you're doing heavy stuff.

Not exactly true, I'm afraid. Terminal Services kicks the bottom out of CPU and memory, as has been said above. Personally, I usually spec a four way box with at least 4Gb per 50 users. If they are heavy access database users, running 30 instances of Access over terminal services, you will need every clock cycle you can buy.
At the risk of taking it off topic, could you perhaps consider a lateral investment, and get the application ported to SQL Server, then pop a web front end on it. Much more scalable, and you could even throw in mobile access without too much hassle.

agent006

12,058 posts

294 months

Wednesday 27th July 2005
quotequote all
Missed the Access bit. Our Citrix farm gets 40 users onto Dual P4Xeon 2GB compaqs, with little performance problems. Those were inheited though, and i'd spec them higher if i'd get the choice.

Another thing to consider is to use two lower spec servers, to give a bit of redundancy.

welshblackbird: drop me a mail through my profile if you're after a proper quote for getting the whole lot done (not directly by me though, just our company).

>> Edited by agent006 on Wednesday 27th July 18:10

K50 DEL

9,752 posts

258 months

Wednesday 27th July 2005
quotequote all
We run the majority of our business through remote access (10 locations totalling 150 users)
they currently connect through 3 citrix servers (dual Xeons with 2GB RAM each)
each remote site has 2mb ADSL and we have 2Mb leased line.
The above setup works reasonably well, but the 2mb ADSL is definately the weak point by virtue of its asyncronicity (as discussed in the posts above)

Whilst you'll get away with one server (although I'd still spec 2 and load balance the farm)
2 MB ADSL simply won't cut it for connectivity, you'll end up with irate users complaining "my system's really slow" in a whiny annoying voice all the time.

agent006

12,058 posts

294 months

Wednesday 27th July 2005
quotequote all
Also, it's latency that kills Terminal sessions. or at least kills the perception of speed in a TS session.

ThatPhilBrettGuy

11,810 posts

270 months

Wednesday 27th July 2005
quotequote all
You will find that within reason the bandwidth isn't the issue. I've done a shed load of work on this (even having the head of development of Longthorn TS from Microsoft flown over).

It's network latency that'll get you. We pushed the network speed from 100Mbit down and down and found you had to get down to 10Kbit before any effect was observed (and our app is quite dynamic). Push the latecy up with a Packet Storm box or alike and the bandwidth means nothing.

E-mail me via my profile if you need some more detailed stuff.

ATG

23,811 posts

302 months

Wednesday 27th July 2005
quotequote all
welsh blackbird said:
... There will be approximately 30 active connections at any one time, all of whom will be working on an Access database...
That bit rings some major alarm bells. If you need a database application that is reliable and robust for more than a few users I'd dump Access. It is great for prototyping, it can be used as an OK report generator and in the hands of a skilled end-user it is a powerful tool ... BUT Access is fundamentally evil and it sucks organisations in and drains all the goodness out of them.

BliarOut

72,863 posts

269 months

Wednesday 27th July 2005
quotequote all
Yup, dump access or just use it as a front end. Go to SQL or MySQL for the back end instead.

I would read up on the implications of Access on TS, it kinda doesn't work properly!

malman

2,258 posts

289 months

Thursday 28th July 2005
quotequote all
robbieduncan said:

malman said:
Bear in mind that all flavours of ADSL have 256 upload so do your bandwidth calculations based on the fact the server will only beable to upload to the net at that rate. Check to see if SDSL is available if you need extra bandwidth.



Not true. My ADSL (Bulldog 8Mbit) has an advertised 400Kbs upload. I'm actually seeing nearer 450.


Oops forgot about LLU stuff. He would still be better off with SDSL though.

welsh blackbird

Original Poster:

692 posts

274 months

Friday 2nd September 2005
quotequote all
BliarOut said:
Yup, dump access or just use it as a front end. Go to SQL or MySQL for the back end instead.

I would read up on the implications of Access on TS, it kinda doesn't work properly!


BlairOut, where can I find out more information on this incompatability? I've googled, but come up with nothing!

Cheers