I have to second the ePO suggestion. I am guessing you are running enterprise mcafee? If you have a support contract, deploy ePO. I used Perl scripts to monitor my AV setup. However, I found that since we were paying for a licenses, why not use it since it comes with the package?

Some things to consider: 200 less WAN calls for updates to the DATs. Forced updates. Forced Scans. The biggest gift, you can keep your people from uninstalling or hamstringing the AV.

Now, if you don't have ePO access, you might consider the TieRegistry module. I found there were certain areas of the registry is where mcafee stores DAT info, etc.

Since you can access the registries remotely, I found that better then hoping shares and trying to open files.

I should try and find my old level report and see about posting it in the code libraries.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.