topic Re: I can't access to intelligent provisioning via F10. in ProLiant Servers (ML,DL,SL)

I can't access to intelligent provisioning via F10.

Andrea Cicchelli — Sun, 07 Oct 2018 14:08:51 GMT

as in the object I can't access to intelligent provisioning via F10 , on ML350 GEN10

As suggested in other posts, I installed the Intelligent Provisioning Recovery Media for Gen10 v. 3.20 but the problem persists.

I can't access to intelligent provisioning via System Utilities.

I can access to intelligent provisioning via Ilo. Here we can the see the wizard for the first configuration. I can run the wizard until the end, and arrive to see in the browser a a screen with teh following message : "Intelligent provisioning api is not registered yet.please wait while the server is booting to itelligent provisioning.....". meanwhile the server switches off and on automatically and goes to the home screen with only the F10 button visible and active: but the intelligent repository doesn't start.

What can I do ?

Thanks
Andrea

Re: I can't access to intelligent provisioning via F10.

Suman_1978 — Mon, 08 Oct 2018 03:41:47 GMT

Hi,

You can try to clear NVRAM from System maintenance switch S6.

Refer to page#17, https://support.hpe.com/hpsc/doc/public/display?docId=a00016366en_us

Thank You!
I am an HPE Employee

Was the post useful? Click on the white KUDOS! Thumb below. Kudos is a way of saying thank you to a post.
Useful Links for ProLiant Servers

Re: I can't access to intelligent provisioning via F10.

Andrea Cicchelli — Mon, 08 Oct 2018 06:27:27 GMT

Thank you for your answer Suman but I have the solution and I apologize for my ignorance. I write the solution to help others: when you create the intelligent Media Provisioning Recovery for USB, do not use any software to create ISO images, but only the HPE USB Key Utility for Windows/Linux. As written in the instructions ... I had not read
Thanks

Andrea

Re: I can't access to intelligent provisioning via F10.

4bakra — Wed, 11 Nov 2020 07:58:18 GMT

It worked! Thanks you so much.

I did almost everything that found on web and could not fix the issue, just because, I was using Rufus.