Using _BESClient_Relay_NameOverride on main server

Usage and Config Platform
1

(imported topic written by geofmuck)

I’ve run into some trouble with endpoints autoselecting the main server as their relay. This server is joined to an AD, so the name that the OS reports as its “DNS Name” is really the DDNS name, which is not the same as the DNS name by which the service is known and which is in the masthead. This means that the server reports its relay with the DDNS name and the clients select it (as it is closest) because they don’t realize that it’s actually the main server.

I’ve found the “_BESClient_Relay_NameOverride” setting, and it sounds like it does what I need (to make the relay report the DNS name associated with the service), but the task that sets it won’t run on the main server (“not exists main gather service”), which leads me to believe that maybe I can’t (shouldn’t) use this setting on the main server.

Can someone tell me definitively whether I can safely use this setting on the main server? And if not, is there some way I can get the relay on the main server to identify itself the way I want?

Geoff

2

(imported comment written by jpeppers91)

Can anyone comment how to do this on the server? I want to create an alias name for the main Bigfix server and want to be able to select it as an option as a relay.

3

(imported comment written by Tim.Rice)

Have you looked into the Relay Affiliation Groups options for the Relays? You configure the Relays to advertise a Group Name, then tell the clients to use the appropriate group for relay selection. Simply don’t configure the Main Server to advertise the same group that clients are looking for.

i do something similar with our clients at remote sites to prevent them from connecting to a relay at a different site.

1 Like