4 comments

Add a comment…

Sign in

prestine

Your name

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Pascal Wechsler commented  ·  May 08, 2018 01:36  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  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

  https://msdn.microsoft.com/de-de/library/ms177512(v=sql.120).aspx

• Konstantin commented  ·  May 04, 2018 00:20  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  I just checked it, the SQL SP2 corrects this issue and the SCOM discovery discovers the Service Pack Version correctly, now (SP1 still affected).

• Konstantin commented  ·  May 03, 2018 13:34  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  https://social.technet.microsoft.com/Forums/windows/en-US/cf04ec56-737d-4998-973d-fe8493a19c29/sql-2016-mp-service-pack-compliance?forum=operationsmanagermgmtpacks

  Here we go:
  https://blogs.technet.microsoft.com/philipvandevyver/2018/01/05/sql-server-2016-management-pack-service-pack-compliance-sp1/

• Konstantin commented  ·  May 03, 2018 13:31  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  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”.
  Regards
  Konstantin