the sequence counter is used to determine if you have duplicate agent guid, most probable cause being imaging and incomplete/interrupted communications.
Ensure your 2 duplicate agent GUID server task are running periodically and that agent information is removed from images/vdi
You can search in the EPO server logs (C:\program files (x86)\mcafee\epolicy orchestrator\db\logs\ directory) to try and determine why it's showing the sequence error. The most common reason is as Andre stated, duplicate GUIDs. When the agents communicate for the first time, they're asssigned a sequence number of 1 and EPO stores the same number, 1. Over time at each communication to the server, the numbers sequence on both sides. Eventually if a machine is a snapshot that was rolled back to an earlier date or an image was made of a machine that already communicated to EPO, the sequence number expected by the server won't match, preventing communication. This explains why the last communication (successful) timestamp is older than the last sequence error timestamp.
The server log should show it's duplicated. If you search for the GUID assigned to the machine in the system details page of EPO in the log, you should be able to see what other machines share that GUID. Once you identify those machines affected, you can follow the steps outlined below to clear the GUID.
mariyappa, are these cloned/imaged systems? it sounds like systems were deployed with duplicate McAfee agent guid. it can be rectified in *many* ways.
- modify your sysprep to run framepkg.exe upon first boot. so you will need to copy the framepkg.exe file somewhere on the image and specify the path/command in sysprep
- find systems in do a new forced deployment. this can be manual or automated.
- manually installing agent as you deploy your desktops in your network.
- use group policy /batch file/powershell to install framepkg.exe