AUTOGROWTH settings in SCOM for SQL 2019 Management Pack

I had a request to configure the Auto growth for the databases used for SharePoint. As SharePoint use increases on day today bases, newly contents are added and accessed almost everyday, hence auto growth settings is important to make effective of the storage in the infrastructure.

In my example, I will be demonstrating how can we do the auto growth settings on a content DB of SharePoint.

As the Management Packs display the DB parameters view only in Monitoring view of the Management packs and not in the Health Explorer view of a server. 

Resolution:

Pre-requisites 

The team which needs auto growth threshold value settings needs to to share the maximum threshold value, kindly get the values of MDF & LDF with you.

Go to the DB Engine view on Monitoring workspace:

Select the server on which you want auto growth to be done, use Health Explorer of the server:

Now in the Database Performance view, select the required database need change auto growth threshold.

Create a override on LOG Free Space Left (LDF) & ROWS Data Free Space Left (MDF) with desired threshold values in Megabytes and that's it !, the auto growth values is configured.

Please note there are other ways of configuring auto growth, I found this way, and was successful.

I hope this topic will surely help somebody in SCOM Community.

 

 Sharepoint: Database Connection Failed alert

We all know Microsoft Sharepoint is a collaborative platform. We all use it today widely for storing and sharing the documents on the internet platform.

I recently migrated had Sharepoint: Database Connection Failed alerts in bulk, while I configured Sharepoint 2019 Management Pack and found out the resolution for these alerts.

The console looked as above for all the environments of Sharepoint 2019.

The description of each alert looked as below:

Alert Unit: SQL database connection failed 

Resolution:

If you go to the Microsoft SQL Management Pack folder on "Monitoring" workspace you will find this alert is already getting monitored, hence we can disable the above alerts as these are re-discovering from the Sharepoint 2019 Management Pack again.

Thought to discuss:

In the Management packs of 2019, I have found that the monitoring parameters that discovered for a SQL server for example, will no longer display under Health Explorer view but rather you can only see them in the Management Pack folder in "Monitoring" workflow of SCOM. The question still remains Why?

Somebody can comment with their valuable resolution for this thought.

This topic is to help the SCOM Community.

 UNABLE TO VALID OVERRIDES in SCOM

OVERRIDES

This feature of SCOM, is used to make changes on the existing Monitors and Rules which gets populated when the servers are added to the SCOM environment. This is the important of SCOM workflow "Authoring" where all troubleshooting / supressing / disable of alerts happen. For more information Please find the article from Microsoft here.

When we open it We will find all the different options of the feature, among which are :

The tick button on the left is used for enabling the Override values of different categories and the tick button on the right is to enforce any changes already applied to this Override.

This blog is for those who are seeking for a help if they are not able to see the above screen. I had the same issue when I upgraded my SCOM remote console from 2012 to 2019 version. I was not able to perform valid overrides, as below:

I was not able to edit the Override value column, After a lot of troubleshooting, I found the resolution for this issue, and here it is as below:

Resolution 1:

If you are using a Laptop:

The recommended resolution and scaling of display will be the problem, hence please change the laptop display settings to as below:

Scale & Layout:

125%

Display resolution ( you try with other resolution settings and check)

1920 x 1080 - (This has worked for me)

and rest all defaults

Reopen the SCOM console, you will now able to see valid override window as below:

Resolution 2:

In this method, its more of shelling out extra money to buy a "21" inch dual monitor so that the high resolution can be seen on the big monitor, as Laptop's are hardly 15 inch' and resolution as Applications wont scale up  automatically. 

Now you can decide, which one you would like to go for 1st Resolution or the 2nd Resolution.

This post is to encourage the SCOM Community.

Please comment if it has helped you!.

 

 SCOM Gateway server re installation steps 

As Gateway server in SCOM is a bridge server which allows the servers in DMZ(servers behind firewall zone) and servers which are part of an enterprise domain (workgroup) communicate and download Management Packs for the clients in DMZ / workgroup effectively get monitored in SCOM Tool.

Since the clients or servers which are in DMZ/workgroup servers, they need authentication of some sort communicate with the SCOM servers which are usually are deployed in a domain.

There are scenarios where you need to deploy the Gateway servers using different methods and security permissions.

Gateway with Agent-managed Workgroup Servers

In this implementation monitoring of a remote, untrusted AD domain is desired. Some servers desired for management by the Gateway Server are members of a workgroup. In this scenario, certificate authentication will be required not only between the management server and gateway server, but also between the Gateway Server and agent-managed computers. 

Requirement of this setup: Machines requiring certificates: Management Server, Gateway Server, agent-managed workgroup servers.

Please note: 1.Please create a new Gateway server to migrate all the existing agents. 2.And also ensure new Gateway server is communication with the Management you are connecting.3. Ensure that your new Gateway server has the CA or PK certificate installed with event id: 20053 received on that server.

         Steps to follow:

• You need to remove all the old gateway entries on the client machines in control Panel.
• Delete all agents appearing grey under old gateway server on Console.
• Goto Management server and run the Gateway Approval with "Delete" attribute for the old Gateway server.
• Run the Gateway Approval with the new Gateway Server name with attribute "Create".
• Goto new Gateway server uninstall the Gateway role, and reinstall with Management Server.
• Restart the Gateway Server and wait until it comes back
• You will see the turned Gateway Server turned healthy under Management Server on console
• All the client servers will be in Pending Management on Console.

Please note: This article is for those with less gateway clients and they can very efficiently do it without any hazzle.

I have written this article to contribute to the SCOM community.