K1000 5.5 update screwed up my BIOS Revision custom inventory field
Last year I created a custom inventory field to detect the BIOS. It has been very useful in applying BIOS updates as I have my bioses for my Dell computers password protected. I detect the revision and if it is not the latest it will deploy the BIOS update. See this thread:
http://www.itninja.com/question/bios-revision-not-showing-up
Now with the update non of my workstations will show the returned value of the BIOS.
I am assuming something changed with the update on how it reads inventory but I kind of need this to work.
1 Comment
[ + ] Show comment
Answers (1)
Answer Summary:
Please log in to answer
Posted by:
dugullett
11 years ago
What are you using for your rule? Try this.
ShellCommandTextReturn(cmd /c powershell "Get-WmiObject Win32_Bios")
Comments:
-
I was using this command
ShellCommandTextReturn(wmic bios get smbiosbiosversion)
Seemed to work for a long time and that was what was suggested on the forum post I linked above
Your command works too and shows even more information.
I have had some actually report in using new labels reading the BIOS version with the built in inventory options - bwilkerson 11 years ago-
You'll need to add "cmd.exe /c" to get it to work.
ShellCommandTextReturn(cmd.exe /c wmic bios get smbiosbiosversion) - dugullett 11 years ago
-
Is that new?? - bwilkerson 11 years ago
-
Well I'm not sure if it was planned, but that's how I got mine to work in 5.5. I'm fortunate enough to have a test VM. I make sure all of my custom inventory works before I update. I still haven't updated my production box. Trying to find some time. - dugullett 11 years ago
-
Well I thank you much for your expertise.. Fortunately I have not run into any issues other than that and only have the BIOS updates to install when there is no one logged in as it forces a reboot. This saves so much work and still allows me to password protect my BIOSes. I have a script that uses the Dell Configuration utility to set my BIOS settings on new Dell computers including the password set and then I can update my BIOSes simply by editing the label to the new BIOS revision number and uploading the new BIOS exe file. The only hard ones are the laptops not left idle at the login screen very often. - bwilkerson 11 years ago
I think I had this trouble with the last revision of the KACE which is why I went the custom inventory route. - bwilkerson 11 years ago