You setup a snapshot job to run against the servers you want to monitor using the template. Schedule this snapshot to run daily, weekly, whatever.
After the job runs two times, you’ll see a ‘change tracking’ tab in the job run result that shows the changes between runs. This data is also available in bdssa.
the idea is to see the changes.
If you want to act on them you can do an audit of two snapshots and do a ‘sync to master’ to remediate to the previous state of whatever you are monitoring.
This seems like a good place to post - and although this was answered - it was not marked as "answer" - so..
when setting up FIM, especially on a large asset list, what is the best way to control snapshots and files that take up server space because it needs to keep old/new for being able to run the diffs? Seems to me that disk space on a primary provisioning server could become an issue. I don't see any "best practices" on setting this up..
What do you mean by “primary provisioning server” ?
If you are running db cleanup and only retaining the past X amount of snapshot data, everything should take care of itself for the most part I think.
the fileserver... But you just answered the question - we discovered that "cleanup" procedures are not being run regularly.. lots of old data.
One area I think BMC could improve is the documentation on using the tool as a primary FIM solution. It has the capabilities, but documentation directed at FIM seems to be lacking.
What areas are deficient?
Fim is basically creating a template w/ objects and running a snapshot job using that template against your servers on a scheduled basis.