- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Updating AssetTag in Instrumented BIOS
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
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
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
07-04-2014 07:32 AM
07-04-2014 07:32 AM
Updating AssetTag in Instrumented BIOS
Hi All,
In order to try to change the AssetTag in a Proliant Server I've entered in Powershell:
$a=Get-WmiObject -Class “HP_SMBIOS_ProcessorInformation” –Namespace“root\HP\InstrumentedBIOS”
$a.AssetTag ="123456"
$a.Put()
It's returned the following error:
Exception calling "Put" with "0" argument(s): "Not supported "
At line:3 char:1
+ $a.Put()
+ ~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
Does this mean that the AssetTag property is not editable?
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2014 11:42 PM
07-06-2014 11:42 PM
Re: Updating AssetTag in Instrumented BIOS
Hi!
I don't know if its that same Asset tag that you are speaking of, but HP has release a HP scripting toolkit for windows powershell that contains a CMDLet thats called set-hpiloassettag that has the description sets or clears the asset tag. There is also get-hpiloassettag to see the current value.
http://www.hp.com/go/powershell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2014 07:11 AM
07-24-2014 07:11 AM
Re: Updating AssetTag in Instrumented BIOS
Many thanks Cederberg!
Haven't resolved this yet, but your advise has moved me closer and provided some pretty useful powershell commands to boot.
Now after installing the HP PS commands, I enter the following:
Set-HPiLOAssetTag-Serverlocalhost-Username ******* -Password "**********"-AssetTag '301176'
This seems to execute ok, but then when I try to retrive the value with
Get-HPiLOAssetTag-Server LocalHost-Username *******-Password '**********'
I get the following:
S C:\Windows\system32> Get-HPiLOAssetTag -Server LocalHost -Username HPSIM -Password 'g)8c(bo5w&O)&&)1@'
PS C:\Windows\system32> Get-HPiLOAssetTag -Server LocalHost -Username ****** -Password '********'
IP HOSTNAME STATUS_TYPE STATUS_MESSAGE
-- -------- ----------- --------------
::1 127.0.0.1 LocalHost ERROR No information available
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2014 07:31 AM
07-24-2014 07:31 AM
Re: Updating AssetTag in Instrumented BIOS
Just an update on the above, I think I've found what the issue is with the above, I believe that what is prevention my write to the AssetTag are the ILo permissons on the device in question, apparently VirtualMedia, ResetServer and RemoteCons privileges are required - and these are set at boot on the device.