After you apply ePO 5.10 Update 5, the product version property for point products might not update correctly when the point product is upgraded. This issue is most commonly seen with the McAfee Agent version, but can also affect other point products.
An example sequence of events might be:
- Upgrade a McAfee Agent 5.5.1 client system successfully to McAfee Agent 5.6.2.
- The local About screen and all file version information correctly show McAfee Agent 5.6.2.
- The ePO console continues to report McAfee Agent 5.5.1.
This issue will be resolved with “Update 6” package.
This problem is intermittent. The next time the McAfee Agent submits its version information, it might update correctly. But, in normal agent-to-server communications, the agent does not resubmit its version information, because it has not changed since the last communication.
As a workaround, you can schedule a client task on the affected clients to run a wakeup call and submit their full properties:
- Log on to the ePO Console.
- In the Client Task Catalog, create a new McAfee Agent client task.
- For the client task type, select McAfee Agent Wakeup.
- Under the Options section, make sure that you select Send all properties defined by the agent policy.
- Assign this task to the affected system.
- Schedule the task to run at regular intervals.
Over time, the client systems will update their version information correctly. After the client systems update their version information, you can unassign this task from them.
· Save at list the last two backup.
1. Backup the database of ePO server:
a. Open “Microsoft SQL Server Management Studio”, log in with “SA” user or user with full control on the ePO database.
b. Expend <Server_name> -> expend databases.
c. Right-click ePO_<Server_Name>, select All Tasks, Backup Database.
d. In the Database field, select the ePO_<Server_Name> to be backed up.
e. In the Name field, type a name for the backup set (example: ePO Master Backup).
f. In the Description field, type a description of the backup (example: ePO Full Backup).
g. Under the Backup Type, select Database – Full.
how McAfee ePolicy Orchestrator System design and structure
McAfee Agent Option:
<Installation Path>\Common Framework\CmdAgent.exe
McAfee Agent 5.x C:\Program Files\McAfee\Agent>cmdagent.exe McAfee Agent 5.x
EXTRA.DAT files is release when there is new and could be critical to your environment, When new malware is discovered and extra detection is required to detect and prevent against the threat.
EXTRA.DAT files contain information that is used by VirusScan and other McAfee products to detect new malware.
McAfee ePolicy Orchestrator Change time zone for see task working normally time
One of the following parameters must be added to the registry under HKLM \ SOFTWARE \ Wow6432Node \ Apache Software Foundation \ Procrun 2.0 \ MCAFEETOMCATSRV250 \ Parameters \ Java \ Options. The problem is solved after entering one of the parameters.
-Duser.timezone = Asia / Kuwait
-Duser.timezone = Asia / Baghdad
-Duser.timezone = ” GMT + 3 ”
After the addition process, the following services need to be restarted by stopping with sirasin.
McAfee ePolicy Orchestrator Application Server
McAfee ePolicy Orchestrator Event Parser
McAfee ePolicy Orchestrator Server
If your Windows server is running on Eger servers, you can check the connection times on ePO and apply the corresponding solution.
You can see the screen display related to the parameter below.
This is site full with all kinds of information about Security Products (McAfee,Sophos,Avecto,Websence,proofpoint) Specially McAfee Endpoint Products
Installation, Procedures, Solution of problems, Tips and Guide
This information is for beginners and experts
All the information is from my own experience and from McAfee Intel Security
Explore and Enjoy