I believe this is a known defect on 8.1.1 installer, which got fixed in 8.5.
The work around involves using a different Topology Manager database for the 2nd install, then change the 2nd server to use the first one (and delete the second one).
One has to wonder though... why aren't you deploying 8.5 rather than 8.1.1?
The Environments (and Websites/apps) you configure in Topology Manager represent logical Environments; each of these things may or may not be scaled out physically, but that doesn't affect Topology Manager.
In your case, it seems you want to scale out both your Websites and your Deployer. The idea is that this is achieved at the infrastructure level.
The Content Manager ID stored in the System Environment Variables:
TRIDION_CM_ENVIRONMENT_ID = TridionCM_localhost
To see the Content Manager environment setting:
Gets one or all Content Manager Environments from the Topology Manager.
CoreServiceRootUrl : net.tcp://localhost:2660
WebsiteRootUrl : http://localhost:80
The SDL Live Content documentation has scaling information under "Scaling SDL Tridion" (requires login).
Clustering the Content Manager isn't your only option. You could also look into scaling out the Database, Search, Workflow, or Publishing (as well as Content Delivery).
Nick points out you cannot scale out the Content Manager Database. My mistake, ...
For any service goes: scaling out means running multiple instances of the service against the same database.
AFAIK, the discovery-registration.jar connects to the Discovery Service configured in cd_storage_conf.xml, so maybe you didn't change that configuration on each server.
I'm also wondering why you are trying to run the tool multiple times on multiple ...
@Ashraf, the CM Environment ID is stored in the Topology Manager Database. So as long as your two clustered CM servers are connecting to the same Topology Manager database, it should have the same CM Environment ID.
The %TRIDION_HOME%\Topology Manager\web\web.config contains the database setting
Note: The database setting is encrypted so you will need to ...
As Alvin says, you can scale out to multiple Content Manager servers (with a load balancer to manage the traffic to each).
As well as being able to spread the load and provide fault tolerance, scaling out the Content Manager and accessing the CME site through a load balancer allows you to easily put a 'holding page' in place (for the CME interface), if ...
All you need to do is to configure one of the machines as a host and another as slave. Documentation mentions it in the subsections of Installing Search on a dedicated machine
Otherwise you, I assume, you can have your Server B to point to search index on machine A. So all of your searching activity (and index) will occur on machine A. It's configured in ...