Building SCOM 2012 Dashboards

System Center Operations Manager 2012 has significant enhancements in the ability to display data through the use of its new dashboard technologies.
This post is the first in a series of dashboard-related posts introducing these new abilities. This post will create two dashboards:
– An VMM Host performance dashboard which contains the performance indicators of the Hyper-V hosts
– An Environment state dashboard which display’s the current health of the complete environments

SCOM 2012 Dashboards
Before we get into the steps of creating a new dashboard, I will talk a  over a bit of terminology. A dashboard is a collection of data from SCOM which give’s you the right overview on a specific view also named the Network Operations Center (NOC) display.

This shows the health of various key applications, products, or websites that are monitored by Operations Manager. Some Advantages of a dashboard:
– Ability to provide custom charts, graphs, beyond those available in the built-in performance view
– Network Operations Center (NOC) shows the health of various key products or applications
– Build an overview which covers the health of specific product’s

Let’s see how this actually all works…

Step 1 – We first start with the VMM Host Performance dashboard layout.
Note: The Virtual Machine Management pack is required for this dashboard

1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Choose the Management Packs node, click Create Management Pack and type the name (we choose Custom Dashboards) Click Next, Create
4. Go to Monitoring, go to the newly created MP name (Custom Dashboards), right click new, Dashboard view

5. Choose Grid Layout and click next, change the name in VMM Host Performance and click next, choose the 4 Cells option, choose next and create.

Step 2 – Adding Widgets to the dashboard.
1. Go to the Grid Layout and click to add widget

2. In the general properties choose the name of the Widget. We choose:
VMM Nodes – % CPU Performance
VMM Nodes – Memory Available MBytes
VMM Nodes – Logical Disk Reads/sec
VMM Nodes – Logical Disk Writes/sec

3. In the groups section choose Groups and scope it to Hosts in VMM, click next

4. Select the required Performance counters and click next

VMM Nodes – % CPU Performance 
Object:
HyperV Logical Processor
Counter: %Total Run Time
Instance (All)

VMM Nodes – Memory Available MBytes
Object:
Memory
Counter:
Available MBytes
Instance:
(All)

VMM Nodes – Logical Disk Reads/sec
Object:
LogicalDisk
Counter:
Disk Read Bytes/sec 
Instance:
(All)

VMM Nodes – Logical Disk Writes/sec

Object: LogicalDisk
Counter: Disk Writes Bytes/sec 
Instance: (All)

 

6. Click Next, set the time range to 12 Hours (or different)

5. Check the chart preferences and sort so it looks like this
Show the legend
Target
Path
Last value
Minimum Value
Maximum Value
Average Value

6. Click next and finish.
7. Do this for
VMM Nodes – % CPU Performance
VMM Nodes – Memory Available MBytes
VMM Nodes – Logical Disk Reads/sec
VMM Nodes – Logical Disk Writes/sec

 
Note;
HyperV processor monitoring; Why monitor HyperV Logical Processor, %Total Run Time and not the %Processor time

Measure overall processor utilization of the Hyper-V environment using Hyper-V performance monitor counters To measure total physical processor utilization of the host operating system and all guest operating systems, use the “\Hyper-V Hypervisor Logical Processor(_Total)\% Total Run Time” performance monitor counter. This counter measures the total percentage of time spent by the processor running the both the host operating system and all guest operating systems. Use the following thresholds to evaluate overall processor utilization of the Hyper-V environment using the “\Hyper-V Hypervisor Logical Processor(_Total)\% Total Run Time” performance monitor counter:
– Less than 60% consumed = Healthy
– 60% – 89% consumed = Monitor or Caution
– 90% – 100% consumed = Critical, performance will be adversely affected

See http://technet.microsoft.com/en-us/library/cc768535(v=bts.10).aspx for more information

 

 

 

 

 

 

 

Creating Device Collections in SCCM 2012

