Relay deployment showing "not relevant"

I have a 2012 server that I’ve been trying to install the Relay on for several days with no success. The server doesn’t have any Relay installed, and hasn’t ever had it installed (it’s a new server). However, the fixlet for the Relay shows up as not-relevant to this server - despite it being the same (exactly the same model and image) as over 240 other servers where the Relay has been successfully installed.

I’ve attempted to clear my console cache, which didn’t help. I’ve deleted everything inside the __Global directory inside the C:\Program Files (x86)\BigFix Enterprise\BES Client\__BESData\ directory, which also didn’t help. I’ve tried a refresh of the server in the console, which didn’t help either.

I’ve read some posts that refer to a “force refresh” - I’m unclear if this is simply a refresh of this client through my console using the “Send Refresh” option in the context menu or if it’s in reference to something else.

I’m not sure what to do at this point - should I attempt to uninstall the client entirely and reinstall? I’m not understanding why a server could show up as not being relevant to the Relay fixlet when it should be, considering the Relay isn’t installed already.

If you’ve access to the server start the fixlet debugger and try out the various relevance clauses from the install fixlet.
That can help narrow down the problem.

Thanks for the information - that led me almost immediately to the problem. Apparently - and I have no idea how, since the BES root server is version still 9.0 - this system has the 9.2 version of the client installed.

2 Likes