(imported comment written by WeylanWang)
For content that you are āstuckā in pending download.
This can be for a number of reasons. And can be quite complex.
what pending download means, is that the agent has reported that the agent does not have the download. The agent has asked the parent for the download, but the agent does not have the download yet.
So there are a number of reasons for the download to not be available.
It could be relay related.
It could be server related.
It could be internet source related.
You can diagnose this top down or bottom up.
If you diagnose this bottom up, you start at the agent and you check each relay till you get to the internet for the file.
You check the agent. Does the agent have the file?
Then you check the relay. Does the relay have the file?
Then you check the parent of the relay. Does that relay have the file. ⦠Until you get to the server.
Then you check to see if the server has the file. If the server does not have the file.
You check the server can get the file from the internet.
If you are checking this top down, you first check if you can get the file from the internet.
Then you check to see if the file is on the server.
Then you check the relays.
Then you check the agent if it is geting notification that the file is available from the relay. And that the agent can get the file.
You can check the relay or the server has the file by checking the download status page on the server or the relays. By using this URL:
Download status
http://127.0.0.1:52311/cgi-bin/bfenterprise/besmirrorrequest.exe
Given this page, you can see it refers to the āloopbackā. But you can substitute the TEM server, or the relay address. Once you know where to look for the the downloads, and you know the action ID, you can find the action ID and see if for the action ID the download is ready.
You can also go to the server/relays and check to see if the file is in the SHA1 directory.
C:\Program Files\BigFix Enterprise\BES Server\wwwrootbes\bfmirror\downloads\sha1
The SHA1 directory if you look the the action script for the action you should see a line that refers to the
prefetch ā¦
This line list the SHA1 and the SHA256 value for the download, and you should be able to find a file in the directory for the download.
If all of this is true, then the agent should have the download.
Otherwise you need to look in the agent log file to see other reasons the file might not be there.
As a reminder, some patches have issues with downloads from the vendor (Microsoft, Adobe, ā¦) The file we refer to in the Fixlet changes. If this happens, you can have the pending download if the vendor removes the file. This is because the Fixlet in the current state will refer to the file as a snapshot in time when you made the action and deployed the file. If this is the case then if the file ever gets cleared from the cache, the file will not be available. And you may have to deploy the Fixlet again with the new SHA1.
As a reminder some Microsoft patches require manual downloading of the files. It depends on the Patch. In the Fixlet we document if the patch must be downloaded manually. PLEASE check the description of Fixlet for notes of if the patch must be downloaded manually.
Please post some more if you need more help with this. But while this seems like a simple thing it is pretty complicated and a lot of places to check for problems.