Sage 100

In the middle of an upgrade from 90 to 200 (4.40 to 4.50) and client informs me they have terminal services running on the server. He neglected to indicate that on our questionnaire. Informed him that's a problem due to TS cannot reside on same server as 200. He wants to know why - other than 'Sage says so!'. Can somebody explain it to me? What are the ramifications? We are going back to MAS90 till issue resolved, but I'd like to give him something other than 'Sage Says So'.

@AlnoorCassim would be the guy I would turn to for an answer on this. Don't tell anyone, but before I was a consultant, our company ran MAS200 on the Terminal Services server, which was also the domain controller, and I don't remember ever having any sort of issues that weren't caused by mistakes that we made in setup.

I think Sage says so because that would be one less item to troubleshoot. Depending on the robustness of the server and the number of users, go ahead and install it. Just warn them that if issues DO crop up, they MAY have to bring in another box or at least virtualize this one for a Terminal server.

We have run into issues down the road, never on a new server, but as it ages and resources are gobbled up. Slow downs and occasionally hangups. Never a stand still.

I tend to agree with Jeff. Inform that it is not a supported platform and many times things work out fine but on occasion there are problems and if so they may have to bring another server.

In general, I think it's resources - they don't want you to install MAS 200 on Domain/email servers, terminal servers, etc. But we've had several clients that have gone this way and we give them the old disclaimer - it's not supported, play at your own risk. For some, it's been ok. For others, it doesn't work out so well.

Thanks everyone, you guys rock for responding so quickly. We are going to move forward with the MAS200 and TS on same box with plans to move 1 of them in next couple of months. Thanks again,

Everyone's answer is correct. I will the most important factor is the number of remote users. How many are we talking about?

Offhand I'm not sure but they only have a 15 user license to begin with and not everyone is remote.

Just talked with customer, they have 5-10 that are hitting the TS (generally 5) and they aren't hitting it hard or all day either. We are moving forward with 200 with plan to put 200 on its own server soon. Thanks again everyone.

If it's up to 5 to 6 users and their main purpose for using a TS is to run MAS (as opposed to other major applications) and the hardware is fairly recent, I wouldn't worry about it. Problems come into play when you're on an SBS version of Windows Server or when Exchange Server is running or there are hundreds of client redirected TS printers to service (they add up quickly when you have multiple remote locations). If you explain that to client and give them fair warning, it usually works out. One more thing - Some people run a virtual Terminal Server (e.g. VMWare or Hyper V) that connects to the virtual MAS server, both of which reside on the same physical machine. If you have to insist on a separate box, if the hardware is good, then separate virtual machines is a much easier solution for IT than a separate box.