Force client to re-evaulate relay selection

(imported topic written by murtasma91)

We have around 700 clients that have been using the main BigFix server as the relay used for communication. These clients are currently set to use the automatic relay selection. We have 12 relays in our envrioment (each relay is loaded with clients) so I know the automatic relay selection process appears to be working correctly for us. How can I get these clients off the Main BigFix server?

(imported comment written by SystemAdmin)

Issue a custom action with an action script of relay select targeting the desired machines.

(imported comment written by murtasma91)

like

relay select “dns entry of target relay”

?

(imported comment written by BenKus)

Agents will use the BigFix Server if it is closer than any other relays… but they will prefer relays to the server if there is a relay available at the same distance… So if you put a relay in the same subnet as the BigFix Server, I bet the agents will migrate to it.

Ben

(imported comment written by murtasma91)

We have two relays on the same subnet as the BigFix server. Many of these machines are on a subnet where other clients are using one of our relays just fine. Across our deployment the average distance to a relay is 3 - 5 hops. A few computers are 8 hops while the rest typcially roam and come in around 8 - 12 hops away.

(imported comment written by BenKus)

Hmmm… OK… try using the “Failover relay” setting (look in the BES Support site or the “BigFix Management” domain)…

Ben