SCOM 2012 R2 Console crashes after October Windows Update -Hotfix KB3200006

SCOM 2012 R2 Console crashes after October Windows Update

• The SCOM 2012 R2 Console crashes after installing the Latest October patches.
• This is know issue and microsft has released a Hotfix KB3200006.
• https://support.microsoft.com/en-us/kb/3200006.
• Please downaload the hotfix and install to resolve the Console Crash issue.
• It affects all OS versions. So you need to install on App OS where there is SCOM 2012 R2 Console irrespective of the UR 

Step by Step Procedure to Restore SCOM 2012 R2 Databases after crash or Disaster:

Step by Step Procedure to Restore SCOM 2012 R2 Databases after crash or Disaster:

Many times for various reason we have to restore the SCOM databases.Follow the below procedure

• Start SQL Server Management Studio.
• In the Connect to Server dialog box, select the appropriate values in the Server type drop-down combo box, in the Server name box, and in the Authentication box.
• Click Connect.
• In Object Explorer, expand Databases, and then select the OperationsManager, OperationsManagerAC, or OperationsManagerDW database.
• Right-click the database, point to Tasks, and then click Restore.
• Click Database to open the Restore Database dialog box.
• On the General page, the name of the restoring database appears in the To database list.
• In the To a point in time text box, either retain the default (the most recent possible) or select a specific date and time by clicking the browse button, which opens the Point in Time Restore dialog box.
• To specify the source and location of the backup sets to restore, click the From Device option.
• Click Browse to open the Specify Backup dialog box.
• In the Backup media list box, select one of the listed device types. To select one or more devices for the Backup location list box, click Add.
• In the Select the backup sets to restore grid, select the backups to restore. This grid displays the backups available for the specified location.
• In the Restore options panel, select the Overwrite the existing database option.
• In the Restore the database files as options panel, verify the original database file name and path are correct.
• For the Recovery state options, specify the state option Leave the databases ready to use by rolling back the uncommitted transactions. 
• Additional transaction logs cannot be restored.
• Click OK to restore the database.
• Make sure whenever you restore always restore OperationsManager, and OperationsManagerDW database. Orelse youw ill face 31552 issue.

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.