SQL MP wrongly specifies Service Pack Level
SQL MP wrongly discovers Service Pack Level attribute which shows 0 but the SQL 2016 is already installed as 13.1 which is SP1 version. Please correct.
Pascal Wechsler commented
Although this is not directly an issue with the SQL MP itself, quering this particular reg key causes the wrong SP level in SCOM. I would rather prefer to query @@VERSION within such a discovery
I just checked it, the SQL SP2 corrects this issue and the SCOM discovery discovers the Service Pack Version correctly, now (SP1 still affected).
That is an issue during the SQL SP installation where the regvalue will not be set correctly. SCOM discovery works as expected. SQL Team addressed that this should/would be fixed with SQL SP2 (do not have the link right know) but could not check if this is true.
Therefore I think it is not a SCOM “issue”.