KACE Product Support

You can do this using custom help desk rules, but DellKACE discourages inserting data into tables (which is what you would be doing by creating assets based on IP scan results). Is it possible? Yes. However, it's a bit dangerous to perform this type of database modification. Also, writing the rules is going to take some time, as they are rather complex.

Thanks for the info Airwolf.

Is there any way I can link an Asset record to a device discovered by the IP scan? (within the Kbox's existing functionality)

I could just create a new text field within the Asset and manually enter a unique identifier for the device. i.e. if the IP scan found a printer and it's hostname is PRINTER1, I could manually type in PRINTER1 in the new Asset field. Then, when a user needs to know when the printer was bought, the Asset record would tell them, and if they wanted to know its IP, they could search for the unique identifier (PRINTER1) in the IP Scan results page and find the printer.

This kind of takes the fun out of the Kbox though!

If anyone has any suggestions of how I could do this better it'd be much appreciated. Even if it were possible to choose an IP Scan discovered device from a dropdown list field in the Asset would be slightly quicker.

There is absolutely no way to link IP scan data to assets without the use of custom SQL rules in the helpdesk.

That is a shame, thanks Airwolf.

I'll submit a support ticket with Kace to see if they have any other ways I can work it to achieve the same without touching the database tables.

I'm not saying the end result you are looking for is not possible, it's just a bit risky. It all depends on how far you want to push your KBOX. Virtually anything is possible (database-wise) with custom help desk SQL rules.

On a side-note, I'd love to see an automatic link for IP Scan results and assets. I've already submitted a feature request for this, and I'd suggest you do the same (enhancement requests are sent in as support tickets to DellKACE - you'll see it as a "priority" level).

Hi airwolf

On a side note but still kinda relevant to the topic - can you show me an example of a custom Helpdesk SQL rule?

Say for example, I wanted to populate a field called AuditDate in all my assets by external means e.g. run a script that sets all asset's AuditDate field to 01/09/2010.

Whats the first step?

For updating only PCs running XP I guess it would be something like:

UPDATE MACHINE.AuditDate
SET MACHINE.AuditDate = "01/09/2010"
WHERE MACHINE.OS_Name = "Microsoft Windows XP Professional"

Where would I run this SQL? Create it as a helpdesk rule?

The only way to run SQL against the KBOX database is in the form of a Custom Helpdesk Rule.

Thanks Airwolf

I've had a play with the Helpdesk SQL rules and experimented with a few simple, safe changes such as just changing the title of a ticket.

Does the Select Query have any bearing on the Update Query? i.e. can I use an irrelevant Select query (just because it needs something in that field), but then update, say, the knowledgebase table, is that possible?

....to clarify by Select Query I mean the field on the Helpdesk rules page, not a sql select query in general, but the box on the page it asks you to fill in.

You are correct. The select query and update query only interact with one another if you use the <TICKET_IDS> variable in the update query. You can simply put SELECT * FROM HD_TICKET in the select query and update an entirely different table if you'd like.