Create collections in System Center 2012 Configuration Manager to represent logical groupings of users or devices. You can use collections to help you perform many tasks including application management, deploying compliance settings, or installing software updates. You can also use collections to manage groups of client settings or use them with role-based administration to specify the resources that an administrative user can access.

This article limits to collection based device collection groups.

Step 1 – Building / Creating custom Device Collections in SCCM 2012
1. In the Configuration Manager Console, click Assets and Complicance.
2. Right Click Device Collections and choose Create Device Collection
3. Type the Device Collection Name, choose Browse to limit the Collection; we choose All Systems in this example.

4. Choose Add Rule and choose Query Rule
5. Type the Query Rule name (we used Query – <Query name>), and click Edit Query Statement
6. Choose the Criteria Tab and click on the Star

7. Choose Select
7. Make you’re query statement (see some simple examples below)

Collection based on computers in a specific group:
Criterion Value:  Simple
Attribute Class: System Resource
Attribute: System Group Name
Operator:  is equal to
Value:    <Group Name>

Collection based on computers in a specific Active Directory OU
Criterion Value:  Simple
Attribute Class: System Resource
Attribute: System OU Name
Operator:  is equal to
Value:    <OU Name>

Collection based on computers in a specific Active Directory Site
Criterion Value:  Simple
Attribute Class: System Resource
Attribute: AD Site Name
Operator:  is equal to
Value:    <AD Site Name>

Collection based on computers with a specific program in Add/Remove Programs
Criterion Value:  Simple
Attribute Class: Add/Remove Programs
Attribute: Display Name
Operator:  is equal to / is like
Value:    <Program Name>

Example Collections:
 -SQL Servers:
Value: Add/Remove Programs Display name is like “%Microsoft SQL%”

Collection based on computers with a specific file Criterion

Criterion Value:  Simple
Attribute Class: Software Files
Attribute: File Name
Operator:  is equal to
Value:    <File Name>

Collection based on computers in a specific Operating System
Criterion Value:  Simple
Attribute Class: System Resource
Attribute: Operating System Name and Version:  is like
Value:    <%NAME%>

Example Collections:
– Windows Vista:
Value = %Workstation 6.0%
– Windows 7:
Value = %Workstation 6.1%
– Windows 8:
Value = %Workstation 6.2%
– Windows Server 2008:
Value = %Server 6.0%
– Windows Server 2008 R2:
Value = %Server 6.1%
– Windows Server 8:
Value = %Server 6.2%

Collection based on computers of a specific hardware model Criterion
Criterion Value:  Simple
Attribute Class: Computer System
Where: Model
Operator:  is equal to
Value:    <Model>

Direct
Rule Direct rules let you to choose the users or computers that you want to add as members to a collection. This rule gives you direct control over which resources are members of the collection. The membership does not automatically change unless a resource is removed from Configuration Manager. Configuration Manager must discover the resources or you must import the resources before you can add them to a direct rule collection. Direct rule collections have a higher administrative overhead than query rule collections because you must modify this collection type manually. For more information about direct rule collections, see How to Create Collections in Configuration Manager.

Query
Rule Query rules dynamically update the membership of a collection based on a query that Configuration Manager runs on a schedule. For example, you can create a collection of users who are a member of the Human Resources organizational unit in Active Directory Domain Services. Unlike direct rule collections, this collection membership automatically updates when you add or remove new users to the Human Resources organizational unit. For more information about query rule collections, see How to Create Collections in Configuration Manager.

Include
Collections Rule The include collections rule lets you include the members of another collection in a Configuration Manager collection. Configuration Manager updates the membership of the current collection on a schedule if the membership of the included collection changes. For more information about the include collection rule, see How to Create Collections in Configuration Manager.

Exclude
Collections Rule The exclude collections rule lets you exclude the members of another collection from a Configuration Manager collection. Configuration Manager updates the membership of the current collection on a schedule if the membership of the excluded collection changes. For more information about the exclude collection rule, see How to Create Collections in Configuration Manager.

 

 

 

