Terminal Services/Remote Desktop Server Setup for Sage Line 50

Currently have a SBS 2011 setup with 5 local users that use Sage Line 50 2013 (data folder held on SBS 2011).

I also have a TS/RDS Server 2013 setup for 4 remote users for Booking s/ware and 2 remote users for Sage Line 50 2013.

We having occasional issues with slow speeds and ‘file waiting’ using Sage Line 50 2013 – a common problem with Sage across a network. Sage support have suggested upgrading to Sage 200 (at a cost of approx. £16k!), for a lot of modules we won’t use. Doing a bit of research pointed me in the direction of perhaps using RDS locally for Sage Line 50 2013 and store the Sage data files locally on the RDS aswell – thus eliminating the networking issue, as all local and remote users would remote in (most probably using RemoteApp).

So my question is on the build side. I’ve tested Sage Line 50 2013 on a number of machines using their local stores and my i7-2600k/8GB/SSD machine out stripes them all by a long way. So I was going to build a new server based on similar spec with:

I7-3930k (or perhaps a Xeon to a similar price – I used http://www.cpubenchmark.net/high_end_cpus.html  for cost to performance ratios)
SSD x2 (Raid 1) 240GB or 480GB
Windows Server 2012 + Appropriate Std. Cals/RDS Cals
[Approx. cost £2k/£2.5k.]

I know most will say don’t build, but you get so much more for your money and this is a local server where I am based so support isn’t an issue. Also I know a few will question SSD setup, but I’ve been using SSD’s in Raid1 in the SBS 2011 server for 2 years now and it’s been rock solid. Also its possible overkill, but if it’s able to speed up running reports by 30 seconds a time, it’s well worth the cost against labour waits particularly  costing out Managing Directors and Financial directors wages.

So couple of questions:
Firstly is there any issues with running Sage Line 50 2013 over RDS to this level.
Is the above build appropriate for a potential 11 (current) – 15 (potential) users remote’ing in.

As always, thanks for any replies.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bruce DenneySage 50 Consultant and IntegratorCommented:
SBS 2011 is not supported by Sage for Sage 50.  

I suggest using a supported operating system.

For best performance, run all users even the local ones on Terminal Server.
joefolkesAuthor Commented:
I havent installed Sage 50 on the SBS 2011, just holding Sage data in shared folder.
But thats a +1 for TS/RDS for Sage - Have you used it yourself like that?
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Running SAGE locally and allowing users to RDS is a good option, just ensure to setup your options for idle and disconnected users.  If you have only 8 GB of emory then I suggest to bump up the memory to ensure optimum performance.  Install SAGE under Win2K8 or Win2K12 and publish SAGE via RDS Web.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Bruce DenneySage 50 Consultant and IntegratorCommented:
SBS 2001 is unsupported even for file sharing.  

Sage is a bandwidth hungry application.  If you want great performance then you want it to have shed loads of bandwidth, so having it use a network to read data off a disk on another machine is going to have a bottleneck in the network.

I would use and store the sage data on the local SSD  RAID array (you want a fast SATA controller to match the drives)

Some people say SSD'd are still a bit unreliable, so having a big old HDD drive might be an idea as you can write an image to it every so often and should it go bang you can recover back to a single drive whilst you sort things out.

Personally I am unconvinced about RAID, disk mirroring is going to slow things down.  You also need to be sure you will spot a failed mirror, I know of many cases where mirrors failed and no one noticed until the other drive failed as well!
joefolkesAuthor Commented:
Thanks for the responses, seems all in favour of Sage over RDS. Also didnt realise Sage 2011 data hosting is unsopported on SBS.

Good option to add extra HDD for backups.

I'll wait a little to see if anyone else has something to add in favour or against my Sage RDS setup, before closing.
joefolkesAuthor Commented:
Helped me choose Remote Desktop for Sage
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Hardware

From novice to tech pro — start learning today.