‎Jun 14, 2019 09:28 AM
Hi Kimberly!
You can change the application server of the old beacon to the new application server, this should make sure that all agents will know both beacons.
Once you are fairly confident that all agents have updated their policy, you can delete the old beacon. You can also create an A record just to divert any strays to the new beacon.
Make sure that the new beacons FQDN is resolvable by all clients prior to deleting the old one however.
Would this approach work for you?
‎Jun 14, 2019 09:57 AM
Hi Kimberly,
There are multiple possible approaches. Goal of most of them is to create a transition phase for the agents to catch up with the changes in the infrastructure. Here are two:
Alternatively, you could push the new Beacon details to all machines registries via script, after the new environment went live.
Best regards,
Markward
‎Jun 14, 2019 10:34 AM
One strategy which can be useful in some scenarios is to deactivate an old beacon and the configure a DNS entry pointing the old beacon's name to the new beacon's IP address. This will allow existing agents using the old beacon's name to get to the new beacon with one single centrally managed change.
‎Jun 16, 2019 05:57 PM