How to backup all SCOM management packs

Very simple powershell script to backup all management packs to disk.
Launch the System Center Operations Manager, Command Shell:

OpsMgr 2007 R2
get-managementpack | export-managementpack -path D:\mgmt\MPBackups

OpsMgr 2012
Get-SCManagementPack | Export-SCManagementPack -path D:\mgmt\MPBackups

The difference in the code above in comparison to the OpsMgr 2007 R2 code is that the ‘get-managementpack’ and ‘export-managementpack’ commands have been modified in SCOM 2012 to become ‘get-scmanagementpack” and ‘export-scmanagementpack’

 

SQL Agent Job Discovery in SCOM is empty

Issue:
When implementing the SQL management pack the “SQL Agent Job state” is empty. Therefore there is no overview which jobs have ran successfully or have failed.

Cause:
The SQL Server Management Pack includes an option to discover and monitor SQL Server Agent Jobs for SQL 2005/2008/2012.  The Discovery for this is disabled by default.

Solution:
To use an override to change the setting for automatic discovery
1. In the Authoring pane, expand Management Pack Objects, and then click Object Discoveries.
2. On the Operations Manager toolbar, click Scope, and then filter the objects that appear in the details pane to include only SQL Server objects.
3. In the Operations Manager toolbar, use the Scope button to filter the list of objects, and then click SQL Server Agent Job.
4. On the Operations Manager toolbar, click Overrides, click Override the Object Discovery, and then click For all objects of class: SQL 20xx Agent

5. In the Override Properties dialog box, click the Override box for the Enabled parameter.
6. Under Management Pack, click New to create an unsealed version of the management pack or use an existing one, and then click OK, or select an unsealed management pack that you previously created in which to save this override. As a best practice, you should not save overrides to the Default Management Pack.

After you change the override setting, the object type is automatically discovered and appears in the Monitoring pane under SQL Server.

NOTE: The script runs every 14400 seconds so it can take up to 4 hours before the discovery takes place. You can shorten this by changing the discovery interval to for example 120 seconds. Don’t forget to change it back to default.

After the discovery the SQL Agent Job State

 

 

 

 

Why download management packs manually instead of from the catalog

When updating OpsMgr management packs the easiest way to do this is to show “Updates available for Installed Management Packs” in the console.

When doing this only the existing imported MP’s are updated.
If the MP is updated with new additional monitoring features it will not show up as needing an update. So if you use the console you will miss new ones.
Because of this I do not recommend using the console update feature but download the MSI from the catalog on the web at http://systemcenter.pinpoint.microsoft.com and extract them, if not you will end up missing MP’s you need.

 

Updating the Exchange 2010 Management Pack in OpsMgr 2007 and OpsMgr 2012

This is a step by step guide on how to update the Exchange Server 2010 management pack with System Center Operations Manager 2007 and 2012.

Installing a fresh installation of the Exchange 2010 MP see http://www.toolzz.com/?p=63

NOTE!
Operations Manager 2007 R2 requires a restart!
Operations Manager 2012 does not require a restart!
The Exchange Monitoring will have downtime during the upgrade of the correlation engine

This article is discusses how to update the Exchange 2010 management pack the proper way.

Step 1 – Checking the current version of the Exchange 2010 MP
1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Choose the Management Packs node,
4. Type Exchange in the search box and check if it is an older version and not already updated.

Step 2 – Updating the Exchange correlation Engine
The correlation update must run on from the server where it is successfully installed. Most likely (and recommended) the Correlation Engine will be installed and updated on the root management server (emulator).

Do the following steps on the RMS Emulator
1. Download the MP software from the Microsoft site http://www.microsoft.com/downloads/details.aspx?FamilyID=7150bfed-64a4-42a4-97a2-07048cca5d23&displaylang=en
2. Choose the proper version (X64)
3. Launch the MSI Package and run the installation and follow the installation


4. As mentioned before
Operations Manager 2007 R2 requires a restart after that you can continue to step 3
Operations Manager 2012 continue to step 3.

