Upgrading an Operating System from Windows 2003 to Windows 2008: How to Prevent Discovery Problems

Upgrading an Operating System from Windows 2003 to Windows 2008: How to Prevent Discovery Problems

• Before you upgrade the operating system on a monitored computer, uninstall the Operations Manager agent. After the upgrade, reinstall the Operations Manager agent.

Reason:

• The objects that the management pack discovers, such as logical disks, are hosted by a parent class that is not version-specific. When you upgrade the operating system, the order in which discovery occurs can result in duplicate objects being discovered.
• For example, you upgrade a computer running Windows Server 2003 to Windows Server 2008. 
• If the Windows Server 2003 discovery rules run first after the upgrade, the instance of the computer running Windows Server 2003 and its objects will be removed from discovery because the operating system base class has been removed. When the Windows Server 2008 discovery rules run, the computer and its objects will be discovered again.
• If the Windows Server 2008 discovery rules run first after the upgrade, the computer running Windows Server 2008 and its objects will be discovered. When the Windows Server 2003 discovery rules run, the instance of the computer running Windows Server 2003 will be removed from discovery, but the objects hosted by that instance will not be removed.
• So If you upgrade a computer without uninstalling the agent first and then discover duplicate objects, uninstall the agent to mark all hosted objects as deleted in the database. Next, reinstall the agent to only discover existing applications/objects.  

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.