Depends on the string (and the format of course).
Dell is pretty consistent with their Axx format for most of the Dell systems that I have seen. So using the operator in this case does work properly (i.e. ‘A12’ < ‘A13’).
However, not sure that SMBIOSMajorVersion/SMBIOSMinorVersion will work as expected on Dell Systems, as that version doesn’t seem to change with BIOS version changes.
Here a D630 with BIOS version A13:
![]()
And here is a D630 with BIOS version A04:
![]()
Mike Terrill | Systems Management Practice Lead | 1E |
Mobile: (480) 862-9137
US/Canada Toll Free: (866) 592-4214
mike.terrill@1e.com | www.1e.com
Only problem is > will not work reliably with a string, and the "A" in it makes it a string.
You could say = 'A13' and use NOT logic, but what happens when you get something with a newer bios? I would be concerned it would run then....
Hence the major and minor version queries.
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Mike Terrill
Sent: Thursday, July 09, 2009 12:50 PM
Subject: RE: [mssms] ConfigMgr OSD - PXE boot menu for BIOS updates?
Expanding on Todd’s query below a bit for Dell Systems might look something like this:
select SMBIOSBIOSVersion from Win32_BIOS where SMBIOSBIOSVersion < 'A13'
as the Version field on my D630 displays “DELL - 27d8071c”
Mike Terrill | Systems Management Practice Lead | 1E |
Mobile: (480) 862-9137
US/Canada Toll Free: (866) 592-4214
mike.terrill@1e.com | www.1e.com
SELECT Version FROM Win32_BIOS Where Version < 3.3
Assuming you want to update anything less than 3.3. It will return true if the version is less than 3.3, this running the step, otherwise it will skip it
put that in a TS condition > wmi query
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Benjamin Monrad
Sent: Thursday, July 09, 2009 12:10 PM
Thanks, guys.
Part of my idea was to be able to update BIOS on the fly before starting the OSD TS, but maybe it will just be easier to add the BIOS update to the TS after Windows is installed.
I already know how to query WMI for the Model, but is there a simple way to query the current BIOS version as a WMI condition for the TS step so we don't re-install the current version? I saw a thread on that earlier but it didn't seem that straightforward.
-ben
It may not even be necessary to use PC-DOS depending upon the type of system it is. On Dell systems, you can deploy BIOS updates using the –nopause and –noreboot command-line switches. On HP systems, you can use HPQflash.exe in a silent mode. I’m not sure if you can do this from WinPE or not, but you can always do it from Windows after it’s installed in your task sequence.
-Trevor
They way you are describing it, I'd probably look into using the pre-execution hook with a wizard/option for your choice of Build System, CMD Window, etc. I am not sure about actually booting to dos but I don't see why WinPE wouldn't be able to handle the same bios update request. (Have not tried that theory)
Hi,
Something we used to do from the Ghost PXE boot wizard was a PXE boot menu that defaulted to an option to join a standing Ghost session after a short timeout period, with other options to boot (per-model) to PC-DOS and run a BIOS update.
I am curious about doing the same sort of thing with the ConfigMgr OSD boot image, so that a menu would come up that defaults to the ConfigMgr OSD boot wim, but could be intercepted to boot into PC-DOS or WinPE to do the BIOS update... I looked into it once before (before I actually had OSD PXE up and running all the way) and I got close, but couldn't get it quite right.
Is that something that I would be able to do by customizing the WDS boot files with BCDedit, or would there be a better way to do it, maybe with a Pre-Execution hook?
I know we could theoretically push the BIOS updates with DCCU, but most of our clients are laptops and I am concerned about the advertisement hitting clients when they are not plugged in to power, and failing with alerts that will confuse the end users.
Thanks.
-ben
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
--
-------------------------------
Jason (Schuff)
-------------------------------
DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of this email address. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
==============