Step 3 – Import the Exchange 2010 Management Pack
1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Right-click the Management Packs node, and then click Import Management Packs.
4. The Import Management Packs wizard opens. Click Add, and then click Add from disk.
5. If prompted to connect to the online catalog, click No.
6. The Select Management Packs to import dialog box appears. Go to the directory where your management pack file is located as extracted in Step 1. By default, the location is C:\Program Files\System Center Management Packs.
7. Select both management pack files to import from that directory, and then click Open.
8. On the Select Management Packs page, the management packs that you selected for import are listed.

9. You will receive a prompt indicating that the management pack presents a security risk. This is due to the management pack’s use of agent proxying. Click Yes to allow the import.
10. The Import Management Packs page appears and shows the progress for each management pack. Each management pack is downloaded to a temporary directory, imported to Operations Manager, and then deleted from the temporary directory. If there is a problem at any stage of the import process, select the management pack in the list to view the status details. Click Close.
11. Check the C:\Program Files\Microsoft\Exchange Server\v14\Bin directory content if the update ran successfully

That’s all !
Note:
Because the configuration already took place during the initial installation of the MP the update does not require any adjustments.

 

 

Configure/open Firewall ports for MS SQL 2008 R2/Windows 2008 (R2)

By default, installing SQL Server 2008 R2 on a brand new Windows Server 2008 R2 server does not open the required Windows Firewall ports.
I always wonder why they don’t give you the option during the installation of SQL and let MS make the changes for you. Anyway, MS has a tool to “Fix It” but on my Windows Server 2008 it runs 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. Don’t forget to run the script as Administrator in the CMD box.

@echo =========  SQL Server Ports  ===================
@echo Enabling SQLServer default instance port 1433
netsh firewall set portopening TCP 1433 "SQLServer" 
@echo Enabling Dedicated Admin Connection port 1434
netsh firewall set portopening TCP 1434 "SQL Admin Connection" 
@echo Enabling conventional SQL Server Service Broker port 4022  
netsh firewall set portopening TCP 4022 "SQL Service Broker" 
@echo Enabling Transact-SQL Debugger/RPC port 135 
netsh firewall set portopening TCP 135 "SQL Debugger/RPC" 
@echo =========  Analysis Services Ports  ==============
@echo Enabling SSAS Default Instance port 2383
netsh firewall set portopening TCP 2383 "Analysis Services" 
@echo Enabling SQL Server Browser Service port 2382
netsh firewall set portopening TCP 2382 "SQL Browser" 
@echo =========  Misc Applications  ==============
@echo Enabling HTTP port 80 
netsh firewall set portopening TCP 80 "HTTP" 
@echo Enabling SSL port 443
netsh firewall set portopening TCP 443 "SSL" 
@echo Enabling port for SQL Server Browser Service's 'Browse' Button
netsh firewall set portopening UDP 1434 "SQL Browser" 
@echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK)
netsh firewall set multicastbroadcastresponse ENABLE

Check if the ports are opened successfully (see the picture).

 

 

Alerts from the HP management pack

Issue:
Regarding my blog post on HP monitoring I get a lot of questions on errors which are generated by the HP management pack / SNMP hardware logs; these errors are displayed in the Computer State not in the Active Alerts.

The description is very poor but it suggests that there are issues in the HP Hardware logs.

Context: Date and Time: 11/11/2011 10:20:52 AM Property Name Property Value Processors_SNMP.HealthState HealthSuccess Cooling_SNMP. HealthState HealthSuccess RealtimeMonitors_SNMP.HealthState HealthSuccess TemperatureSensors_ SNMP.HealthState HealthSuccess Logs_SNMP.HealthState HealthError

Logs_SNMP.FailedComponent Integrated Management Log Server Others_SNMP.HealthState HealthSuccess Health explorer

Cause:
The cause is in the computer’s local HP log which is in a bad state and has errors which are not resolved (cleared or fixed). Therefore it will stay in bad state.

