OMS Configuration:

Pre-requisites:

OMS only supports Operations Manager 2012 SP1 UR6 and greater, and Operations Manager 2012 R2 UR2 and greater. Proxy support was added in Operations Manager 2012 SP1 UR7 and Operations Manager 2012 R2 UR3.

All Operations Manager agents must meet minimum support requirements. Ensure that agents are up to the minimum update, otherwise Windows agent traffic will fail and many errors might fill the Operations Manager event log.

An OMS subscription.What is OMS: A SaaS based monitoring tool provided by Microsoft.

By default, we may not get the OMS section in System Center Operations Manager under Administrator Console.

These are my steps to get this fixed.

My SCOM Installed version was 7.1.10226.0 SCOM 2012 RTM

Our OMS will work only if SCOM Version is above UR7.

I have deployed UR9 then on my management server.

We can download this from below URL.

https://support.microsoft.com/en-in/kb/3129774

My Test environment has only management server and operations console.

So I have downloaded the relevant file for management server and operations console.

First I have updated rollup for Management server, we need to restart the server.

Now I have installed the patch for operations console.

Now close the console and re-open the Operations Console.

We need to re-import the management packs which are available in Management Packs for Update Rollup’s

After few investigation, I found that by default, the new management pack for OMS (Advisor) was not imported. So, I

added it. The source of these MP updates are located in C:\Program Files\Microsoft System Center 2012 R2\

Operations Manager\Server\Management Packs for Update Rollups. The following MP has been imported:

Microsoft.SystemCenter.Advisor.Internal.mpb

Microsoft.SystemCenter.Advisor.mpb

Microsoft.SystemCenter.Advisor.Resources.ENU.mpb

Microsoft.SystemCenter.Visualization.Library.mpb

http://scug.be/florent/files/2015/12/image.png

When it’s done, close your SCOM console and reopen it. You will see that the name is now Operations

Management Suite and not Advisor:

When we open the console now we can see Operations Manager Suite.

Now we can see the tab for registration:

Configure OMS proxy settings in the Operations consolePerform the following steps if an internal proxy server is between the management group and OMS web service. These settings are centrally managed from the management group and distributed to agent-managed systems that are included in the scope to collect data for OMS. This is beneficial for when certain solutions bypass the management server and send data directly to OMS web service.+

1. Open the Operations Manager console and select the Administration workspace.

2. Expand Operations Management Suite, and then click Connections.

3. In the OMS Connection view, click Configure Proxy Server.

4. On Operations Management Suite Wizard: Proxy Server page, select Use a proxy server to access the Operations Management Suite, and then type the URL with the port number, for example, http://corpproxy:80 and then click Finish.

+

If your proxy server requires authentication, perform the following steps to configure credentials and settings that need to propagate to managed computers that will report to OMS in the management group.+

1. Open the Operations Manager console and select the Administration workspace.

2. Under RunAs Configuration, select Profiles.

3. Open the System Center Advisor Run As Profile Proxy profile.

4. In the Run As Profile Wizard, click Add to use a Run As account. You can create a new Run As account or use an existing account. This account needs to have sufficient permissions to pass through the proxy server.

5. To set the account to manage, choose A selected class, group, or object, click Select… and then click Group… to open the Group Search box.

6. Search for and then select Microsoft System Center Advisor Monitoring Server Group. Click OK after selecting the group to close the Group Search box.

7. Click OK to close the Add a Run As account box.

8. Click Save to complete the wizard and save your changes.+

After the connection is created and you configure which agents will be collecting and reporting data to OMS, the following configuration is applied in the management group, not necessarily in order:+

The Run As Account Microsoft.SystemCenter.Advisor.RunAsAccount.Certificate is created. It is associated with the Run As profile Microsoft System Center Advisor Run As Profile Blob and is targeting two classes - Collection Server and Operations Manager Management Group.

