Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance (preview)
Article
4 minutes to read
This article provides detailed information on how you can migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance (preview).
Provided the procedure for the following artifacts as an example:
Follow these steps to validate the migration of Groups and Data collection.
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.
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.
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).
Check the performance views and verify that performance data has been collected.
Operations Manager supports the following four types of data visualizations.
Below is a quick summary of what can be migrated:
Types of data visualizations
Can be migrated to SCOM Managed Instance (preview)
Recommendations
Dashboards/Views that are available in Management Pack
Yes
Operations console
Dashboards/Views created on Operations console
Yes
Operations console
Reports that are available in Management Pack
No
Power BI reports
Reports that are created on Operations console
No
Power BI reports
For Dashboards/Views that are available in Management Pack, you can view the data similar to the one in Operations Manager on-premises (as they're built into Management Pack).
For Dashboards/Views created on the Operations console, you need to reconfigure custom dashboards and views in SCOM Managed Instance (preview).
For (SSRS) reports that are available in Management Pack and on the Operations console, you need to reconfigure all reports on Power BI as the Reporting Server doesn't exist in SCOM Managed Instance (preview).
Note
No 1:1 mapping is permitted between user roles in SCOM Managed Instance (preview) to Operations Manager on-premises.
In preview, only two user roles are available, whereas Operations Manager on-premises has 10 user profile roles. For more information, see Operations associated with user role profiles.
Use the following mapping chart to provide access on SCOM Managed Instance (preview) with appropriate permissions:
Mapping chart
Operations Manager on-premises
SCOM Managed Instance (preview)
Report Operator
Reader
Read-Only Operator
Reader
Operator
Reader
Advanced Operator
Reader
Application Monitoring Operator
Reader
Author
Contributor
Administrator
Contributor
Report Security Administrator
Contributor
Read-only Administrator
Contributor
Delegated administrator
Contributor
Export the list of user roles and users in each role.
# This script will export the SCOM User Roles to CSV and Text File Format.
# -----------------------------------------------
# Outputs the file to the current users desktop
# -----------------------------------------------
$UserRoles = @()
$UserRoleList = Get-SCOMUserRole
Write-Output "Processing User Role: "
foreach ($UserRole in $UserRoleList)
{
Write-Output " $UserRole"
$UserRoles += New-Object -TypeName psobject -Property @{
Name = $UserRole.Name;
DisplayName = $UserRole.DisplayName;
Description = $UserRole.Description;
Users = ($UserRole.Users -join "; ");
}
}
$UserRolesOutput = $UserRoles | Select-Object Name, DisplayName, Description, Users
# Table Output
$UserRolesOutput | Format-Table -AutoSize
# CSV Output
$UserRolesOutput | Export-CSV -Path "$env:USERPROFILE`\Desktop\UserRoles.csv" -NoTypeInformation
# Text File Output
$UserRolesOutput | Out-File "$env:USERPROFILE`\Desktop\UserRoles.txt" -Width 4096
With the exported list and mapping recommendations, manually add the users to the respective Azure (SCOM Managed Instance (preview)) user roles.
SCOM Managed Instance (preview) supports the following notification channels:
Emails
SMS/Text
Export the Notifications Internal Library Management pack from the Operations Manager Management Group to migrate all your notification settings and import them to SCOM Managed Instance (preview).
After you migrate the notification configuration to SCOM Managed Instance (preview), copy the local files that are used in Command Channels to the same path on all Management Servers in the Notification Resource Pool. If you migrate from Operations Manager 2016, configuring Notification Channel requires additional steps.
Groups are migrated as part of Management Packs. For more information, see step 5 in Management Packs and Overrides tab.
The following integrations are supported:
Service Manager
System Center Virtual Machine Manager
Azure Monitor
System Center Orchestrator to Azure Automation is the recommendation on Azure equivalent services.