KACE Product Support

Hello,

The attribute value you're looking for in KACE is "BIOS Serial Number:". You'll find it on the Inventory tab, click any Dell computer object to view the details and then expand the Hardware section.

I've actually used the BIOS Serial Number as the association between Inventory items and our Assets in KACE. This will help to ensure you always have a way of uniquely identifying your Assets and associating them with the related Inventory item. You can find additional details on this if you look up Asset Import in the Admin Guide.

Hope this helps,

The BIOS Serial Number is separate and can be different from the Asset Tag field available on Dells. I don't know of a way to gather that Asset Tag field in the Dell BIOS.

Thank you for your note Jason, but the BIOS Serial Number is actually the ServiceTag on the device as defined by Dell.

There are other fields in BIOS where additional information can be stored, it just seems the inventory scan is not pulling the information, or the application is not displaying the information. In our situation for example, with Dell, there is an Asset Tag utility (http://search.dell.com/results.aspx?c=us&l=en&s=biz&cat=sup&cs=555&k=asset+tag+utility&img=True&sum=True&qmp=10&p=1) that users can download and boot from. This tool allows one to manually enter data into the Asset Tag field in BIOS. We simply have Dell perform this work at the time the machines are purchased.

We currently use this information from within our LanDesk solution (which reads this information automatically on inventory scan) and we are looking for Kace to fully replace. We use the unique organization assigned Asset Tag since it contains data about year of purchase, etc.

Any other ideas?

Thanks for the correction RichB, the Asset Tag and the Service Tag are two different values. The BIOS Serial Number is associated with the Service Tag.

One possibility is to do an import of a csv file which lists your Asset Tag to Service Tag mappings. This could then be linked to an asset during the import process where you'd create a new field for the Asset Tag value.

Thanks,

Thanks J, but that pretty much defeats the purpose of and investment in an automation/management solution, right? :-P

chollandjr,

Do you know where this information is kept in WMI?

If so, what you can do is write a script that retrieves this value from WMI and writes it to the registry.

After that create a custom inventory field that returns this information.

Yes, I agree with Dchistian. I have some tools available which can write the script upon chosing the field from WMI. you can find

MICROSOFT WMI CODE CREATOR[/align]over internet

We would also like this feature too
has anyone come up with a solution? We use spiceworks to do inventory and it is able to pick up the info. I do not know why this cant be added to Kace aftre all this is now a Dell product and the asset tag utility came from Dell. If anyone found a way to scritp this or add this please respond

http://msdn.microsoft.com/en-us/library/aa394587%28v=vs.85%29.aspx

Use the Win32_SystemEnclosure class, and the properties SerialNumber and SMBIOSAssetTag.strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" _
& strComputer & "\root\cimv2")
Set colSMBIOS = objWMIService.ExecQuery _
("Select * from Win32_SystemEnclosure")
For Each objSMBIOS in colSMBIOS
Wscript.Echo "Part Number: " & objSMBIOS.PartNumber
Wscript.Echo "Serial Number: " _
& objSMBIOS.SerialNumber
Wscript.Echo "Asset Tag: " _
& objSMBIOS.SMBIOSAssetTag
Next

This is a script we are using in K2000 (Deployment) to name the PC. Dell is adding this information to the Asset Tag field when we purchase machines.

I think looking at the other script that is posted, that this is pretty much the same...except for the end part where we change the Windows Computer name, to match what is in the BIOS asset tag field.

strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" _
& strComputer & "\root\cimv2")
Set colSMBIOS = objWMIService.ExecQuery _
("Select * from Win32_SystemEnclosure")
For Each objSMBIOS in colSMBIOS
Wscript.Echo "Asset Tag: " _
& objSMBIOS.SMBIOSAssetTag


sNewName = TRIM(objSMBIOS.SMBIOSAssetTag)


Set oShell = CreateObject ("WSCript.shell" )

sCCS = "HKLM\SYSTEM\CurrentControlSet\"
sTcpipParamsRegPath = sCCS & "Services\Tcpip\Parameters\"
sCompNameRegPath = sCCS & "Control\ComputerName\"

With oShell
.RegDelete sTcpipParamsRegPath & "Hostname"
.RegDelete sTcpipParamsRegPath & "NV Hostname"

.RegWrite sCompNameRegPath & "ComputerName\ComputerName", sNewName
.RegWrite sCompNameRegPath & "ActiveComputerName\ComputerName", sNewName
.RegWrite sTcpipParamsRegPath & "Hostname", sNewName
.RegWrite sTcpipParamsRegPath & "NV Hostname", sNewName
End With ' oShell


Next

thank for your post
i actually found this exact vbs script and called kace and we got it all working
i had them help me with a cutom inventory field and i was happy
unfortunalty i did an upgrade to my server and clients
i am so happy Dell did me a favor and made everything more complicated.
now my script doesnt work anymore and Dell is saying that the vbs doesnt put the asset tag txt file on the c:\drive like it use to
i am poistive i didnt change anything and i thought it was Kace that got the information from the script to write it in a file, then the cutom inventory picked up the info
long story short
how do you run this in kace? what exactly do you tell kace when you are runnning this so i can get my info back
WHAT DO YOU SAY IN THE SCRIPT
NOT THE VBS SCRIPT BUT THE KACE SCRIPT?
THANKS A BUNCH
S

What i would do is create this as a shell script.

You could then upload the VBS script as a dependency.

You command would be:
cscript nameOfYourScript.vbs
Make sure you change the script name from script.sh to script.bat (box just below script text).

Also if all your doing is renaming the machine you might want to take a look at wsname

The $ASSETTAG variable should do the same thing.