I run my whole office off a cablemodem, connected to W2K Server with ms terminal server for about 6 staff who dial in through various ISPs at 56k and I am very impressed with how quickly and with such little knowledge and expertise we had the thing going. We had to make some minor changes to our vfp app to do it properly (such as ensuring each user had their own non-conflicting temp disk space and ensure application work files didn't collide - took about a week to sort out). Our platform is a simple 800mhz machine with 256mb of ram, with mirrored SCSI drives on separate controllers. Yes, we did it on the cheap, as we can't afford to lay out cash for a RAID 5 setup with a redundant machine, etc, but we are willing to live with the consequences, of which have not arrisen since we installed about a year ago.

I have a dual P3-700mhz box with 512mb of ram and dual SCSI's I plan to migrate the system to. We just happened to inherit this new box from a failed ASP (a lot of them around these days it seems). We are not experiencing any problems or speed issues, we're doing it, "just 'cuz". My testing of the dual processor setup with W2K/WTS shows that the user experience isn't any faster, however, the box tolerates a lot more concurrent users doing a lot heavier work, so we decided to do it just for good practices sake.

I don't know how well WTS would work in a really large implementation, however from what I've seen it requires major $$$ and the WTS client licensing scheme by M$ really sucks in super-large deployments. From a fiscal point of view, you might be better off recoding for a browser and an N-tier setup with browser presentation, unless you really don't want to re-engineer the app, or your user experience has to be richer than a HTML browser can provide.

My 2 cents.

Jay