Recent content by jeffatemc

Fabio, You can create a query using a pie chart, for example, and configure the 'Configure Criteria' where 'Product Version' = 7.0 and 7.1 or you may want to have it be more specific. You may want to have 'Product Version' >=7 AND < 8. You will want to play with that so that you are getting...

Dream, I have noticed that some units may not report but are updating ok as well, though not 20% of them having a problem - far, far less. From your posts I cannot see where anything has been left out and the fact that 80% seem fine leans that way. Is there something unique about the units wit...

The non-compliance issue could be one of many things, perhaps as simple as an agent version slightly older, etc. It just depends on the filtering in place that defines 'non-compliance'. You would need to review that policy and determine if the non-compliance is an actual issue for you. You will...

Dream, Not sure if this will get you started but from the ePO management web page, go to 'Systems', then manually add one or more systems via 'New Systems', pushing out the agent that way. Hope this helps!

Take a look at this previous post: http://www.tek-tips.com/viewthread.cfm?qid=1452563 Regards, Jeff

Perhaps this is not possible but, can someone call the former employee and ask him what the userid/psw is? Would certainly be a time saver. I've heard of this kind of thing happening and, unless the former employee left on bad terms, would probably be quickest. And, being Captain Obvious here...

Mike, Thanks for the explanation of how you use RSD in your environment. This is something we may revisit as an additional tool of discovery. Have a star!

We use a simple domain logon script that checks for the presence of a marker file. If that marker file is not there, the agent is installed, allowing for further monitoring, installs, etc. While this is not 100% accurate, it does get most new PCs. Additionally, we periodically review our...

Not using 4.0 yet but on 3.6 that should be under Policies->ePO Agent x.x.x.->Configuration (policy name)->General Tab->Policy Enforcemetn Interval. Hope that helps.

Sorry you have that type of roadblock - that's never a pleasant thing. There may be hacks to get around this (though I've not heard of any) but somehow, someway, on-access is going to have be turned off OR your project will get done in, say, oh about 10 years. Good luck!

It is likely that your 'security nazi' also has ePO configured to not allow for the modification of associated files and settings as well as preventing the termination of any process associated with McAfee. (This is an out-of-the-box setting AFAIK). So this would likely prevent a script to shut...

No, I would leave those checked. So there is nothing in any event log or McAfee's logs to indicate an error, it just does not back up the system state? Is the backup successful on other W2K3 boxes? Just trying to narrow this down.

Jay, Try this: Under 'On-Access Low-Risk Processes Policy' add BPCD.EXE and BPTM.EXE. We did this on the advise of Veritas. Hope this helps. Jeff

I have had this happen several times (usually after a reboot) and I have been able to resolve that by stopping and starting ePO's services. Good luck!

Plank brings up valid and correct points but allow me to bring up another scenario: You have a folder that,due to extremely high traffic (not uncommon), on-access has been turned off via policy to enhance performance. An infected file is copied to this folder but this virus is not yet in the...