blog  bookmarks  archives  about

Search:

HP Network Configuration Utility for Server 2008 R2 (resolved)

13 September 2009 | server 2008 r2 | 10 Comments

UPDATE: HP has updated their drivers to include support for Server 2008 R2. The version number is 9.80.10.0.

If you look inside the cp011548.xml file, you will see the following:

As you can see, Server 2008 R2 is listed as a supported OS. There is no longer a need to make the changes.

However, if you want to extract the contents of the executable, use Winrar or 7-zip. Once you open the executable, you will see all the files that it contains. See below.

We’ve wanted to start testing Server 2008 and SQL 2008 and eventually begin a migration process from our current environment of Server 2003 and SQL 2005. We purchased some blade servers with two BL680c servers allocated for our new environment. I began prepping the servers first with Server 2008 R2 since it was available for us to use. This wasn’t our first time installed Server 2008, but it was our first time installing Server 2008 R2 on our blade environment.

The install of the operating system went smooth. We were able to install the Proliant Service Pack 8.21 without any issues as well. However, we did run into one problem – the HP Network Configuration Utility would not team our NICs. We were able to team two of the NICs, and it looked as if it successfully teamed them. Yet when we looked in the Configuration Utility, it showed no teamed NICs. Weird. When we looked in the Network Connections applet, they showed as disconnected. After a restart, the teamed NIC was gone.

After searching HP’s site for an update, we found version 9.70 available for download; we were running version 9.60. After checking out the enhancements tab, it showed that there was support for Server 2008 R2. Perfect. We downloaded the update and tried to install it on the server. This is when we ran into our next hurdle – the error message stated that the update was incompatible with our operating system. That seemed odd since it was for Server 2008 x64 with support for R2.

After some searching around, it seems that we weren’t the only ones who were experiencing this issue. However, the sites I came across didn’t have resolutions to this problem, so I called HP support to find out what was going on.

After speaking to a service rep, he informed me that Server 2008 R2 hasn’t been certified for the BL680c. He forwarded me the Proliant support matrix for Server 2008 R2 (see left), and the only system that was shown as supported was the BL460 G1 series. That does me no good. Unfortunately, he also had no time table as to when it would be certified, but he did send me the link for the Proliant Support Pack for Server 2008 R2, but it was in the beta stage. I didn’t want to run the risk of installing beta software on our servers which were slated to enter production in the near future.

I’ll just have to keep checking the site and hope that our servers will certified before they enter production.

UPDATE (09/17/09): Diego, from HP, left a comment on how to resolve this issue. Thanks Diego for the tip!

I tested it out and it worked with no issue! I did have to update the drivers for the NICs as well. After that, I had no issues teaming the NICs.

Here’s what I did.

First, I edited the cp010849.xml file and added the following line to the subsection labeled "SUPPORTED_OPERATING_SYSTEMS" under the "PREREQUISTES" section. See the image below if you need to see what the final output should be.

supported_operating_system platform="nt_x86-64" major="6" minor="1" sr="OEM" name="Microsoft Windows Server 2008 R2"/

NOTE: In order to edit the file, you’ll have to extract the contents of the downloaded executable to your drive first.

Once I made the changes to the file, I re-ran the setup and was able to install the updated software. See below for screenshot.

10 Comments

1. Diego Ordonez said on 15 Sep 2009 at 10:24 am:

   Hi,

   I am a support engineer for HP ProLiant Technical Support. We just saw this issue this morning. The problem is a small line missing in the installer code, that needs to be added in an XML file on the installer.

   Engineering has already been warned about this. If you want, you can use NCU 9.65 as a workaround. As for now, I just notified engineering this morning.

   The fix is basically to add the line:

   In the file cp010849.xml (Being NCU 9.70 for 2008 x64), in the section PREREQUISITES -> SUPPORTED_OPERATING_SYSTEMS.

   Add that line, save the file, and you should be all set.

2. Diego Ordonez said on 15 Sep 2009 at 10:26 am:

   supported_operating_system platform=”nt_x86-64″ major=”6″ minor=”1″ sr=”OEM” name=”Microsoft Windows Server 2008 R2″/

3. Reuv said on 13 Oct 2009 at 6:32 am:

   You need to fix the text listed above, replacing the ‘?’ character with an “end quote” for each paramater, as shown in the final screen shot. Looks like a cut ‘n paste issue.

4. jim said on 13 Oct 2009 at 7:57 am:

   Reuv,

   Thanks for catching that! I corrected it.

5. James Mackay said on 16 Nov 2009 at 10:43 am:

   Nice catch – I’ve ben wondering why I couldn’t get the HP NCU to install… (Worked on my DL360 G6s as well)

6. Srikanth & Vijayraj said on 28 Dec 2009 at 11:01 pm:

   We had the same issue in HP DL360 G4 and with NCU 9.70.0.0. We did the work around suggested and could successfully install the same.
   Thank you all.

7. Primoz Peternelj said on 18 Jan 2010 at 2:18 am:

   Nice work you all. But I still can’t find cp010849.xml file.
   I have Server R2, and it saids it is not supported. But it seems like it doesn’t extract anywhere…
   I’ve looked in systemroot\cpqsystem\cpxml but it’s not there.

8. James Nightingale said on 20 Jan 2010 at 11:58 pm:

   Same here… I cannot find this XML file extraction. Please email me if you know the answer.

9. jim said on 21 Jan 2010 at 12:17 am:

   I just took a look at the new version, 9.80.1.0, and it looks like they have updated the file to include Server 2008 R2. There’s no need to edit the file anymore.

   The filename for version 9.80.1.0 is cp011548.exe for 2008 R2, and it’s cp010849.exe for 9.70.0.0.

   If you extract the contents of cp011548.exe and look inside the cp011548.xml file, you’ll see the following line:

   supported_operating_system platform="nt_x86-64" major="6" minor="1" sr="OEM" name="Microsoft Windows Server 2008 R2"/

   If you are having problems extracting the contents of the executable, I would recommend opening the file with Winrar.

   I’ll update this post with the new info.

10. Tom said on 27 Jan 2010 at 2:54 pm:

    download link here:

    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=MTX-0282535b5f334232ab338711d0&prodTypeId=15351&prodSeriesId=397634

You can follow the discussion through the Comments feed. You can also pingback or trackback from your own site.

© 2010 jim jacob, proudly powered by tiny and wp.
Feeds: Atom, RSS.