Another ProLiant ESXi 4>5 upgrade question

So, I've been able to upgrade my ProLiant DL360 G5 thanks to the HP VMWare boot CD suggested in this thread: http://www.experts-exchange.com/Software/VMWare/Q_27651729.html

But now I wanted to do the same on a ProLiant DL380 G6 and got this error message:

screenshot
How do I resolve this? Any suggestions?

Thanks!
XeronimoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
are you using the HP version of ESXi 5.0?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If this is OEM HP ESXi 5.0 just continue with installation.
0
XeronimoAuthor Commented:
@hanccocka:

Yes, I'm using the HP version of ESXi 5.0
It's the same CD I used to upgrade that other ProLiant yesterday. There I didn't get those error messages (although I got the same error message in the Update Manager!), is that normal?

And so what you're saying is that I should force the migration (that's how the option is called)? I can't do it right now though ... the window of opportunity has closed ... tomorrow or on the weekend then.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Correct, its likely other drivers have been installed in the previous installation.
0
XeronimoAuthor Commented:
Hm, are you sure then that forcing the migration won't make me lose network access (since one of the problematic drivers is apparently the NIC one)?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
you got three options

1. do not upgrade
2. fresh virgin install
3. proceed with upgrade

any upgrade carrys a risk, and you will need to check upgraded server afterwards to check configuration before production.

resolving network issues, adding drivers, vswitches is straightforward.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
XeronimoAuthor Commented:
a. Ok, I'll try the upgrade (and pray ;)). But what if I need to add drivers later (for example to get network connectivity) again, how would I do that?
b. In the case of a fresh install I also need to redefine all the storage connections etc, right?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
a. upload the vib and install
b. you need to recreate everything
0
XeronimoAuthor Commented:
I did a virgin fresh install and it worked.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.