Hello,
I am working on setting the wake on lan setting in the bios to on for remotely turning on pc's at night to install updates. The question i have is how can i validate the current status of WOL on a machine?
Using the Dell Client Configuration Utility, i can create a package that will read BIOS settings, and write BIOS settings. Once it completes, it creates an XML file with its findings.
Is there a way to have landesk pull this information, or do i need to write some sort of vb script to parce the xml file and create a custom reg key to report against?
Has any one already one this?
Thanks in advance.
- Steve
Sounds like you should parse it and create a custom registry key. LANDesk doesn't handle XML files so you need to do something externally to the scanner. Maybe someone has the script? If you do it yourself, just remember that the easiest place to put it is in the LANDesk customer registry area
HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\Inventory\Custom Fields
Mark Star - MarXtar LANDesk Enhancements
Home of Power State Notifier & Wake-On-WAN for LANDesk
ldms_client already speaks XML, send me some sample files with and without the value you need and I'll add it,
Attached you will see the 2 xml files that are generated.
I am not Familiar with LDMS_client can you elaborate on this for me?
What i would need is for it to grab the value out of that file, which in this case is 6. The values co-inside with the status of the WOL setting:
2: Unsupported
3: Disabled
4: Enabled for add-in NIC
5: Enabled for on-board NIC
6: Enabled for all NICs
7: Enabled with boot to NIC
If i can have the state (2-6) dumped into the inventory scan, i can run reports\queries based on that field. This will enable me to verify that i have the proper settings on all my dell machines.
The Dell Client Configuration Utility will create packages to either get values from, or set values on the bios. The package it creates runs silently, and generates the files attached. So really all i need to do, is make it so it runs the package, sets reg value based on the value in the xml, then kicks off an inventory scan, so i can report against it.
Please let me know what you think.
I just found a new version of the Dell Client Configuration Utility Released 11/19/08
ldms_client is an inventory extension tool. Its website is here: http://www.droppedpackets.org/inventory-and-slm/ldms_client/
How are you running DCCU? Is it on a network share, or on each computer? Where does it install to and where does it write its file?
The package will be sent down to the client via a software deployment. When the package runs, it deletes itself, and leaves the xml files behind in the same folder.
sdmcache? or ldclient? Tell you what, I'll look for the xml files in ldclient... that way you can mod your package if necessary.
The new Dell Client Config util is web based for some stupid reason, and does not seam to be that intuitive as the older version.
IT only works in IE, and the output is a bit different. See attached file with the EXE's and the output. They also no longer delete them selves unlike how the old one was.
But the newer version supports the latest machines. Although this version has Altiris written all over it.
Just wrapping stuff in tag markers doesn't exactly make it XML... It's faster and easier to process this as a regular text file.
Here's a hint of the direction I'm taking... I'm giving produkey the same ability to specify where the exe lives, too. In produkey's case, I suspect that will allow you to leave its binary on the core server and do it over the network, but that's untested. getwol.exe doesn't look like it could handle that.
I haven't even looked at supporting the DCCU 3.x stuff, it's probably possible, though. Anything's possible given enough time and money, as the consultants say.
Anyway, I just uploaded ldms_client 1.8 if anyone would like to give it a spin.
ok i will play with this for a few. ill get back to you. Thank you for your hard work.
The new client does not autodelete itself, and it inventorys the whole machine, which if scripted right could be a useful addtion to the database.
I figured out how to use do the newer inventory.exe too, it's not finished yet but should be in the next release.
Sweet will you have it dump the full inventory of the bios, or just the WOL?
| ||||||
