I am working on project to create “bread crumbs” that will contain information about which fixlets have run on the clients. I wrote a small app (compiled AutoIt script) to create the registry entries using passed parameters. What I am looking for is a way to pull the information from the “Properties” page such as:
fixlet name
source
source id
description
date/time run started
date/time run completed
etc.
At the end of each action script, I want to pass this information to the breadcrumb application to create the registry entry. This would become the standard for all custom fixlets/tasks within our organization.
When I am authoring a fixlet or task from the BF console, I have 4 tabs - Description, Actions, Relevance, and Properties. On the Properties page, there are several fields that we can use to store data specific to the particular fixlet or task. For example, we include a ticket reference number that corresponds to a help desk ticket so that we can maintain a linkage with the help desk details of the problem/situation that lead to the development of the fixlet/task.
My expectation is that this bread crumb script will become the standard “footer” for all custom actions that we run. I know that we can always just look in console for the fixlet/task and then filter for a specific computer. But, we are interested in having this information immediately available on the client without the need to go to the BF console.
So if I understand you properly, you want to have each action write out the action info to the agent’s registry during each action (so the agent will have record of all actions)?
That is correct. I have created a small executable that accepts a predefined set of command-line parameters (action name, action version, source, etc.) and populates the registry with these params.