Muokkaa

Jaa


Quickstart: Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance

This quickstart provides the process of migration from Operations Manager on-premises to Azure Monitor SCOM Managed Instance.

Prerequisites

  1. Verify that your current Operations Manager agent version is supported to multi-homed with SCOM Managed Instance.

    Note

    Agent versions 2022 and 2019 are supported.

  2. Deploy a SCOM Managed Instance instance.

  3. Configure user roles and permissions in SCOM Managed Instance.

  4. Import management packs and overrides from your current Operations Manager environment.

  5. Configure Run-As account for management packs.

  6. If you use multiple management servers in SCOM Managed Instance, deploy a small set of pilot agents and verify failover behavior between management servers in SCOM Managed Instance.

  7. Identify an application or service that is currently monitored by Operations Manager on-premises. Multihome its agents to start reporting to SCOM Managed Instance and Operations Manager on-premises and perform the following steps:

    • Verify that you see the same monitoring data for the service in both your current Operations Manager environment and SCOM Managed Instance.
    • Configure groups.
    • Configure notification subscriptions.
    • Configure reporting.
    • Configure Dashboards.
    • Configure agent-specific settings.
    • Configure Agent primary and failover management server.

    Repeat the service-based migration according to step 6 for each application/service.

  8. Configure and verify connectors. For example: Configure and verify connectors for ITSM tools and automation.

  9. Once all the monitoring data, reporting, notification, connectors, permissions, and groups are verified in SCOM Managed Instance, uninstall agent configuration for the old Operations Manager environment.

Note

Overrides target a specific instance of a class and may not work after migration of management packs, as instance ID might change between management groups. Group membership configured on specific instances might not work either.

Provided the migration details for the following artifacts as an example:

  • Management Packs and Overrides
  • Dashboard
  • User roles and permissions
  • Notification subscriptions
  • Groups
  • 1P Integrations
  • Agent mapping and configuration

Here's the complete list of supported artifacts.

Migrate from on-premises to SCOM Managed Instance

Select the required artifact to view the migration details from on-premises to SCOM Managed Instance:

  1. Run the below script to create an inventory of all existing Management Packs deployed in Operations Manager:

    Get-SCOMManagementPack | Select-Object DisplayName, Name, Sealed, Version, LastModified | Sort-Object DisplayName | Format-Table
    
  2. Export unsealed Management Packs:

    Get-SCOMManagementPack | Where{ $_.Sealed -eq $false } | Export-SCOMManagementPack -Path "C:\Temp\Unsealed Management Packs"
    
  3. Import Sealed Management Packs in SCOM Managed Instance.

    • You must have a copy of any custom sealed Management Packs that you need to import.
  4. Import unsealed (exported) Management Packs in SCOM Managed Instance.

Post migration validation

Follow these steps to validate the migration of Groups and Data collection.

  1. In Groups: Go to Authoring workspace in the Operations Manager console and select Groups. Review the membership of any groups created by the Management Packs and verify that they've been populated with the correct objects.

  2. In Data collection: To verify that the intended objects are discovered, go to Monitoring in the Operations Manager console and review the views for each Management Pack.

    1. Verify that the state views are populated with the correct objects (Servers, Databases, Websites, and so on) and they're being monitored (Health State isn't Unmonitored).

    2. Check the performance views and verify that the performance data has been collected.

Supported artifacts for migration

  • Management Packs and Overrides
  • Dashboard
  • User roles and permissions
  • Notification subscriptions
  • Groups
  • 1P Integrations
  • Agent mapping and configuration
  • Gateways
  • Custom and 3P Solutions

Next steps

Create a SCOM Managed Instance on Azure.