Query: Firmware update – User token USB key required?

[rznr]

Hello everyone,

we got some new "ProLiant DL380 Gen10"-Servers for our company. When trying to apply the suggested firmware updates for hard drives etc. we are prompted for a USB key user token (see picture below). What is this? Are we not able to just apply the firmware updates without any further authorisation?

Thank you in advance,
rznr

[support_s]

System recommended content:

1. Updating firmware

If the above information is helpful, then please click on "Thumbs Up/Kudo" icon.

Thank you for being a HPE community member.

[Torsten.]

What firmware and update method do we talk about?

[rznr]

Thanks for the replies.

I thought there was only one update method. Unfortunatly I cannot access the server to look up the update method at the moment. I get back to you when i can.

Regards,
rznr

[Torsten.]

There are dozens of upgrade methods ... please tell the details.

[rznr · Accepted solution]

Now i got it. The update method i use is via intelligent provisioning after booting up the server ("Server maintenance" -> "Firmware update"). I inserted an empty usb flash drive and got an additional popup which told me exactly what to do:

• Go to the website https://support.hpe.com/hpesc/swd/entitlement-token-service/generate and generate a user token
• Save the token in a file named "user_token.txt" to an usb flash drive
• Insert the flash drive into the server before the firmware update

-> Now you can start the updates.

Regards
rznr

[ljkhlkbljhvgkhg]

OH MY GOD, what is this stupid piece of *****!?
Can't we just update firmware without being tortured with useless stuff like that?

Now the deployment of a server gets delayed because I have to wait for someone to connect the stupid USB stick to the server.

This is just utterly, utterly stupid and ridiculous. We are burning our time, installing fixes for bugs which were introduced by  HPE themselves in the first place and as a bonus they just torture us all the way through the process.

[Torsten.]

Why not just booting the current SPP?

Any reason to struggle with IP?

[ljkhlkbljhvgkhg]

why not use a (supposedly) convenient feature if it is there?

also, the server is located thousands of km away and has a bad internet connection to my location. the remote iso boot process would most likely take ages and/or abort.

i've managed to get another machine on-site running however, from where I'll do the iso boot. still unbelievably annoying.

[Jackson0000]

Sound like illegal user token key to pass for access.... FUNNY HPE.... HPE should put user token in their own website to generate. we can enter private and copy user token.

is it all for people to use user_token.txt that you give us so easy?