Solution:
The solution is most of the time very simple. Clearing the HP log on the local server and resetting the OpsMgr heath state will solve the issue. You can do this in the HP homepage on the local computer which is causing the issue.

Monitoring Exchange 2010 with OpsMgr 2012

This is a step by step guide on how to configure the monitoring for Exchange Server 2010 with System Center Operations Manager 2012. Normally the Microsoft Exchange 2010 MP will not automatically start monitoring all features.

This article is discusses how to enable these features and to start monitoring of Exchange 2010 the proper way.

Perquisites – Before you import the Microsoft Exchange Server 2010 Management Pack, take the following actions:

  • Ensure that all Exchange 2010 computers that are managed by the Operations Manager use LocalSystem as the Agent Action Account.
  • If you are monitoring Exchange 2010 database availability groups (DAGs), ensure that all DAG members are monitored by Operations Manager 2012 (agent must be installed)
  • Ensure that all agents on Exchange 2010 computers have Agent Proxy enabled.
  • Determine which server will host the Correlation Engine. While not strictly required, it’s strongly recommended that the Correlation Engine be installed on the root management server emulator.

Step 1 – Installing the Exchange correlation Engine and configure Agent proxying
As mentioned before determine which server will host the Correlation Engine. While not strictly required, it’s strongly recommended that the Correlation Engine be installed on the root management server emulator.

Do the following steps on the RMS Emulator
1. Download the MP software from the Microsoft site http://www.microsoft.com/downloads/details.aspx?FamilyID=7150bfed-64a4-42a4-97a2-07048cca5d23&displaylang=en
2. Choose the proper version (X64)
3. Launch the MSI Package and run the installation and follow the installation
It’s known that SCOM 2012 has known issues wit the correlation engine. See http://www.toolzz.com/?p=49 for more information. To stop the event flooding stop the Exchange correlation engine and change the above settings.

 

To enable Agent Proxy configuration on all managed Exchange servers, in the
1. Administration pane, under Administration, Device Management, Agent Managed
2. Right-click on each Exchange server, select Properties, then the Security tab
3. Check the box Allow this agent to act as a proxy and discover managed objects on other computers.
This step will also make exchange cluster instances to appear in the Agentless Managed section (ensure that all physical nodes of the cluster are monitored). Repeat the process for every managed Exchange 2010 server in the list.

 

Step 2 – Import the Exchange 2010 Management Pack
1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2012 management group.
2. In the Operations console, click Administration.
3. Right-click the Management Packs node, and then click Import Management Packs.
4. The Import Management Packs wizard opens. Click Add, and then click Add from disk.
5. If prompted to connect to the online catalog, click No.
6. The Select Management Packs to import dialog box appears. Go to the directory where your management pack file is located as extracted in Step 1. By default, the location is C:\Program Files\System Center Management Packs.
7. Select both management pack files to import from that directory, and then click Open.
8. On the Select Management Packs page, the management packs that you selected for import are listed.
9. You will receive a prompt indicating that the management pack presents a security risk. This is due to the management pack’s use of agent proxying. Click Yes to allow the import.
10. The Import Management Packs page appears and shows the progress for each management pack. Each management pack is downloaded to a temporary directory, imported to Operations Manager, and then deleted from the temporary directory. If there is a problem at any stage of the import process, select the management pack in the list to view the status details. Click Close.

 

Step 3 – Create Test Mailboxes for Synthetic Transaction Tests
The Exchange 2010 Management Pack can run synthetic transactions to help you measure the performance of monitored objects in your Exchange organization. The Exchange 2010 Management Pack uses the Test-OwaConnectivity, Test-ActiveSyncConnectivity, and Test-WebServicesConnectivity cmdlets to test Microsoft Office Outlook Web App, Exchange ActiveSync, and Exchange Web Services connectivity from Client Access servers to Mailbox servers.

