What specifically are you trying to achieve by installing multiple VSE, Coordinators, Simulators, etc.?
I am curious if DevTest Community Edition or CodeSV might also work for you. Both have smaller footprints.
One challenge: How do you ensure that each new installation names their components so they don't conflict with another installation?
After installation and before starting the services on each new machine:
- Ensure that local.properties is pointing to the one registry; you will NOT start the Registry Service on this machine -- it should be executing on the other machine.
lisa.registryName=tcp://<serverName or IP>:2010/Registry
You could also add lisaAutoConnect=tcp://<serverName or IP>:2010/Registry if you want to
- Name each VSE, Coordinator, and Simulator with a unique name. For your own sanity, edit each CLI and Service .vmoptions for the components (VSE, Coordinator, Simulator):
-Dlisa.vseName=vse1 - where "vse1" changes so that each new install is visible in Portal
-Dlisa.coordinatorName=Coord1 - where "Coord1" changes for each install
-Dlisa.simulatorName=Sim1 - where "Sim1" changes for each install
Check out abrsh01 tech tip: Tech Tips: Creating and Configuring Multiple Simulators on the Same Machine for Windows Services if considering multiple Simulators on a single machine.
As you start each service, check the log file(s) to ensure the service starts correctly and attaches to the Registry.
In Workstation, all of the environments will be visible. You can create and assign ACLs (groups, roles, etc.) to your users if you need to implement security such that folks do not see each other's environments.