Thursday, March 28, 2019

[SCOM] How to Re-Install Reporting Server for SCOM


Hi! Last time, my customer contact me and raised the issue regarding their SCOM  Reporting server. They told me their SCOM not producing report. Before re-install, make sure backup SCOM MP that contain the custom reports. Let start the configurations!

Step 1: Uninstall SCOM Reporting Server Features

1.  Open Control Panel and click on Programs and Features

2.  Click on the System Center 2012 R2 Operations Manager to uninstall the features



3.  Click on the Remove a feature



4. Tick on the Reporting Server and click Uninstall



5. Once complete click Close



Step 2: Delete ReportServer Database from Microsoft SQL Server Management Studio

1. Right click on the ReportServer&SCOM2012R2TempDB and delete the database

* Make sure to tick;
    • Delete backup and restore history information for databases
    • Close existing connections


2. Open Program and Features, double click on the Microsoft SQL Server 2012 (64-bit)



3.  Select instance for the Reporting and click Next



4.  Tick on the Reporting Services – Native and click Next



5. Click Next



6. Click Remove




7. Click Close




Step 3: Install Reporting Server for SCOM

1. Open Program and Features, double click on the Microsoft SQL Server 2012 Setup (English)

2. If you see Status Failed, then you need to solved which rule getting error. For me, I just need to restart the server once.

3. On the installation type, choose instance that you want to install Reporting Services and click Next



4.  Select on Reporting Services – Native and click Next



5. Click Next



6.  Click Next



7. Enter account name and password for SQL Server Reporting Services and click Next



8. Select Install only and click Next



9. Click Next



10. Click Install

11. Once installation completed, click Close




Step 4: SCOM Reporting Services Installation

1. Open System Center Operation Manager Installer and click Install



2. Click Add a feature



3. Select Reporting Server and click Next

4. Click Next



5. Select Server Instance and click Next



6. Enter Data Reader account and click Next



7. Click Next



8. Click Next



9. Verify and click Install



10. Click Close

Wednesday, March 27, 2019

[SCOM] How to Override Time Accuracy Out of Range Alert


Hi All, today I have a time to update my blog after left for few months. Today I will share how to override “Time Accuracy Out of Range Alert” from Microsoft Windows Server 2016 and 1709+ Operating System Management Pack.

Below is a screenshot from the “Time Accuracy Out of Range Alert”.




Step 1: Search the “Time Accuracy Out of Range” Monitors


1. Login to SCOM console and click on Authoring

2. Expand Management Pack Objects and click on Monitors

3. Click on Monitors



4. Search “Time Accuracy Out of Range” Monitors on Windows Server 2016 and 1709+ Operating System MP




Step 2: Configure “Time Accuracy Out of Range” Monitors

1.  Right-Click on monitor and go to Overrides > Override the Monitor > For all object of class




2.  Follow the below picture to override the monitor.

Interval Seconds: Change Override Value to 1000000. 1000000 micro second equivalent to 1 second





Configuration completed. Please clean the old alert and verify the configuration. If there is no alert regarding “Time  Accuracy Out of Range”, then the configuration is successful. You may contact me there is a questions regarding this!
Sunday, July 15, 2018

[SCOM] How to Override Existing Rules


From the existing post on [SCOM] Create Monitor Based on Event Viewer Log, we can see this request  to monitor few custom applications wherein they wanted to monitor Event IDs. As per configuration on [SCOM] Create Monitor Based on Event Viewer Log, SCOM will monitor all the servers. So in this post, I will show how to override the rules and monitor just one particular server. Below shows the steps;

Step 1: Open SCOM Management Console and go to Authoring tab

Step 2: On Authoring, go to Rules and search rules name. E.g. Event Viewer Monitoring

clip_image001

Step 3: Right click on Event Viewer Monitoring rules, and choose Overriders > Override the Rule > For a specific object of class: Windows Computer

clip_image001[5]
Step 4: Choose the object you want to override and click OK. E.g. ICG-AP-SQL01.INFRONTAPAC.local

clip_image001[7]
Step 5: On Override Properties, click on Override as below;

clip_image001[9]
clip_image001[11]
Step 6: Click Apply and OK.

Configuration for Override Rules completed. If you have any issue on this, please email to me. I will help you as soon as possible. Thanks!
Saturday, July 14, 2018

[POWERSHELL] How to Simulate Error on Event Viewer Logs


Hye all, today I will share with you guys how to simulate error on Event Logs. If you works in an Enterprise level, you most likely have some type of central monitoring system that collect errors from your event logs such as System Center Operation Manager.

To begin this, let’s open Windows PowerShell console and see what cmdlets are available that deal with the event logs;

Step 1:  Open the Windows PowerShell console and type “get-command –Name *eventlog”. This command will search all the command contain work “eventlog”. To simulate the error, we need to use Write-EventLog command.

Command: get-command –Name *eventlog

image

Step 2: To simulate the Error EventLog, please follow below command;

Command: Write-Eventlog –LogName Application –Source “Firdaus” –EntryType Error –EventID 8888 Message “for testing only”

As you can see, the Write-EventLog now return with no error. And if we check the event log entries, we should now see out test message.
image

Step 3: Open Event Viewer and verify the Error EventLog

image

Event Properties details of the message:

image

As you can see, the source is now populated with “Firdaus”. You can also use this to create an event log specifically for your script or to create a source for event logs other than the Application log.

[SCOM] Override Storage Threshold Monitoring for AS/400 ASP Monitor


It is always important to understand how AS/400 server workload are doing. Getting visibility into our systems allows us to proactively deal with future issues. As an example, monitoring can let us know that we are running out of disk space on one of our volumes so we can prepare all the necessary things before it happens.

One of our customer received an alert as below from their SCOM monitoring system.

Alert: AS/400 ASP Monitor
Resolution Status: New
Alert Descriptions: ASP number 1 on ASCMYPRD is 61 % used.
Source: ASCMYPRD.1.66
Path: PWMXXXXXXXX.XXBank.my;PWMXXXXXXXX.XXBank.my;XXXXPRD
Last modified by: System
Last modified time: 6/26/2018 10:11:22 AM

From this alert, we can see that disk utilization for AS/400 environment hits 61% whereby the minimum of the disk utilization set for this server only 60%. Customer request to increase disk utilization as the business are keep growth. Below are the steps how to override the value for AS/400 ASP Monitor.

Step 1: Open SCOM Management Console and click on Authoring tab.

Step 2: Click on Monitors and search monitor called AS/400 ASP Disk Utilization Monitor

clip_image001

Step 3: Open AS/400 ASP Disk Utilization Monitor properties

clip_image001[5]

Step 4: Click on Overrides tab and click View Summary button and choose “For all object of class: AS/400 ASP Disk Utilization”
clip_image001[7]
clip_image001[9]

Step 5: On Override Summary, choose the Effective Value = 60 and click Edit. We need to change this value to 68.

clip_image001[11]

Step 6:  Change the override value from 60 to 68 and click Apply. Then click OK

clip_image001[15]
clip_image001[17]

Step 7: Verify the Effective Value in the Overrides Summary

clip_image001[19]

Overriding configuration for AS/400 ASP Disk Utilization monitor completed. Verify the Alert on the SCOM management console.