Two connectors are created. The first is named Microsoft.SystemCenter.Advisor.DataConnector and is automatically configured with a subscription that will forward all alerts generated from instances of all classes in the management group to OMS Log Analytics. The second connector is Advisor Connector, which is responsible for communicating with OMS web service and sharing data.

Agents and groups that you have selected to collect data in the management group will be added to the Microsoft System Center Advisor Monitoring Server Group.

Before this, we need to register an account for OMS on azure.

https://account.windowsazure.com/

Sign-in with Free trail account

If you get some errors like

Error 2200: Unable to register the Advisor Service

Then we need to check for Advisor Mp’s are in place or not.

Switch an Operations Manager group to a new OMS Workspace1. Log in to your OMS subscription and create new workspace in Microsoft

Operations Management Suite.

2. Open the Operations Manager console with an account that is a member of the Operations Manager Administrators role and select the Administration workspace.

3. Expand Operations Management Suite, and select Connections.

4. Select the Re-configure Operation Management Suite link on the middle-side of the pane.

5. Follow the Operations Management Suite Onboarding Wizard and enter the email address or phone number and password of the administrator account that is associated with your new OMS workspace.

Validate Operations Manager Integration with OMS

There are a few different ways you can verify that your OMS to Operations Manager integration is successful.+

To confirm integration from the OMS portal1. In the OMS portal, click on the Settings tile

2. Select Connected Sources.

3. In the table under the System Center Operations Manager section, you should see the name of the management group listed with the number of agents and status when data was last received.

4. Note the Workspace ID value under the left-side of the Settings page. You will validate it against your Operations Manager management group below.

+

To confirm integration from the Operations console1. Open the Operations Manager console and select the Administration

workspace.

2. Select Management Packs and in the Look for: text box type Advisor or Intelligence.

3. Depending on the solutions you have enabled, you will see a corresponding management pack listed in the search results. For example, if you have enabled the Alert Management solution, the management pack Microsoft System Center Advisor Alert Management will be in the list.

4. From the Monitoring view, navigate to the Operations Management Suite\Health State view. Select a Management server under the Management Server State pane, and in the Detail View pane confirm

the value for property Authentication service URI matches the OMS Workspace ID.

How to Remove

Remove Integration with OMS

When you no longer require integration between your Operations Manager management group and OMS workspace, there are several steps required to properly remove the connection and configuration in the management group. The following procedure will have you update your OMS workspace by deleting the reference of your management group, delete the OMS connectors, and then delete management packs supporting OMS. +

1. Open the Operations Manager Command Shell with an account that is a member of the Operations Manager Administrators role.

Warning

Verify you do not have any custom management packs with the word Advisor or IntelligencePack in the name before proceeding, otherwise the following steps will delete them from the management group.

2. From the command shell prompt, type Get-SCOMManagementPack -name

"*advisor*" | Remove-SCOMManagementPack

3. Next type, Get-SCOMManagementPack -name “*IntelligencePack*” |

Remove-SCOMManagementPack

4. Open the Operations Manager Operations console with an account that is a member of the Operations Manager Administrators role.

5. Under Administration, select the Management Packs node and in the Look for: box, type Advisor and verify the following management packs are still imported in your management group:

Microsoft System Center Advisor

Microsoft System Center Advisor Internal

6. In the OMS portal, click on the Settings tile.

7. Select Connected Sources.

8. In the table under the System Center Operations Manager section, you should see the name of the management group you want to remove from the workspace. Under the column Last Data, click Remove.

Note

The Remove link will not be availble until after 14 days if there is no activity detected from the connected management group.

9. A window will appear asking you to confirm that you want to proceed with the removal. Click Yes to proceed.

To delete connectors:

To delete the two connectors - Microsoft.SystemCenter.Advisor.DataConnector and Advisor Connector, save the PowerShell script below to your computer and execute using the following examples. .\OM2012_DeleteConnector.ps1 “Advisor Connector” <ManagementServerName>

.\OM2012_DeleteConnectors.ps1 “Microsoft.SytemCenter.Advisor.DataConnector” <ManagementServerName>

More information: https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-om-agents