Thing is that SCOM uses SHA-1 itself for monitoring UX based workloads!
SHA-2 to the rescue?
Gladly, UR#12 for SCOM 2012 R2 and UR#2 for SCOM 2016 fixes this issue by replacing SHA-1 by SHA256, member of the SHA-2 family.
What to do?
Simple! Whenever running SCOM 2012 R2 and/or SCOM 2016 AND monitoring UX based workloads, roll out the respective UR and follow this article on the SCOM Team Blog about how to replace the SHA-1 certificates with the SHA256 certificates.
Do I need to?
Well, it depends. When you like flipping burgers as a next career move, then don’t. When you like your current career, then do it ASAP…