locked
SCOM 2019 - SQL MP - Service Principal Name Configuration Status Monitor. RRS feed

  • Question

  • Hi,

    One of the Monitors within the SQL MPs is the "Service Principal Name Configuration Status". This Monitor checks whether the SPNs are actually created inorder for the SQL to communicate through Kerberos and not NTLM. The problem is that the Monitor is getting the Instance Name and the Ports used from the registry and concatenates them. 

    Serviceclass "/" FQDN [":" Ports]

    In instances where the SQL is using one port the Monitor works fine, however when having multiple ports the monitor triggers false alarms since SPNs for multiple ports are not created in one single entry (the way SCOM is searching for) but separate for each port.

    Any one encountered the same issue ?


    Monday, June 8, 2020 10:00 AM