We have 2 Windows 2008 servers - hostnames are server1 and server2. Both have the VCM (SCM) agent installed and can successfully communicate with the VCM server.
Our users want to use a BCP client called NeverFail to provide proper redundancy to the 2 servers. The way NeverFail works (in a nutshell) is it creates a heartbeat between the current primary server and the secondary. So, when installed and working - server1 has a hostname of server1 and server2 has a hostname of server1. Server2 becomes unavailable to the rest of the network, only addressable through the primary server (Server1). When a change is made to server1 the same change is applied to server2 through the NeverFail heartbeat connection. With the Neverfail software installed/working, server2 does not communicate back to the VCM server. VCM can not monitor the changes on server2. It can on server1, just not on server2.
So we have tried to add a second IP to each server and attempt to communicate to it through those IPs, however we still fail with server2. I suspect it is because the hostname on server2 has become server1 and identifies itself as server1 regardless of the IP used to communicate with the server. With this scenario, the machine names do not match the domain names. Help!
Any suggestions? Anybody else run use this NeverFail product with VMC?
Help!
Thanks