Removing Japanese firmware from Version Control Repository

[Sander-A]

Do I have to remove each instance of Japanese firmware to keep my ilos from being upgraded by mistake or is there a more systemic way of doing this?

TIA

[HotFix]

We just upgraded our VCR to version 7.1 to see if there was some new features to help with this and there appears to be some sort of archive function we haven't played with yet.

Unfortunately upgrading from 7.0 to 7.1 seems to have dorked our repository as several "rescan repository & update catalog" were not able to properly reflect everything in the repository. So... we decided to wipe the repository and start over again and it's almost done downloading.

Meanwhile we are hoping we can delete the Japanese iLO firmware from the list and that it will stay deleted even though the repository is configured to automatically udpate once a week. I.E. We hope it won't re-download them.

The archive functionality looks promising, but it looks to be unclear if we can combine the "Select bundles/components to Archive using below list" and the "Select bundles/components older than X recent version(s)". It doesn't look like though we can archive everything older than X recent versions and also add individual items such as the Japanese updates.

Either way we agree HP needs to give us a way to proactively exclude Japanese only updates. Combined English and Japanese updates seem to be fine.

[Sander-A]

Funny you should mention it I have been having problems with unmet dependancies in the Version Control Repository recently maybe it was when I upgraded to 7.1.

For exampe when I try to update the HP Insight Management AgentsI get the following error which has been driving me nuts:

For the following components the minimum dependent components are not available in repository

HP Insight Management Agents for Windows Server 2003/2008 x64 Editions version

I keep rebuilding and downloading, but the error on the vcagent doesn't specify what dependency is missing. Maybe I need to wipe and start from scratch too.

[HotFix]

We had to basically dump our repository and start over as well because we couldn't just get the reinventory to work properly. Starting over took over a day to redownload and inventory everything. We deleted the Japanese iLO firmware and are crossing our fingers it stays deleted. The rest of my response goes off topic, but I really wish HP would allow us to determine which languages we download so the wrong language version doesn't get applied to our servers.

Then we had to relink SIM to the repository and that took several hours.

Then we had to go onto one of our servers and select the baseline we wanted, which was the new HP service pack 2012.06.0B and then then use SIM replicate this agent setting out to all of our servers. This is despite the fact that we had used the Manage Software/Firmware Baselines to supposedly push out the setting which didn't seem to do anything but make SIM think they were on the baseline.

Now that servers are once again pulling from the VCR, they show the "HP ProLiant Smart Array SAS/SATA Controller Driver" as being installed but not being in the baseline (there is no check box) and that there is no latest version (there is no check box here either). They are currently at version 6.20.2.64 when there is a 6.24.0.64 version listed in the 2012.06.0B service pack, installed in the VCR, and we configurmed the VCR thinkss the new 6.24.0.64 driver is linked to the service pack.

So we are still not 100% recovered from the rebuild and aren't sure how to get this driver and potentially other updates to show up on these servers. I feel like we should get PHDs after getting this all fixed...

[Sander-A]

It is ridiculous that they can't get the Japanese issue resolved after at least 4 years that I'm aware of.

The primary use of SIM for our organization is leveraging its connection to HP hardware. If they can't get this one thing right on top of their limited data gathering, inconsistent documentation and other issues we're probably just going to pull the plug on the eventually.

[HotFix]

FYI HP support got back to me and said they could reproduce the issue where the driver did not appear to be linked to the service pack, and they indicated this was a bug with VCR 7.1. After following their instructions and downgrading to VCR 7.0, it worked as expected.

Meanwhile when I try to update my HP servers, for whatever reason the VCA doesn't show the iLO firmware as being a part of the service pack, probably because I removed the Japanese only versions (shame on me...), and every time I try to push an update to the server I get an error message that it couldn't install the X86 driver pack on an X64 server. Why on earth it is trying to deploy an X86 driver pack on an X64 server is beyond me.

I have to manually install cp016891.exe and cp016189.exe to get them to apply, and then I can finally get the rest of the updates to go thorugh the VCA process. I still get an error message as it still tries to push the X86 version of "HP ProLiant iLO 3/4 Management Controller Driver Package for Windows Server" for some unknown reason, but a reboot yields the server coming back all green in the VCA.

Now if I can only get HP SIM to understand the VCA on these servers is up to date... Software polling seems to work 4 out of 5 times, and the 5th time is just stubborn and will never update the updated status.

The VCR and SIM are really sucking these days.

[Dave DuVal]

Just piling on, but I also think the language issue needs to get fixed.  I had to force the correct version onto several servers that got the wrong language version.  The other comments in this thread about the 7.1 repository not correctly recognizing components it has downloaded is also a problem.  I am hoping for a solution other than back reving to SIM 7.0.