OpManager 8 startup issues due to McAfee Virus scan
Hi All,
If you are have OpManager 8 with McAfee running on the same server, then you will face some issues with starting OpManager, because McAfee doesn't allow MySQL to start. A simple way to fix would be to disable McAfee during startup and once OpManager starts, you can enable McAfee and exclude the OpManager folder from scanning. If you do not wish to disable McAfee, follow the steps posted by Brian Lanktree (blanktree) which will help you fix it. Thanks Brian for those steps and here is the copy of his post.
I found the solution in Mcafee. In my case I was using the EPO but here are the instructions for both. The key was to split out my Policies in order to use a High Risk and a low Risk policy. Inside the low risk policy put in all of the mysql execs found in the bin folder. I then defined in that policy to exclude the C:\Program Files\AdventNet\ME\OpManager\mysql\bin\* path.
Finally got everything working as it should..
Very Happy Smile Laughing
-------------------------------------- > 8 -------------------------------------
Solution 1
Exclusions can be set locally (if the software is installed as a standalone) or through the appropriate management program (ePolicy Orchestrator or Protection Pilot).
Creating Low-Risk Process exclusions in the VirusScan Console (Standalone installations)
Open the VirusScan Console.
For VirusScan 8.5i and later, click Start, Programs,Mcafee, VirusScan Console.
For VirusScan 8.0i, click Start, Programs, Network Associates, VirusScan Console.
Right-click On-Access Scanner and select Properties.
Select All Processes, then enable the option Use different settings for high-risk and low-risk processes.
NOTE: If All Processes is not available, but you can choose from Default Processes, Low-Risk Processes, High-Risk Processes, this option has already been enabled.
Select Low-Risk Processes.
On the Processes tab, click Add and use the list or browse to the application you wish to include as a Low-Risk Process.
In the Detection tab, deselect any or all of the options in the Scan Files section.
NOTE: It is generally sufficient to disable When reading from disk. However, database servers also perform many write operations. In some environments it may be necessary to disable the When writing to disk option as well.
Solution 2
If VirusScan Enterprise is managed by ePolicy Orchestrator, you must modify the existing policies or create new ones.
IMPORTANT: When creating new policies or changing existing policies, use the drop-down menu to select Workstation or Server. Any policy changes must be made separately for servers and workstations.
Creating Low-Risk Process exclusions in ePolicy Orchestrator (ePO) 3.6.x
Log on to the ePO console.
Use the Directory to select the node or container for the new policy.
Click the Policies tab on the right.
Expand the appropriate version of VirusScan Enterprise.
Click the Policy Name for On-Access Default Processes Policies.
NOTE: If you are using the McAfee Default policy, you must first create a new named policy.
Deselect Inherit.
Select Use different settings for high-risk and low-risk processes, click Apply then Close.
Click the Policy Name for On-Access Low-Risk Processes Policies.
In the Processes tab, click Add, then type the file name (example: BACKUP.EXE) for the process you wish to include as a Low-Risk Process.
In the Detection tab, deselect any or all of the options in the Scan Files section.
NOTE: It is generally sufficient to disable When reading from disk. However, database servers also perform many write operations. In some environments it may be necessary to disable the When writing to disk option as well.
Click Apply then Close.
If you still face any issues, get in touch with us at support@opmanager.com
Pravin
New to ADSelfService Plus?