After changing the IP address on the CSA and pushing out the change to your machines, some machines stop connecting to the core through the CSA. During troubleshooting, you find that the IP address the machine is attempting to connect to the CSA with is the old one that you changed.
This can cause any number of issues with devices outside the network. Internal devices may be unable to retrieve a broker certificate.
Navigate to and edit %ldms_home%ldlogon\AgentBehaviors\clientconnectivitybehavior_CoreServer_XXXX.xml (there may be multiple depending on how many client connectivity settings you have. Be sure to make the change in all settings that use the CSA)
Change the IP address in the following locations:
<p> <Name>csa_fqdn</Name> <Val>CSA.FQDN.com</Val> </p> <p> <Name>csa_ipaddress</Name> <Val>IPAddress</Val> </p>
<fqdn>CSA.FQDN.com</fqdn> <ipaddress>InternalIPAddress</ipaddress> <publicUsed>0</publicUsed> <publicfqdn>CSA.FQDN.com</publicfqdn> <publicipaddress>ExternalIPAddress</publicipaddress>
Save the document and confirmed the change made it into the database under the DBO.AgentBehaviors table. If the database still shows the old IP address, make the change on the database record as well.
The clients that are still communicating to the core server will automatically get the change over the next few days (depending on their vulnerability scanner schedule).
If the clients have lost communication to the core server because of the setting reverting (Usually off-network devices), you will have to wait until they connect to VPN, come into the office, or manually make the change yourself. Reinstalling the agent should also fix this issue, just be sure to uninstall first.