This can be done via manually deleting the records in the database. Mainly there are 3 tables related to this. Maybe more, so far I got three. The main record is in table PROV_HISTORY_TASK. And the other two tables refer to the PROV_HISTORY_TASK_IDN column in it as a foreign key.
So you can delete via SQL statements or via the GUI tool to delete the records. If it prompts other constraints then other tables might be involved. Just delete all the things related to delete the main record finally.
Hope this help.
Isn't there some easier way to clear the provisioning history? I would rather not touch the DB.
Thanks in advance!
Our in-house provisioning expert, Tracy Hammond, has the answer.
"The provisioning history is stored in the LD database. The easiest way to clear it it to just delete the machine from inventory, then delete HKLM\software\intel\landesk\commonAPI and HKLM\Software LANDesk\CommonAPI
This will give it a new DeviceID in LD with no history associated with it."
This method works well for lab/testing machines that get provisioned over and over, but not recommended for actual production machines as you will lose any other history the machine has as well. Also it will break your Management Gateway... er excuse me, Cloud Services Appliance certificate as well.
This is what we use. We have some history that needs to be cleaned out over time usually involving "Waiting" or "Running" states which is 1 and 2. There are others that you could do as well.
Delete from prov_history_variable where prov_history_task_idn in (Select prov_history_task_idn from prov_history_task where (history_task_state = 1 or history_task_state = 2) AND Device_Name = "$deviceName" Delete from prov_history_entry where prov_history_task_idn in (Select prov_history_task_idn from prov_history_task where (history_task_state = 1 or history_task_state = 2) AND Device_Name = "$deviceName" Delete from PROV_HISTORY_TASK where (history_task_state = 1 or history_task_state = 2) AND Device_Name = "$deviceName"
**Note (Disclaimer) ***
This is deleting from your LD database so be careful
I just tried this on a "lab" machine on LDMS 9.6 SP2 and it did not clear the provisioning history. Was this loophole closed?
I take that back. Deleted the system from LANDESK and rebooted; now the system has a new unique ID and the provisioning history has been reset.