If you're OK with using the device description for this:
blcli ProvisionDevice setDescription xx-xx-xx-xx-xx-xx "svc_tag"
And what would it take to execute this during pre-boot? What would need to be included in the WinPE image?
You'd have to execute that from a machine where NSH is installed (obviously), but if you're only provisioning Windows, then this becomes significantly easier than it would be with Linux.
From windows, you'd essentially need to do something like (or similar) to this:
1) place bios util on data store
2) from system package, map drive to data store
3) execute bios util from data store redirecting output to a txt file w/ the appropriate output (service tag for example)
4) unmap drive
5) script and/or automate execution of a CLI / Jython script that calls the CLI call referencing the service tag in the file
Depending on how this all were to be implemented, you could have synchronization issues if more than 1 machine write to the output file at a time. So while not ideal, it could work. I'm sure there are plenty of improvements upon my suggestion here, so I'm all ears as well.
If you're doing linux provisioning, I'm still thinking on possible workarounds.
Thanks for the solution. This will definitely work for Windows. As for Linux, do you think it would be possible to include NSH in the WinPE image? If this is possible, I suppose it would work for both Windows and Linux.
if you're using winPE as your default boot image, then this shouldn't matter. pre provisioning scripts execute w/ the "current" boot image whatever that may be. so if winPE is your default, then you can do what I suggested before. if your default is the Gentoo image, then another approach may be needed...
WinPE is the default. No need to complicate things :) Thanks for the help Dan!
doesn't 7.4.2 already populate the 'serial_number' property by default now? (maybe just the 7.4.2 bmi w/ 7.4.1 ?)
on a dell, the serial number should be the same as the service tag.
There does not seem to be a released/unreleased command for grabbing device properties :(
Does the "BIOSCFG.EXE --svctag" utility reside in the dtk or winpe or somewhere else?