This content has been marked as final. Show 12 replies
Are you talking about the Daily DAT updates ? :confused:
I don't even understand the pb grin I'm useless grin
No, not dat updates. I am talking about updates to ePO itself. For instance they pushed an update from v3.6 to 4.0 then from 4.0 to 188.8.131.525 and the latest from 184.108.40.2065 to 220.127.116.112
Each time it pushes an installer called mfeagent.msi to the common framework directory and tries to run from there, but cant. So every time there is an update the whole organization gets an error message saying MFEagent.msi cannot run, until I go run it manually. And each time I run it manually it changes the permissions on the Common Framework directory back to Everyone with Read Only.....
Does that make more sense?
It is the same exact problem seen here, but there is no permanent fix listed
If you use firefox and scroll all the way to the bottom, you can see the answers.
I checked the permissions on our McAfee repository and all looks fine....
Also, thought I would mention it runs fine when logged into an admin account
FYI, we still have this issue if any one can help it would be greatly appreciated.
I found if I image a machine from the ground up and leave default windows permissions the error does not occur. We use the following permissions on our standard image
Admin - Full
Authenticated Users - Modify
System - Full
I dont understand how this could be causing these errors.
Have you tried a manual push from the ePO console and using the domain admin credentials? Or try creating a new framepkg.exe, the update services should be running with a local system account with admin rights.
hope this helps
Thanks for the post Schoeys. Unfortunately the ePO admin is not in the same city as we are. We are currently in the process of splitting off onto our own network, but that will be at least another 6mos-1yr.
In the mean time I have been in contact with the ePO admin and he has tried a manual push with no success. According it him the update services are running under Domain Admin group which is present on all our machines as an admin group, but again I am unable to verify this...I am only taking his word.
Thanks again for your assistance. There is another person with the exact same issue about five/six threads down.
Sorry couldn't help more, but did have a thought, as it works under and admin acccount, is the issue a conflict between a GPO and virusScan console stopping the msi from running? You have the problem though of not having access to the logs on the ePO server which might be of more help to you.
Strange about permissions, we're citrix so the PC's don't sit on the domain and the msi's run fine when pushed out.