Sage 50 Company Files on Separate Servers

I have a client running a Server 2012 STD server as domain controller and remote desktop server.   On that same server, they have Sage 50 US installed and hosting 4 Sage company files accessible via the local network workstations and through remote desktop services.    We now have a need to isolate one of these company files.   My thought is simply to install another 2012 or 2016 Standard server and to install Sage 50 on that box for that single company.   I'm assuming local workstations could still access that file through a different drive mapping.   Is that correct?   Would I need all new RDP licensing to keep users of this lone company ONLY on this new server when accessing it remotely?

Any other solutions anyone can think of?
darylkrauseAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Bill BachPresident and Btrieve GuruCommented:
Each Sage 50 installation would come with the Sage 50 software AND the PSQL database engine license to run that software.  I do not know for sure if Sage allows you to install their license onto multiple servers, or if you would have to pay another license fee for that, so contacting them is the best way to know for sure.  

Licensing aside, the PSQL database engine works solely from the application's perspective.  It is up to the application to provide the path to the database files to the PSQL Client, which then handles finding the right server and contacting that server for database services.  This should make it a simple matter of changing the drive letter or UNC path used by Sage.  As long as it resolves to the new server (and the firewall doesn't block access to TCP ports 1583 and 3351), then you should be contacting the new server directly.  If Sage provides the PSQL Monitor tool, then you should be able to see the users connecting to the server within that GUI interface.  If not, perhaps they provide BMON, a Java-based alternative that runs from a command line.  If they don't provide even that tool, then try the third party PSConfig tool.  With that tool, a simple command line "PSCONFIG /M*" run from the database server will show you all you need to know about what is going on inside the PSQL engine,

For true separation, you'll need to have RDP licenses available on the second server, too.  Note, though, that you could have users from BOTH systems on a third server running RDP services and accessing either server, which might save in licensing costs.
darylkrauseAuthor Commented:
Thank you for your response!   That last paragraph helped more than you can know.
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
Networking

From novice to tech pro — start learning today.