1. Open the Exchange Management Shell.
2. In the Shell, change directory to the C:\ Program Files\Microsoft\Exchange Server\V14\Scripts folder by running the following command:
Set-Location C:\Program Files\Microsoft\Exchange Server\V14\Scripts
3. Run the test-user script using the following command:
New-TestCasConnectivityUser.ps1
4. Follow the on-screen installation instructions in the Shell to create the test mailbox. You’ll be prompted to enter a temporary secure password for creating test users. You’ll also be prompted to specify the Mailbox server where you want the test user created.
5. Repeat this process on all Exchange 2010 Mailbox servers in each Active Directory site that you want to test.

Possible issue:
When trying to run the new-TestCasConnectivityUser.ps1 script the latter might fail with the following error CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password meets complexity requirements.
The first thing you need to do is making sure that the password does meets complexity requirements however if you did and still having the failure you most probably have multiple OUs with name “Users” and that is why the script is failing.
The solution for this is to specify the OU in the command by running the following .\new-TestCasConnectivityUser.ps1 OU domain.com/users

 

Step 4 – Configure the MP in OpsMgr Creating a New Management Pack for Customizations.
The Microsoft Exchange 2010 MP does not work properly out of the box, therefore we recommend to create an override management pack and save overrides for Exchange in this management pack.
1. In the Operations console, click Administration.
2. Right Click Management Packs
3. Create new management pack
4. Give the MP a name example: “Custom – Exchange 2010

.
Known Issue 1
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”.

Exchange 2010 Monitoring with SCOM 2012 – Correlation Service Issue
http://www.toolzz.com/?p=49

Known Issue 2
When you run the .\new-testcasconnectivityuser.ps1 script from the C:\Program Files\Microsoft\Exchange Server\v14\scripts directory you get the following error:


CreateTestUser : Mailbox could not be created.
Verify that OU ( Users ) exists and that password meets complexity requi  rements.  At C:\Program Files\Microsoft\Exchange Server\v14\scripts\new-TestCasConnectivityUser.ps1:267 char:31  +       $result = CreateTestUser <<<<  $exchangeServer $mailboxServer $securePassword $OrganizationalUnit $UMDialPlan $  UMExtension $Prompt      + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException      + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,CreateTestUser

The error you got usually turns up if there are multiple OUs in the AD domain called Users. Resolution: Open the script new-TestCasconnectivityUser.ps1 with notepad or any other texteditor and search for the section $OrganizationalUnit = “Users” Replace ´Users´ with ´domain.local/Users´ (replace domain.local with your domain) or to a path to some OU of your choice.

 

 

 

Exchange 2010 Monitoring with SCOM 2012 – Correlation Service Issue

Issue
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”.

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

Solution
Summary:
1. Run Exchange 2010 Management Pack setup on a Management Server
2. Stop the Correlation Engine to prevent the event log flooding with errors.
3. Import the Management Packs
4. Check the name of the SCOMRMSEmulator.
5. Change the Management Server in the config file
6. Changing the Service Account
7. Start the Microsoft Exchange Monitoring Correlation service

Presuming that importing the management pack and installation of the correlation engine finished successfully we continue with step 4; don’t forget to stop the Exchange correlation service

Step 4: Check the name of the SCOMRMSEmulator.
Which server is the RMS Emulator? Usually the first Management Server in the Management Group, but to be sure
– start the SCOM powershell and type:
Get-SCOMRMSEmulator
– Copy the FQDN name

Step 5: Change the Management Server in the config file
The default path is C:\Program Files\Microsoft\Exchange Server\v14\Bin
– 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.

Step 6. Changing the Service Account
– Start Services.msc
– Go to the “Microsoft Exchange Monitoring Correlation” service, choose properties Go to the logon tab
– Fill in a user account with proper rights in Exchange (Admin)

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.

Check the eventviewer.

Sometimes You might find a warning event from
Source Bid
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: 0x8007007E) at Bid.internalInitialize()

To solve this, 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