There’s nothing more frustrating than downloading an installer that assumes that you’re going to have internet access on the machine that you subsequently intend to run the installer on (called a stub installer).
For example, downloading firefox so that you can get to your enterprise storage arrays java based admin interface without the agony presented by internet explorer’s tendency to throw its toys out the pram over the certificate and the settings are locked down by IE policy, this policy, that policy and the other policy that all exist to make the environment so much more “secure” but actually just don’t allow anything, anywhere, ever. It’s secure!, it’s been signed off as being suitably unusable to prevent exposing ourselves to any kind of imaginary threat! Aren’t we clever?. No. Rant over.
It’s secure!, it’s been signed off as being suitably unusable to prevent exposing ourselves to any kind of imaginary threat!
I’ve probably digressed, I can’t tell. I’m too angry. And you are too probably, if you’ve ended up here. Installers that assume an internet connection are completely useless in the enterprise environment (best read in the voice of Clarkson).
Whats even more frustrating is that the stub installer is the only apparent option, judging by mozillas website. Well it isn’t the only option – you can still download the full-fat, stand-alone installer from their ftp site – but ftp is blocked by your firewall!