MSSQL clustered instance operational status set to Non-OperationalIssue Pre post script "Modify Operational Status for MSFT SQL Instance CI" checks if a MSSQL Instance is running on a Windows Cluster. If so, it looks for other MSSQL Instances. If other instances with the same name are found running on the same server it will set those instance's operational status to "Non-Operational".ReleaseParis and newer releases.CauseA common setup for clustered sql instances is active/passive. In such scenario one instance is operational and the other is on "stand by". This is expected behavior as seen in the code for pre post script "Modify Operational Status for MSFT SQL Instance CI". However, some instances are setup as "active/active" (always on). The script provides an option to control this behavior by setting the field "comments" on an instance to "always_on".ResolutionIf the instances facing this issue are indeed setup as "active/active" (always on): Open each of the MSSQL instances in the clusterUpdate field "comments" value to "always_on"Related LinksMSSQL server discovery