1 of 1 people found this helpful
Are you using Intel vPro/AMT? In our case we had LANDesk look into it and they determined its a Microsoft issue with SSL/TLS.
I have never seen any ill effect from these errors.
Yes we are using vPro/AMT. Was the solution to ignore the errors? or did you guys actually do anything?
Its flooding our logs making it difficult to retain relevant event log data at the very least.
Basically ignore them is what I was told. You could change vPro to not use TLS but that would sacrifice security. Appears this is accross the board with other software and functions that use SSL/TLS. I was told it is a pending issue with Microsoft awaiting for a fix.
Btw, I have seen these errors for a few years and nothing bad has come of them. Only issue is they get pretty annoying when your log is full of them.