We run a provisioning schedule against a subnet to install an agent on all devices on that network.  The provisioning results simply show failed unknown error if the Kace agent is already installed.  I would think it would be an easy task for someone with SQL knowledge to correlate the provision results with the existing inventory using IP address for a report that indicates which failures should be looked into further.

I have looked at it and come to the conclusion that I do not have the expertise to accomplish the necessary joins.


0 Comments   [ + ] Show Comments


Please log in to comment



I created a custom inventory that reads the install date of the kace client and created a report from that.  I  know when I started provisioning and any clients older then that date did not get the provision.

RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5067EC6E-3349-42E1-8C4B-7195CD11C8AB}, InstallDate, date)

my report looks like:

Answered 05/29/2014 by: SMal.tmcc
Red Belt

  • Just updated to v 6 and now I created a new inventory item for it.
    RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DA9986AF-E65B-498D-A8D7-7247980F6C2E}, InstallDate, date)

    Now in my reports Systems that are null for this custom software item have not been provisioned to 6.0 yet. And I have a second report to show who got provisioned on what day by showing everyone that is not null.
    • That's an interesting approach I wouldn't have thought about. How do you corelate discovered devices to devices already in inventory?
      • see new ans for screen shot, this should give you that info.
Please log in to comment

Add the created field to the report and it will show when the machine was added to kace.  So in the report you will see all the machines have been in kace for a while.

Answered 06/03/2014 by: SMal.tmcc
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity