exact same thing happened to us. we've been advised to roll back to 3.02 whilst the issue is worked on by nai. afraid I can't tell you any more than that...
Hope this helps: see page 3 of this Mcafee document. The document is McAfee's official line to business customers on XPSP2.
https://knowledgemap.nai.com/solution/mcafee/Documents/McAfee_FAQ_for_XP_SP2.pdf
I had a demo version - it suited our needs in every way & was a really good product. It kinda fills in the gaps in EPO reporting, including the ability to turn reports into browsable web pages - a feature which our security manager got particularly excited about.
We were going for it until I...
It's an extra ePO-controlled product called Systems Compliance Profiler. It's available for download if you have a valid grant number for any of the ePO type license packages.
that's why I do the full domain import then search & delete duplicates. It leaves you with all your rogue / failed agent installs, even if you've removed inactive / failed agents.
if you mean "can EPO manage clients through a firewall without all the Netbios ports being open?"
...then the answer is yes. You need the following ports open on your firewall to enable your client <-> EPO server communication:
80 81 8081
Please note that you will not be able to push install...
addus,
the global active agent task is found at the server level - in the console click on the EPO server (one level above "directory" in the tree) & it is found by creating a new task under the "scheduled tasks" tab.
hope this helps
RTC
I use the global inactive agents maintenance scheduled task - it runs every Sunday + moves all agents that haven't contacted the server in 6 weeks to a site I created called "inactive agents".
Then every Monday morning I fire an agent install at all the resulting machines that have appeared in...
1 - check that the credentials you use to push is a member of the local administrators group on every target machine
2 - check that port 80 is allowed from your target machine to your epo server
3 - if all else fails, install manually (or use another way of deploying - logon scripts, sms...
sorry, I went all butter fingered with that last paragraph; here's what it should say ;-)
BTW, I was in a meeting with NAI the other day. Apparently SCP 1.1 is on the horizon. Also, NAI are keen for administrators to submit wishlists stuff for future SCP releases to them. I mentioned that it...
ok, here goes: I have deployed SCP 1.0 to 25 pilot PCs & servers. The EPO deployment task was managed to deploy successfully on 60% of machines (there was no obvious rhyme or reason to this deployment success rate). I hit the remaining 40% by running the exe installer manually locally on those...
CD, they're not routing across the internet to get to your EPO server, are they? If they route internally across your WAN links & those WAN links have nothing blocking ports 80 or 81, then my next step would be removing/reinstalling the agent to see if that cures it. You could try a trace...
Hi CD
on the clients that won't communicate with the epo server, what error messages are coming up in the Agent Monitor? are ports 80 & 81 open between the problem clients & the server (ie, you're going over wan links with no firewalls / acls in the way, right?)
On our SQL servers, we disable 1) backup* (read/write) & 2) mssql* (read/write) from VS7 on-access scanning. This was based on feedback from our DBAs & cured any performance issues.
sorry - just re-read your post!!
you acually need to sign up for the nai dat update release list (http://vil.nai.com/vil/join-DAT-list.asp). NAI's policy is to release an emergency update if a new high level virus is discovered. The dat update email from them tells you about the threat...
you need to use McAfee Alert Manager - install it on one of your servers & configure the email notification option so that it notifies you about level 5 events (you'll also need an smtp server for this to work - also specified in the options). You then configure all your virusscan clients to...
I've just noticed that NAI have updated the beta pages for System Compliance Profiler:
Beta Program Schedule
Beta II - Current
Final Release - Mid February
So that's good news.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.