skissinger
Posts: 2119
Score: 134 Joined: 9/13/2001 From: Sherry Kissinger Status: offline
|
Attached is a snippet to add to the bottom of sms_def.mof on your server. When you do so, when you hit save, just monitor the log file dataldr.log on your server, to see if it was accepted or rejected. (Note, there will be an error, which you can ignore--it really just means "hey! you just edited the mof!) You'll know if it was rejected if the old version of the mof was automatically replaced. The attached snippet has 3 basic things it'll return: Regkeys from 7 or 8 Mcafee client, EPO 3.x regkeys, and there's a section which may or may not return any data in your environment; I haven't tested it yet myself but I 'think' it's for EPO 4.x stuff. Once you've added the snippet to the mof on the server, that triggers a policy update which is forwarded to your MPs, which you clients can then pick up at their next policy refresh. So, about 1-3 policy refreshes at a client, it will *try* to report up what you've asked. However, a SMS2003 client will not know "how" to report up the new data--you have to tell it how by 'mofcomp'ing' it on each client. There's several different articles from various people on how they've deployed a mofcomp to their clients; but for just testing a single client, interactively at a cmd prompt, just run mofcomp <nameofthesnippet>.mof . Then, at your next Hardware Inventory, assuming the client has picked up the new policy already from the MP, it'll report up the regkeys it has. Once you get that far, if you need assistance setting up an advertisement to send out to your clients to do the mofcomp, just reply.
Attachment (1)
_____________________________
mofmaster@smsexpert.com (version 2007) | http://www.smsexpert.com | http://www.sccmexpert.com My Blog Microsoft MVP - ConfigMgr
|