Steps need to be taken::

- Run Exchange 2010 Management Pack setup on a Management Server
- Stop the Microsoft Exchange Monitoring Correlation service
- Import the Management Packs
- Change the Management Server in the config file
- Changing the Service Account
- Start the Microsoft Exchange Monitoring Correlation service

After setting up the Exchange management pack, installing the correlation engine the SCOM server gives errors like “The Microsoft Exchange Monitoring Correlation Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs”.

This is because we have to do some adjustments to get the Exchange 2010 MP to work properly with Operations Manager 2012.

• Run Exchange 2010 Management Pack setup on a Management Server
  
• Stop the Correlation Engine to prevent the event log flooding with errors.
  
• Import the Management Packs
  
• Check the name of the SCOMRMSEmulator.
  

Which server is the RMS Emulator? Usually the first Management Server in the Management Group, but start the SCOM powershell and type:
Get-SCOMRMSEmulator
Copy the FQDN name

• Change the Management Server in the config file
  

The default path is C:\Program Files\Microsoft\Exchange Server\v14\Bin
In there, open the file Microsoft.Exchange.Monitoring.CorrelationEngine.exe.config with notepad or some other Text editor.
Change the value of ‘localhost’ to the FQDN servername of your RMS Emulator.

• Changing the Service Account
  

There is no information about this in the MP guide but you have to change the login account from local service to a user account with proper rights.

• Start the Service
  

Start the Microsoft Exchange Monitoring Correlation service.

Verify that the service functions properly by looking for events from MSExchangeMonitoringCorrelation

You might find a warning event from source Bid with Event Id 1:
C:\Program Files\Microsoft\Exchange Server\v14\Bin\Microsoft.Exchange.Monitoring.CorrelationEngine.exe
5364

Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

System.DllNotFoundException: Unable to load DLL ‘MOMBIDldr.dll’: The specified module could not be found. (Exception from HRESULT: 0×8007007E)
at Bid.internalInitialize()

Just copy the file from C:\Program Files\System Center Operations Manager 2012\Server to C:\Program Files\Microsoft\Exchange Server\v14\Bin
I tried it with the 2007 R2 assembly and with the 2012 RC assembly, both seem to work – at least it doesn’t throw any events anymore

By default, installing SQL Server 2008 R2 on a brand new Windows Server 2008 R2 server does not open the required Windows Firewall port. I always wonder why they don’t give you the option and install to have MS make the changes for you. At any rate, MS has a tool to “Fix It” but on my Windows Server 2008 R2 it ran but doesn’t apply to the Windows 2008 R2 setup.

You can of course follow Microsoft’s KB articles and manually add the Windows Advanced Firewall rules.

For me, a script to do this was the way to go.

@echo ========= SQL Server Ports ===================
@echo Enabling SQLServer default instance port 1433
netsh advfirewall set portopening TCP 1433 “SQLServer”

@echo Enabling Dedicated Admin Connection port 1434
netsh advfirewall set portopening TCP 1434 “SQL Admin Connection”

@echo Enabling conventional SQL Server Service Broker port 4022
netsh advfirewall set portopening TCP 4022 “SQL Service Broker”

@echo Enabling Transact-SQL Debugger/RPC port 135
netsh advfirewall set portopening TCP 135 “SQL Debugger/RPC”

@echo ========= Analysis Services Ports ==============
@echo Enabling SSAS Default Instance port 2383
netsh advfirewall set portopening TCP 2383 “Analysis Services”

@echo Enabling SQL Server Browser Service port 2382
netsh advfirewall set portopening TCP 2382 “SQL Browser”

@echo ========= Misc Applications ==============
@echo Enabling HTTP port 80
netsh advfirewall set portopening TCP 80 “HTTP”

@echo Enabling SSL port 443
netsh advfirewall set portopening TCP 443 “SSL”

@echo Enabling port for SQL Server Browser Service’s ‘Browse’ Button
netsh advfirewall set portopening UDP 1434 “SQL Browser”

@echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK)
netsh advfirewall set multicastbroadcastresponse ENABLE

Yesterday we (me and my college Frank) arrived by car in Las Vegas after a 5 day trip from Zion (very pretty) to the Grand Canyon and back.

Las Vegas is really bizar; shops everywhere, big cars huge hotels and a lot of gambling.

We stay in the Venetian, the place where the MMS is happening.
Curious to hear new features and release dates for the System Center products, especially for SCCM and OpsMgr 2012.

3 new projects are starting after the MMS so some RTM’s would be nice

After importing the HP management Pack earlier this week, today i noticed that a lot of servers where in a warning state.

I opened the Health Explorer I found that the RealtimeMonitors_SNMP.FailedComponent Auto Server Recovery 0 was in warning state, resulting in a RealtimeMonitors_SNMP.HealthState HealthWarning.

After some troubleshooting with the hardware guy’s we found that Automatic Server Recovery on the HP System Management HomePage was disabled.
Enabling ASR fixed the problem.