since I couldn't find any information regarding this problem - maybe someone has a hint for me:
We recently updated DLP 10.x to 11.x.
Now, one agent shows: "HDLP Service status: Disconnected".
As allways: It worked before (realy!)
What does this mean? How to troubleshoot?
Operating System is Windows 10 64 pro - 1703
Well, thank you for your feedback.
I opened up a case at McAfee one week ago. Case is still in investigation.
- When Chrome Browser is started, two chrome.exe processes are in memory, but chrome is not visible. One of these processes has to be killed, to run chrome.
- We had this issue till DLP 10.0.200.16
- Only DLP 10.0.223POC resolved the issue on *all* computers
- Now with the new DLP, we have the same issue again
Also, all DLP versions before 10.0.223POC could not handle iDevices properly - or let's say: They could not be handled/blocked.
10.0.223POC worked fine, 11.x isn't usable for now.
Hopefully McAfee may fix this fast. This is a desaster in large environments.
When Chrome Browser is started, two chrome.exe processes are in memory, but chrome is not visible. One of these processes has to be killed, to run chrome.
For this one, did you try import the xml file of chromesupportedversion? And sometimes press the refresh button in the DLPDiag tool, it will try to get the process list correct.
thank you for your reply. We use device-control - not the whole DLP-Suite.
In the past, I searched for the possibility, to import the Chrome Supported Version.xml file,
but did not find the corresponding configuration in ePO - maybe it's only available in the "full" DLP version or
am I missing something?
If you are only use device control, then no need import the mention file, cause the option list on DLP Windows Client Configuration, you are correct.
Thank you for your reply.
It is, like I assumed - this option (a lot of the options in your screenshot) are not available, if you just use device-control.
Best regards, Daniel
Hey Parachute, I have the same issue. Did you fixed it? The DLP clients not update the policy too, just when I restart the machine. Even though update the policy the actions presents some issues like block a device without show the message or report a incident.
Even I'm facing this issue with DLP 22.214.171.1242, issues encountered are as below:
Have opened a ticket with McAfee support with all the MER files and DLP diagnostic trace files.
This is really bad move from McAfee team.