I have been asked by management to create a report on forefront definition versions in our environment. Whether this makes sense or not, doesn't really matter to those asking for it.

My hope is to have a script that runs against all systems (through a job in SCCM) with this forefront installed, that would query the reg key and then create a executable file based off of the key value, to a particular folder. SCCM inventories executables, so creating an exe with this info would be an easy way for me to run reports against the systems.

Can anyone help me out with creating a script for this? It doesn't seem like it should be too big of a deal, but most of the scripts I have found are just piping the information to a txt file that resides on a share. This would be possible, but I would have to parse through a lot of information when really I just want quick snapshots of what the version is in my environment.

HKLM\SOFTWARE\Microsoft\Microsoft Forefront\Client Security\1.0\AM\Signature Updates\AVSignatureVersion <-- is the key I need to query against.

Any help would be awesome!
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


can't you just run an sccm report based on the registry key?
we've modified the SCCM .MOF files to grab the registry keys for the SOE version and dump it into a table, which we then run a report from...
Scope this
Answered 03/21/2010 by: ditch_nz
Purple Belt

Please log in to comment
I think that there is a registration key problem....Ask your service provider to solve this....
Answered 05/05/2010 by: borrows123
Yellow Belt

Please log in to comment
Just a thought...

since you're using SCCM and I assume you can request status codes for your distributions on the machines, why not have your script/exe fail (yes fail) with an error code from which you can deduct the version?

like say version 1.0.0 fails with code 100, 1.0.1 fails as 101, etc etc

you could then report on exit codes

my 2c

Answered 05/05/2010 by: pjgeutjens
Red Belt

Please log in to comment