Oracle MP for SCOM 2012 R2

Oracle MP for SCOM 2012 R2:

• Oracle is one of the Widely used databases in the world. They are proven for there robustness in transaction databases and can easily scale through Peta bytes of data for Datawharehousing.
• SCOM is the enterprise monitoring tool used to monitor the Infrastructure and leads the Gartner Monitoring Quadrant for many years.
• Oracle has released a free Connector which you can download and install and intergrate with SCOM.
• Features Include: 
   

  -	Bi-directional exchange of alerts between Microsoft SCOM and Enterprise Manager
  -	Automatic synchronization of alert state in Microsoft SCOM with the state of alert in Oracle Enterprise Manager (and vice-versa)
  -	Webservices based communication
  -	Out-of-box mapping of Oracle Enterprise Manger alert severity to SCOM alert severity
  -	Ability to customize severity mapping between Enterprise Manager alert and SCOM event

• You can see live demo on how it works by clicking here --> click here
• You can download the connector here --> Click here

HP latest Management Pack for Blade Systems and Proliant Servers - Step by Step Installation steps

HP latest Management Pack for Blade Systems and Proliant Servers - Step by Step Installation steps:

• HP has released the latest MP for monitoring the Blade and Proliant server
• Following are the list of MP:
• HP BladeSystem Management Pack (v 2.1)
• HP ProLiant Agentless Management Pack (v 3.1)
• HP ProLiant Linux Management Pack (v 3.1)
• HP ProLiant PRO Management Pack (v 2.1)
• HP ProLiant Server Management Pack (v 2.2)
• HP ProLiant VMware Management Pack (v 3.1) 
• You can download it from the here --> Click here

Following are the Components that are important in this MP:

• HP management packs
• HP Device Monitor Console (DMC)
• HP Device Monitor Service(DMS)
• HP Custom Data Manager(CDM)

HP management Packs:

              I suggest you install the HP Blade System Management Pack and the HP Proliant Server Management Pack. These should be enought to monitor all the Servers. Other are just some additional addon.

HP Device Monitor Console (DMC):

The HP Device Monitor Console (DMC) provides the user interface for connecting to the HP Device

Monitor Service (DMS) to add or remove devices supported by management packs that use the 

DMS. 

So you need to Install DMC first. You can install on any management server.
If you are already having older version called as HP enterprise manager, then Device Console replaces it.Just install the new DMC and it will automatically upgrade.

Then install the Above MP and everything will be discovered and start working.

How improve performance of your Windows Server by 40 % with this simple tweak

How improve performance of your Server by 40 % with this simple tweak

• Many people see slugish performance of there server ,especially if your server is SQL server and its hosted on Windows 2008 R2.
• The reason is very simple and buy doing this small change it will give you 60 % better performance of your system
• The reason is because of Power settings. In Windows 2008 R2 the Power settings is set as "balanced". What this does it to save power it reduces power consumption to the server
• This wont be visible if you run and check some simple query.
• But as you server runs lot o transactions, you can see poor performance and complaint from your customers.
• Inorder to fix it change the Power settings to " High Performance"
• This will improve the PC perforamance by 40 %.
• This tweeks applies to all Windows Servers versions, but it is more siver in Windows 2008 R2 

Exchange 2010 MP not raising alerts after upgrading from SCOM 2007 to SCOM 2012 R2

Exchange 2010 MP not raising alerts after upgrading from SCOM 2007 to SCOM 2012 R2

• Recently we upgraded from SCOM 2007 to SCOM 2012, after upgrade we also migrated the MP's.
• Everything seems to work fine and after couple of days we got a call from Exchange team that they are not receiving Exchange 2010 related alerts.
• Exchange 2010 raises alerts based on correlation engine. So Correlation Engine decides when to raise an alert.
• So we immediately went and check on the RMS emulator server where the correlation engine was installed.
• We checked the "Application Logs" and there is lot of  Event ID 717 logged.
• When further investigated we found that the Exchange Correlation Auto alert resolution feature is failing because of which you see this Event ID 717.
• Looks like Exchange 2010 Correlation Engine is no longer compatible with SCOM 2012.
• To resolve this 
• We uninstalled the Exchange Correlation engine from Management Server (RMS emulator).
• We Installed Exchange Correlation engine on normal system which is not a Management Server.
• Then Stopped the Microsoft Exchange Monitoring Correlation service and Copied SCOM 2007 R2 SDK binaries into the Correlation Engine install directory %\Program Files\Microsoft\Exchange Server\v14\Bin. 
• Microsoft.EnterpriseManagement.OperationsManager.Common.dll
• Microsoft.EnterpriseManagement.OperationsManager.dll
• MomBidLdr.dll
• Start the Microsoft Exchange Monitoring Correlation and the alerts started flowing again.

SCOM Data access Service and Config Service failing to start after recent SCCM Patching

SCOM Data access Service and Config Service failing to start after recent SCCM Patching

• After recent SCCM patching window where the SCOM servers got patched, i got a call from support team that the SCOM Data access service (SDK service) and Config Service are not starting.
• Further investigation revealed that a particular patch KB2677070 was causing the issue as it was trying to access the intenet to check on revoked trusted certificates.
• As most corporate enviorment internet is blocked from prouction servers this started faining can caused the service not to start.
• After uninstall the patch and reboot the server, the services started without any issue.
• Another solution is that you have go to th registry
• HKLM\Software\Policies\Microsoft\SystemCertificates
• Right-click AuthRoot, select New, and then click DWORD.
• Type DisableRootAutoUpdate, and then press Enter.
• Right-click DisableRootAutoUpdate, and then click Modify.
• In the Value data box, type 1, and then click OK.

SCOM 2012 R2 giving error Operations Manager Database Grooming not compelted Succesfully

SCOM 2012 R2 giving error Operations Manager Database Grooming not compelted Succesfully:

 

• You might get this error in your SCOM console and not sure what to do, lets understand what this alert means and work from there fixing this.
• So when you get this alert, first go and check your grooming settings to see how old alerts can be in SCOM operatoins Database, default is 7 days.
• Then create a view to filter alerts more than 7 days in closed state
• If you see more than 10000 alerts then your grooming is not working.
• Ok now how to fix it.Lets login to to the Operations Manager Database
• Open the query Window and run SELECT * FROM interaljobhistory order by interaljobhistoryid DESC.
• You can see 4 jobs with daily date updated, it will have a 0 or 1 net to it. If its 1 then its success.If its 0 then its failed.
• Now if the failed are more than1 then open the query windows and the run the Grooming Job manually EXEC p_groomingandPartitioning
• It will take long time some time close to 8 hours. If it succeeds then run the SELECT * FROM interaljobhistory order by interaljobhistoryid DESC and see if it succeded.
• If it fails the erro will tell you what the issue is. If its transaction log full error, then take a backup of your transaction logs and then run the above job.
• If the error is temb db full , then increase the space in temp db and try running the query again.
• If the error is LOCK error, then stop all the SCOM services on the managment server and then run the query and wait till it successeds.
• You also try changing the grooming settings .increase the number of days from 7 to 30 for all config in grooming settings and then run the job. If it succeds, the start reducing the days 1 day at a time and keep doing till it reaches optimum level.
• Another technique is to run just the failed jobs that you seel when you run the select query and see if it succeds. 

Scom tutorial to get primary management server

1. Scom is pretty powerful tools to get the management server
2. To get the primary management server use.
3. The powershell command get-primarymangementsever