![]() What does McAfee recommend we do in order to resolve this problem? Is it possible for me to use ENS Package Designer and exclude the McAfee agent from that build? (Additionally a ticket has been opened and MER uploaded: SR # 4-22496227641) This is an extremely inconvenient development that McAfee has created by packaging the McAfee agent with ENS. Although the status of the agent says "unmanaged" we are unable to uninstall the agent from the Control Panel or using the manual command frminst /remove=agent. When the desktop admin tried to install our McAfee agent that we created from our own EPO server he got an error message that said the system already has the same version of the agent installed, and he was unable to install our custom made agent from our EPO server. So when the desktop team ran the initial "Update Security" option on a freshly imaged system that pre-packaged McAfee agent didn't look for our EPO server to update the policies, tasks, and various other updates. ![]() They used that ENS package to update their MDT images with the September release of ENS which also installed the pre-packaged McAfee agent, and the problem is that agent doesn’t have any reference to our on-premise EPO server. I used Endpoint Security Package Designer to create a new ENS package for my desktop team. I discovered today that McAfee has started packaging the McAfee agent with the recent releases of ENS.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |