Why are no BigFix Clients showing in the BigFix Console after setting my proxy?
If this error occurs for the actionsite only and the other sites, like Enterprise Security and BES Support, are successfully downloaded, then it is likely the BigFix Server is unable to communicate with itself.
Resolving the problem
Check the Client log - location by default is: C:\Program Files\BigFix Enterprise\BES Client\__BESData\__Global\Logs
Do you see repeated error messages about a failure to gather the actionsite?
These will look like this: At 14:51:50 +0100 - actionsite (http://besserver.mynetwork.com:52311/cgi-bin/bfgather.exe/actionsite)
FAILED to Synchronize - General transport failure. - 'http://besserver.mynetwork.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://bes.itiso.net:52311/cgi-bin/bfgather.exe/actionsite?Time=11Nov14:51:47?rand=a3be0c2a' http failure code 404
If this error occurs for the actionsite only and the other sites, like Enterprise Security and TEM Support, are successfully downloaded, then it is likely the BigFix Server is unable to communicate with itself.
If the BigFix Server is set up to use a Proxy, you can solve this problem by making an exception on the BigFix Server for 'http://besserver.mynetwork.com'. The exception will allow the Server to not use the proxy for any URL that begins with the hostname of the Server, besserver.mynetwork.com in this case. The BigFix server will then know not to use the proxy when reaching itself.
You also should consider excluding all internal communications so that they do not go through the proxy. For instance, excluding *.mynetwork.com will allow the BigFix Server to be more efficient when contacting relays because it will not need to go through the proxy.