Thanks for responding to this thread. I was forgetting to post an update!
While I had a bit of a "heads up" that it was coming, my support ticket was officially closed on Sept. 18 with the resolution "Resolved in 6.2.1".
I am also currently at 126.96.36.1996 / 188.8.131.526, so I can't personally confirm that this is resolved.
Thanks for the update. Just checked the release notes and it has:
BZ776968—Machine is locked out after 45-60 days although policy is set to 90 days.
We will be upgrading to 6.2 Patch 1 in the new year - 2013.
Machine is locked out after 45-60 days although policy is set to 90 days.
Wow. That phrase is exactly what I typed into my original support ticket. Where's my royalties???!?!?
Since Monday, November 4 2013, we have been recieving far above normal calls to our helpdesk regarding this same issue. This system is locked because it has been too long since the last policy update. Coinsidently (or not) day light savings occured on Sunday, November 3 2013...there seems to be some issue here when OS system clocks are changed automatically. Has this been identified by McAfee support as a potential bug? We have platinum support and will be willing to open a case, however if there is already a solution in the wild I would like to know.
Typically we get calls in for folks who are 75%+ travel and do not connect to the LAN often or ever. While we do think there are major issues with EE and policy enforcement via VPN occuring automatically, this affected pool of users were both remote and local leading us to believe there is something else going on.
Endpoint Encryption for PC 184.108.40.2065
McAfee Agent 220.127.116.1122
VirusScan Enterprise 18.104.22.1685.Wrk
Endpoint Encryption Agent 22.214.171.1245
I spent the past couple days checking with our Helpdesk and with end users directly, but no one is reporting any issues.
I recommend opening the support ticket.
We haven't experienced this problem again since upgrading to 6.2.1. (We're currently at 7.1.3.) So, I'm assuming they did indeed fix the bug and the "solution" is to upgrade.
In this thread, Mantis was the only one who reported this issue in a version higher than 6.2.1 (his reply stated 126.96.36.1995) so hopefully he is still around and may be able to provide some insight if you're running 6.2.1 or greater. If you're NOT running 6.2.1 or greater, I'd suggest upgrading to resolve the issue.
Well I'm on 7.1.3 and we've been experiencing the issue on a couple of systems regularly. Seems the only way to "get around" it is to disable pre-boot authentication. Doesn't matter how long the system stays attached (usually would be all day) and doesn't appear to matter what we set the timeout to be. And since we've now been migrating users from the old ePO server onto the new one we have to be extra careful that we don't completely lock anyone out.
Thanks for the information. We've still not experienced this issue since upgrading to 7.1.3 so I'm not going to be of much assistance. Have you opened a Support ticket? If so, I'd be interested in what they have to say about it.
Feel free to use this thread for any updates you may have for this issue.