How can I check in the HIPS packets to my repository? I want to push the HIPS installtion with the Epo Agent. The upgrade from DFW 8.5 to HIPS 7 works, but i don't know how to install or upgrade my DFW 8.5 Clients witch Epo.
Confirm HIPS is NOT part of an existing deployment task
Configure your policies
Test by deploying to a few machines via local deployment task (disable inheritance on an individual node or group, then add HIPS as an Install item on the local deployment task)
If successfull... Add to your Global Deployment task
Monster Monster MONSTER Caveat of death in my case McAfee Document ID: 612704 - If you Run the Cisco VPN client make 100% sure you have not installed The Firewall component, if you have remove it first (oh the joy). Doesn't matter if it's On or not you must remove the DLLs and registry entries. This KB states it's an issue it's running, in our case it was an issue just being installed and teir 3 had us follow these steps (after BSD'ing multiple machines in the field)
McAfee and VPN do NOT play nice (we've had FW issues in the past that McAfee released SP's for)
McAfee Document ID: 614281 The following Virtual Private Network (VPN) clients have been tested and are currently supported with McAfee Host IPS 7.0:
Ensure all clients are running CMA 126.96.36.1994 (3.6 patch 3) before rolling out HIPS.
+++ mcAfee bullentin +++ McAfee Common Management Agent (CMA) 3.6 Patch 3 is available for download to licensed customers from McAfee ServicePortal: https://mysupport.mcafee.com/eservice_enu/default.htm It is highly recommended to install this patch to remediate of the below critical issue: ISSUE: The Common Management Agent corrupted the server.xml and/or compiled.xml files when it compiled policies. RESOLUTION: The Common Management Agent now locks the server.xml and compiled.xml files as a single unit. This greatly decreases the likelihood of the policy compilation process corrupting these files.