If the ping (ICMP) response time for both servers is exactly the same (to the closest millisecond) then the default priority will likely end up as you're observing. Here are a few thoughts about this:
If the beacons are in different locations, then I expect the likelihood that the ping response time is exactly the same would typically be pretty low, and the typical operational behavior you would see across many devices is a reasonably breakdown based on which beacon can be reached fastest.
If the beacons are in the same location, then it is more likely that the response time will be the same for two different ping operations - although once you get connections from across different networks that is going to be less likely. If this is a real concern then a couple of options to consider may be:
- Use a load balancer - configure agents to connect to the load balancer's URL, and something like a round robin algorithm to farm out requests to both beacons.
- Use a setting like "MgsRandom;MgsPing;MgsADSiteMatch" for the SelectorAlgorithm agent preference - this will randomize the priority order of beacons before doing the ping, such that if the ping response from both beacons is the same then the random order will be preserved.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
