Just had a shipment of these Getac's V110 G4's come in. EPO is putting ENS 10.7 on it and the current McAfee Agent is 5.6.5.195
We are using Windows 10 v.1809
Every other device that has come in is encrypting fine but these 4. They've always been a problem.
I've been through looking for 3rd party DLL's or other processes that could cause it. Nothing has been found.
Is anyone else having issues with these Getacs? It installs and has us reboot but always comes up as inactive. Or other suggestions.
I've tried restarted services, checked MFEPE logs and no errors related to it.
Solved! Go to Solution.
Service Desk has tried for over a week with them and they aren't activating. I'll accept the resolution as these are not compatible with McAfee products. Wouldn't recommend buying. Good luck to anyone else who has bought these.
Edited on 7/16/2020: Oh how quickly the solution of the customer giving up gets such a quick response to resolve. After relaxing and coming back from the long dirt road of not finding anything from help from McAfee / Windows and Getac, we found out it was from the chassis type and it conflicts with EPO. Even with the policy set correctly it was pulling in multiple. Getac is aware of it.
The tag to disable encryption activity was applied with the policy to enable encryption. "Deny" always wins. Whether it's epO policies, NTFS permissions etc.. It took in a tag it shouldn't have and was randomly applying it. MFEPE logs will show that there's an error:
EEADMIN_1000_AddDomainUsersRsp: Unexpected IPC error.
Anyways, that's the solution.
Hi @ChristopherTB ,
Thank you for writing in here.
Can you try to paste the MfeEpe.log from the message "Start of Policy Enforcement" till the message "End of Policy Enforcement"
Thank you.
This is an extract from the current MFEPE log.
2020-07-08 14:03:44,233 INFO EpoState == Start of policy enforcement ==
2020-07-08 14:03:44,233 INFO StatusService Policy enforcement has started
2020-07-08 14:03:44,233 INFO EpoPlugin enforceUserPolicy: Dispatching enforce policy event.
2020-07-08 14:03:44,233 INFO EpoPlugin policyHandler: handling EnforcePolicy event
2020-07-08 14:03:44,233 INFO EpoPlugin policyHandler: skipping enforcement (machine is already compliant)
2020-07-08 14:03:44,233 INFO EpoState == End of policy enforcement ==
Hi @ChristopherTB ,
Thank you.
It Doesn't show any errors, may be you can open a support case where Support can remote in and check why MDE is still inactive on this machine.
Thank you.
Service Desk has tried for over a week with them and they aren't activating. I'll accept the resolution as these are not compatible with McAfee products. Wouldn't recommend buying. Good luck to anyone else who has bought these.
Edited on 7/16/2020: Oh how quickly the solution of the customer giving up gets such a quick response to resolve. After relaxing and coming back from the long dirt road of not finding anything from help from McAfee / Windows and Getac, we found out it was from the chassis type and it conflicts with EPO. Even with the policy set correctly it was pulling in multiple. Getac is aware of it.
The tag to disable encryption activity was applied with the policy to enable encryption. "Deny" always wins. Whether it's epO policies, NTFS permissions etc.. It took in a tag it shouldn't have and was randomly applying it. MFEPE logs will show that there's an error:
EEADMIN_1000_AddDomainUsersRsp: Unexpected IPC error.
Anyways, that's the solution.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: