Deploying the BigFix Agent to a Workgroup that doesn't use our DNS

(imported topic written by tscott91)

We have some PC’s that are in a totally separate domain that we support… Their DNS doesn’t talk to our DNS… When I push the client out and get it installed the client doesn’t know where “BIGFIXSERVER.Domain.abc.net” is located so therefore it does not report back to the console…

I know there are ways around this (editing hosts files, creating A records, etc… The easiest way would be if I could tell the clients instead of looking for BIGFIXSERVER to look for 192.168.1.14…

I was told to create a file clientsettings.cfg and put it here: " C:\Program Files (x86)\BigFix Enterprise\BES Console\BESClientDeploy\BigFixInstallSource\ClientInstaller " on my PC which is the PC I am using to do the right click installs from the Console.

The client gets installed but I still don’t think it’s using the IP address as the log still shows the DNS name…

What am I doing wrong and / or how do I get around this issue?

Thanks, Tom

(imported comment written by BenKus)

Hey Tom,

Did you follow the instructions at http://support.bigfix.com/cgi-bin/kbdirect.pl?id=454 for the clientsettings.cfg file format?

Ben

(imported comment written by tscott91)

All my file has is:

“IP:http://192.168.1.134:52311/bfmirror/downloads/

I’m guessing that is not correct after I read your link… I was following http://support.bigfix.com/cgi-bin/kbdirect.pl?id=244.

So what should my file contain? This?

_BESClient_Relay_NameOverride=192.168.1.134

(imported comment written by BenKus)

Hmmm… the initial syntax you used seemed right (it is the older school version, but should work)…

Try this:

__RelayServer1=http://192.168.1.134:52311/bfmirror/downloads/

And you probably want to make sure the port is open for TCP…

Ben

(imported comment written by tscott91)

Thanks… I put that in the file and it did use that info and report back to the console which is great… However, I can’t get it to change to what I want the relay server to be…

It was set to manual, I right clicked and changed the relay server to the one I wanted, it said completed, I refreshed and it was still pointing to the IP… I even tried changing it to automatic to see if that would change it and it didn’t…

In the edit settings I removed the custom relay server and that didn’t fix it either…

Any ideas?

Thanks!

(imported comment written by BenKus)

Hey tscott,

I guess I am confused at what you are trying to accomplish… If you are trying to point the agent to another relay by another name, but it can’t reach it because of DNS issues, then it won’t ever switch away from the relay that it currently can report to.

Ben

(imported comment written by tscott91)

Ok. Here is what I’m trying to accomplish…

I have PC’s in another domain that don’t know the FQDN of the master BigFix server… So, I want to use the IP so they can at least initially report back to the console… After that, I can then assign them to their local relay servers…

I’m getting them to report back in good with the IP (used your code) but the problem is, some of them aren’t changing their relay servers to what I am telling them to… Others are…

(imported comment written by BenKus)

If they are refusing to connect to a relay that you tell them to, it usually means that they can’t access it… I don’t think this is related to the fact that it was installed with the clientsettings.cfg file… It probably would be best to troubleshoot this on one of the computers: http://support.bigfix.com/cgi-bin/kbdirect.pl?id=182

Ben

(imported comment written by tscott91)

Ahhh… Ok, that makes sense…

Question… Is there a way to edit something locally on the client PC that already has the client installed to point to a specific relay or does that have to be done during install via the clientsettings.cfg?

Thanks