- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Changing BIOS Password with Set-HPEBIOSAdminPasswo...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2024 09:08 AM - last edited on 02-12-2024 06:00 AM by support_s
02-07-2024 09:08 AM - last edited on 02-12-2024 06:00 AM by support_s
Hello. I've successfully updated dozens of BIOS passwords with the Set-HPEBIOSAdminPassword command, however I have one server that gives this error
"Error @{Category=Usability; Message=The BIOS administrator password is set. The settings cannot be changed unless this password is supplied in Connect-HPEBIOS."
I can successfully connect to the BIOS with the Connect-HPEBIOS command:
$connection224 = Connect-HPEBIOS -Address $iloServer222 -Credential $ilocreds222 -BIOSAdminPassword $BIOSPW
The password change is successful.
# Change the password
Set-HPEBIOSAdminPassword -Connection $connection224 -OldAdminPassword $BIOSPW -NewAdminPassword $newBIOSPW
Why does this one server request to use the Connect-HPEBIOS, but others do not?
Thanks
Dan
Solved! Go to Solution.
- Tags:
- Prolaint server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2024 01:53 AM
02-09-2024 01:53 AM
Re: Changing BIOS Password with Set-HPEBIOSAdminPassword failing on G9 server
Hi dangar,
Refer the procedure mentioned in this support site.
Regards,
Shiva_JR
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2024 06:20 AM
02-09-2024 06:20 AM
Re: Changing BIOS Password with Set-HPEBIOSAdminPassword failing on G9 server
Are you saying that I need to perform this procedure in order for the Powershell module Set-HPEBIOSAdminPassword to work? I'm trying to determine why most servers respond well to the Set-HPEBIOSAdminPassword command, but a few require the Connect-HPEBIOS command with the current password parameter.
I changed my script to logon with Connect-HPEBIOS vs Connect-HPEiLO. I think I answered my own question, but want to be sure it's correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2024 10:37 PM
02-11-2024 10:37 PM
SolutionHello,
Please refer doc: https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00020913en_us
Page 19: Establishing a connection to a Gen9 server
And then execute the command.
Thanks.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]