Suddenly all clients are displaying this in the monitor window:
also i cannot run any client tasks and they all fail.
what should i check to get this sorted?
ePO 5.9, Agent 188.8.131.528
thanks for any help
I saw the same thing. It went away when I re-installed the agent with /install=agent /forceinstall switches. I hope we don't have to do that across our 140k+ devices.
Our event parser service is running, and we've rebooted ePO twice this week.
Couple of Suggestions:
1) Check DB for size/server space or restart SQL services
2) Check sitelist.xml for correct IP/DNS name
3) Check Agent GUID Sequence Error Count
4) Check for Duplicate GUIDs
I have done all that.
So im getting those error messages with my agents.
I'm also seeing lots and lots and lots of these in my event log:
A fatal error occurred when attempting to access the SSL client credential private key. The error code returned from the cryptographic module is 0x8009030D. The internal error state is 10003.
If I deploy an agent, the task screen shows and the little progress bar is greyed out. Says it fails, when sometimes it does install.
EPO Version 5.9
Windows 2012 R2
Has there been any resolution to this? It started for me last week when I upgraded ePO from 5.02 to 5.33. I did all the pre-install audit fixes but now packages of unknown origin are failing to upload, and my Running Client Task Status never goes green.
Thank you Moe, performing the cipher reorder seems to have done the trick. I had to do that for my SQL server prior top upgrading to 5.33, but missed it for my ePO server. No more failed package alerts and the tasks in the Runtime Client Task Status goes to green and completes.
Hi, I am now experiencing this issue after upgrading from epo5.3.2 to epo 5.9.1. Our cipher suite was set to "not configured". which means it takes the default. I enabled the setting and tried to reorder the suite but it only take 1023 characters. Did you only add the cipher suite entried McAfee mentioned in the KB or all of them? Please let me know. This is urgent matter. I have a case open with McAfee but they have yet to tell me how to rectify the issue.