Looking at ours, these dates are very inconsistent. I looked at 15-20 computers and the Agent Configuration Date seems to "match" (or be closer to) the Record Creation Date then any other field.
Thanks for checking your install.
Weirdly most of the machines report an updated date of yesterday, despite the agent being both modified and re-pushed today and some of the machines report a date closer to the initial rollout, even if i single target them with an agent update.
Perhaps counter-intuative, but that value is indeed the date the agent was installed. It usually very similar to Record Creation Date because 9/10 times, the agent will submit its first inventory scan during the installation process.
There is currently no easy way to tell if your agent configurations are-to-date. There have been several discussions on this matter, and there are several open Enhancement Requests in relation to this. I'll try and look a few up and link to them in my next reply.
In the meantime, one option is to include a version number in the name of the agent configuration. It has its drawbacks, but works in the most part.
Ok, some related ERs:
- Agent Revision on device in inventory (This is a request to get the agent configuration revision number reported in the inventory - this would make what you're trying to do much easier)
- Agent configuration to work like scan and repair settings (Less related, but a very good idea nonetheless - the basic idea being for agents to automatically syncronise changes to agent configurations)
Thanks for those Richard. I'll go with version number in the Agents name I think. The only other option i could think of was to set a custom registry variable by way of a scheduled task but it seems like more hassle than its worth.
Hopefully Landesk look at the ER's.
They look at some, at least, but there are a lot of ERs
On the version number front, we go for a <major>.<minor> approach where the following conventions applies (which I think I may have stolen from ZMan, so credit to him):
- A simple change to the configuration which only requires a "Schedule update to agent settings" task increments the minor version number
- A significant change (such as adding or removing a component, or applying agent patches) which requires a full agent redeploy increments the major version number