HP Onboard Administrator 4.30 – Keeping up with Industry Standards
As you may (or may not) know – time flows. Once you bought quite expensive piece of equipment you want it to be always up to standards and updated to its fullest. You want it to last as long as your project goes.
Vendors like to forget about it. It’s convenient to sell you new hardware every year.
I have terrible experience with DRAC/RSA/Onboard Administrator’s and ILO’s Java/ActiveX admin’s nighmares. ILO/OA are almost always needed in a time of crisis, so six month after last login you can expect almost for sure: something will go wrong with these interfaces.
Maybe it is a Java cache, java security exception, your newer browser, newer OS, few intalled patches – the story is always the same: you have to react quickly only to find yourself in a neverending loop ‚which element causes this?’
It forces you to have almost neverending supply of browsers, virtual machines with different OS’es, every one of them with different snapshots, every one of these snapshots is with different version of Java/flash/browser/patch set. We have a plan: when you want to use THIS function, you have to use THIS version. If you want to switch to another function, you have to use different version (again: OS/browser/java/patch set).
It’s a reversed version of Russian roulette – you have almost zero chances to find proper, working version at first 6, 12 or even 48 shots.
And no, the magic ‚cloud’ is not gonna resolve this.
My quite harsh words are caused by positive feedback from HP – with OA firmware 4.30 I can use Linux Google Chrome again for login, using Remote Console and managing blades.
Yeeey for me…
Buuuu for vendors.