Sage 100

Sage 100 Advanced version 2014, service pack 3. We have a client migrating to a new server without a version upgrade. However, we will be installing a new DSD enhancement on the new server and the client wants several users to test the new solution before going live. The users who will do the testing run their current Sage 100 client on a terminal server. Is it possible to install two different copies of the Sage 100 Advanced client to two different directories on the same terminal server without stomping on one another? The providex server on the two different Sage 100 server use different ports so that won't be a problem. Thoughts? Be there Lions, Tigers, or Bear's down that path that I need to be wary of. What about dragons that I will never be able to pass? Thanks in advance.

Shawn, I usually install MAS on the sever in its final location. Then make a copy of MAS90 and paste it to another folder. Once this is done, you have 2 separate ""installs"" of MAS. I recommend running the trial MAS as MAS 90 instead of MAS 200

Cooper, in this instance there are two different server installs on separate boxes. I want two clients pointing at different servers on the same terminal server. Worried about ODBC and client conflicts between sessions.

You can always add a second server to the client workstation installation. Rerun wksetup and one of the options will be to Add Server and then you can add the new server and port number. Since this is a terminal server, all users who access it this way, will see two servers when they launch the Sage 100 program. If you don't want other users to see it this way, then running ""MAS90"" style is the way to go