Is this what you need?
SIMS.net and multiple connect.ini files
Good Morning All,
We're looking at a few ideas and was wondering if I'm missing an easier way of doing this.
2 Domains, 2 seperate SIMs servers etc.
1 Domain, 2 seperate SIMs servers
We want to be able to load each "SIMs" application seperately based upon which of the two servers we want to be able to access.
So we can use 2 installations of Solus 3, one on each server and deploying each client with "one" of the SIMs installations based upon which computers need access to which. However that will then require different machines to map to "different" S drives etc depending on which server it'd need to connect to, etc etc annoying
Is there any simple way of effectively changing one of the SIMs boxes to use a different installation path for SIMs and a different shared drive? e.g. Server 1 installs to C:\SIMs1 and uses S:, Server 2 installs to C:\SIMs2 and uses T: as it's SIMs drive? If that makes any sense? Then you'd just have 2 installs of SIMs per pc, and load each one based upon which of the servers you want to connect to?
Steve21 (15th October 2013)
Hmm certainly seems a good start! Thanks. Based on that do you not need an S: drive then? Does nothing directly connect to it unless your connect.ini uses it?
There are currently 1 users browsing this thread. (0 members and 1 guests)