Hi folks,
Those who deployed Firefox patches before may notice that the server actually download/cache the installers for 15 languages before deploying the Fixlet.
It may not be a problem for most of you, but some with limited disk space may hope to optimize this.
We are planning to move the static download to dynamic download.
So BES server only download the languages that are needed and thus can save the disk space.
While as you know, dynamic download requires admin to add the download link/domain to the whitelist.txt file in BES Server.
Will you or your organization have any concern on this move?
Why can’t you expand the storage on your root server?
The firefox downloads should be going into the WebCache, which should roll over automatically as you run out of space, so it shouldn’t cause a problem.
If you cannot expand the storage on your root server, then you could have a single top level relay that you set to do the downloads directly itself rather than the root server. This would take the burden of web downloads and storage off of the root server and put it on the top level relay, which is much easier to swap out and rebuild as needed.
If you are going to stick with the plan as you have laid out, then it seems to me you are already going to be making custom Firefox tasks, so why not just make them for the languages you need and just remove the others? There is no reason to need dynamic downloads if you just remove the references to the downloads you know you will never need.