Search results for query: *

i would suggest; if you use ePO that is, to create a group with a deviating policy that has the 'prevent mcafee services from stopping' mark unchecked. place your machines in that group and rollout to those machines as scripted. so you can limit the impact but do all activities scripted.

why would you want to stop the McShield? i recon you chose to use this setting for a purpose.

I agree that ePO is a bit overkill but it is far more robust than a MirrorTask is. we used mirrortasks in the past (older versions of VSE that is) but they kept failing very often due to various minor issues on network connectivity and security.

have you checked the logs in %temp%/McAfeeLogs ? it is most usefull in these cases if the information as above is the only logging available it becomes somewhat vague.

is the user directly member of the local administrators group? this is the first thing i can come up with. otherwise re-download the patch and extract it. make sure you use a ZIP programm and don't use the WIndows extractor. i haven't used patch 3 yet so i have to test this when my test server...

Hi, you can setup an ePO server for your clients. use the Global Update option to update all clients when checking in a package (the engine/ Dat / SuperDAT file) you download from mcafee manually to update your clients instantly at checkin.

did you enable the other repositories in your ePOAgent policy configurations? this is required for the agents to enable the repositories and use them to update from.

Erdal, to deploy McAfee products you need to configure a Deployment Task in the directory. in this task you can configure what to install etc. regards, Bram

Perhaps you forgot to checkin the McAfee Agent 4.0 package itself into ePO (ZIP for ePO 4.0/.NAP for ePO server 3.6.x) what i find curious is that your McAfee agent is installed in a network associates directory; while McAfee is using McAfee as directory name for all its latest products

try Services.msc to view your running services and search for the McAfee Framework Service. or remove the Virusscanner completely and reinstall it. this will also trigger the framework service to be reinstalled

If you don't have too much policies to migrate and deviations to configure i would suggetst to install a clean 4.0 environment to ensure that you don't inherit any legacy faults and errors. please check the readme if an upgrade is even possible from 3.5 to 4.0 directly

check your McAfee Framework Service if it is running; i think it will not run. try reinstalling the CMA or ePO Agent.

please verify the version of your frameworkservice.exe.. is this really the 3.6.0.xxx version? only those display the M others the blue shield icon. Only option to get the M is install an agent of version 3.6.0.xxx and higher. at least as far as i was able to test.

I think one of the only options to do so is either using rogue system detection to install an agent to rogue machines that match the domain name or use a 3rd party tool to install the agent by eg. scripting or Microsoft SMS.

VSE 8.5i patch 4 is released some time ago, did this solve your problem? We never tested P3 but i have no problems so far with Patch4.

ePOAgent is part of the CMA (Common Framework) it controls the communication with the ePO Server (settings and task enforcement on your client) and the productupdates. So it is no new service or decreases systems performance. To me it seems that only an ePO Server can enforce the behaviour you...

Do you use ePO? ePO server will overwrite any client exclusions or settings. you can check if you run an ePO agent by starting running: "%programfilesdir%/mcafee/common framework/cmdagent.exe" /s Contact your ePO Administrator in that case to ensure that the required settings are set via ePO...

you can disable the M icon without problems, if you still enable the VSE icon they still see an icon for McAfee Virusscan. only the agent doesn't show. If you want to have the M Icon but no excamation mark you always can disable all checkboxes with report in the access protection policies. only...

The exclamation mark indicates that the accesprotection policies have blocked or logged a possible block. You should chekc the accessprotectionlog to see what program is being blocked or action is being logged as would be blocked.

If you mean a Virusscanner console password; If i'm correct you can remove the installation from the server by using Add/Remove Programms and reinstall a new Version with a known Password.