Skip to content

Commit cb137a2

Browse files
PriskeyJeronika-MSPriskeyJeronika-MS
committed
moving SCOM MI contents to Monitor
1 parent fde266a commit cb137a2

File tree

7 files changed

+679
-0
lines changed

7 files changed

+679
-0
lines changed

‎articles/azure-monitor/scom-manage-instance/index.yml

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
### YamlMime:Landing
2+
title: Azure Monitor SCOM Managed Instance
3+
summary: Learn how to manage Hybrid environment with Azure Monitor SCOM Managed Instance
4+
5+
metadata:
6+
title: Azure Monitor SCOM Managed Instance
7+
description: Learn about how to manage Hybrid environment with Azure Monitor SCOM Managed Instance
8+
author: PriskeyJeronika-MS
9+
ms.service: azure-monitor
10+
ms.topic: landing-page
11+
ms.date: 05/24/2024
12+
ms.author: v-gjeronika
13+
14+
landingContent:
15+
- title: About Azure Monitor SCOM Managed Instance
16+
linkLists:
17+
- linkListType: overview
18+
links:
19+
- text: What is Azure Monitor SCOM Managed Instance?
20+
url: overview.md
21+
- linkListType: whats-new
22+
links:
23+
- text: Feature releases
24+
url: whats-new-scom-managed-instance.md
25+
- linkListType: concept
26+
links:
27+
- text: Service Health Dashboard
28+
url: monitor-health-scom-managed-instance.md
29+
30+
- title: Get started
31+
linkLists:
32+
- linkListType: quickstart
33+
links:
34+
- text: Migrate from Operations Manager on-premises to SCOM Managed Instance
35+
url: migrate-to-operations-manager-managed-instance.md
36+

‎articles/azure-monitor/scom-manage-instance/migrate-to-operations-manager-managed-instance.md

Lines changed: 225 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,225 @@
1+
---
2+
ms.assetid:
3+
title: Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance
4+
description: This quickstart describes how to migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance.
5+
author: PriskeyJeronika-MS
6+
ms.author: v-gjeronika
7+
manager: jsuri
8+
ms.date: 05/22/2024
9+
ms.service: azure-monitor
10+
ms.subservice: operations-manager-managed-instance
11+
ms.topic: quickstart
12+
---
13+
14+
# Quickstart: Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance
15+
16+
This quickstart provides the process of migration from Operations Manager on-premises to Azure Monitor SCOM Managed Instance.
17+
18+
## Prerequisites
19+
20+
1. Verify that your current Operations Manager agent version is supported to multi-homed with SCOM Managed Instance.
21+
22+
>[!Note]
23+
>Agent versions 2022 and 2019 are supported.
24+
2. Deploy a SCOM Managed Instance instance.
25+
26+
3. Configure user roles and permissions in SCOM Managed Instance.
27+
28+
4. Import management packs and overrides from your current Operations Manager environment.
29+
30+
5. Configure Run-As account for management packs.
31+
32+
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.
33+
34+
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:
35+
36+
- Verify that you see the same monitoring data for the service in both your current Operations Manager environment and SCOM Managed Instance.
37+
- Configure groups.
38+
- Configure notification subscriptions.
39+
- Configure reporting.
40+
- Configure Dashboards.
41+
- Configure agent-specific settings.
42+
- Configure Agent primary and failover management server.
43+
44+
Repeat the service-based migration according to step 6 for each application/service.
45+
46+
8. Configure and verify connectors.
47+
For example: Configure and verify connectors for ITSM tools and automation.
48+
49+
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.
50+
51+
>[!Note]
52+
>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.
53+
54+
Provided the migration details for the following artifacts as an example:
55+
56+
- Management Packs and Overrides
57+
- Dashboard
58+
- User roles and permissions
59+
- Notification subscriptions
60+
- Groups
61+
- 1P Integrations
62+
- Agent mapping and configuration
63+
64+
[Here's](#supported-artifacts-for-migration) the complete list of supported artifacts.
65+
66+
## Migrate from on-premises to SCOM Managed Instance
67+
68+
Select the required artifact to view the migration details from on-premises to SCOM Managed Instance:
69+
70+
# [Management Packs and Overrides](#tab/mp-overrides)
71+
72+
1. Run the below script to create an inventory of all existing Management Packs deployed in Operations Manager:
73+
74+
```powershell
75+
Get-SCOMManagementPack | Select-Object DisplayName, Name, Sealed, Version, LastModified | Sort-Object DisplayName | Format-Table
76+
```
77+
78+
2. Export [unsealed Management Packs](/system-center/scom/manage-mp-import-remove-delete?#how-to-export-an-operations-manager-management-pack):
79+
80+
```powershell
81+
Get-SCOMManagementPack | Where{ $_.Sealed -eq $false } | Export-SCOMManagementPack -Path "C:\Temp\Unsealed Management Packs"
82+
```
83+
84+
3. Import [Sealed Management Packs in SCOM Managed Instance](/system-center/scom/manage-mp-import-remove-delete?#importing-a-management-pack).
85+
86+
- You must have a copy of any custom sealed Management Packs that you need to import.
87+
88+
4. Import [unsealed (exported) Management Packs in SCOM Managed Instance](/system-center/scom/manage-mp-import-remove-delete?#import-a-management-pack-from-disk).
89+
90+
### Post migration validation
91+
92+
Follow these steps to validate the migration of Groups and Data collection.
93+
94+
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.
95+
96+
1. **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.
97+
98+
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**).
99+
100+
1. Check the performance views and verify that the performance data has been collected.
101+
102+
# [Dashboard](#tab/dashboard)
103+
104+
Operations Manager supports the following four types of data visualizations.
105+
Below is a quick summary of what can be migrated:
106+
107+
| Types of data visualizations | Can be migrated to SCOM Managed Instance | Recommendations |
108+
|---|---|---|---|---|
109+
| Dashboards/Views that are available in Management Pack | Yes | Operations console |
110+
| Dashboards/Views created on Operations console | Yes | Operations console |
111+
| Reports that are available in Management Pack | No | Power BI reports |
112+
| Reports that are created on Operations console | No | Power BI reports |
113+
114+
- For Dashboards/Views that's 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).
115+
- For Dashboards/Views created on the Operations console, you need to reconfigure custom dashboards and views in SCOM Managed Instance.
116+
- 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.
117+
118+
# [User roles and permissions](#tab/userrole-permission)
119+
120+
>[!Note]
121+
> No 1:1 mapping is permitted between user roles in SCOM Managed Instance to Operations Manager on-premises.
122+
123+
In SCOM Managed Instance, 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](/system-center/scom/manage-security-create-runas-account).
124+
125+
Use the following mapping chart to provide access on SCOM Managed Instance with appropriate permissions:
126+
127+
### Mapping chart
128+
129+
| Operations Manager on-premises | SCOM Managed Instance |
130+
|---------------------------------|-----------------------------------------------|
131+
| Report Operator | Reader |
132+
| Read-Only Operator | Reader |
133+
| Operator | Reader |
134+
| Advanced Operator | Reader |
135+
| Application Monitoring Operator | Reader |
136+
| Author | Contributor |
137+
| Administrator | Contributor |
138+
| Report Security Administrator | Contributor |
139+
| Read-only Administrator | Contributor |
140+
| Delegated administrator | Contributor |
141+
142+
1. Export the list of user roles and users in each role.
143+
144+
```powershell
145+
# This script will export the SCOM User Roles to CSV and Text File Format.
146+
# -----------------------------------------------
147+
# Outputs the file to the current users desktop
148+
# -----------------------------------------------
149+
$UserRoles = @()
150+
$UserRoleList = Get-SCOMUserRole
151+
Write-Output "Processing User Role: "
152+
foreach ($UserRole in $UserRoleList)
153+
{
154+
Write-Output " $UserRole"
155+
$UserRoles += New-Object -TypeName psobject -Property @{
156+
Name = $UserRole.Name;
157+
DisplayName = $UserRole.DisplayName;
158+
Description = $UserRole.Description;
159+
Users = ($UserRole.Users -join "; ");
160+
}
161+
}
162+
$UserRolesOutput = $UserRoles | Select-Object Name, DisplayName, Description, Users
163+
# Table Output
164+
$UserRolesOutput | Format-Table -AutoSize
165+
# CSV Output
166+
$UserRolesOutput | Export-CSV -Path "$env:USERPROFILE`\Desktop\UserRoles.csv" -NoTypeInformation
167+
# Text File Output
168+
$UserRolesOutput | Out-File "$env:USERPROFILE`\Desktop\UserRoles.txt" -Width 4096
169+
```
170+
171+
2. With the exported list and mapping recommendations, manually add the users to the respective Azure (SCOM Managed Instance) user roles.
172+
173+
# [Notification subscriptions](#tab/notification-subscriptions)
174+
175+
SCOM Managed Instance supports the following notification channels:
176+
177+
- Emails
178+
- SMS/Text
179+
180+
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.
181+
182+
After you migrate the notification configuration to SCOM Managed Instance, 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 more steps.
183+
184+
Metadata for all notifications/subscriptions is stored under the unsealed management pack. If you migrate the management pack, the notifications and subscriptions are also migrated.
185+
186+
Microsoft.SystemCenter.Notifications.Internal - 10.22.10113.0 - Notifications Internal Library
187+
188+
>[!Note]
189+
>Notifications/Subscriptions depend on Run as account. Configure the accounts/profiles in a newer environment before you migrate the management pack.
190+
191+
# [Groups](#tab/groups)
192+
193+
Groups are migrated as part of Management Packs. For more information, see **step 5** in the **Management Packs and Overrides** tab.
194+
195+
# [1P Integrations](#tab/integrations)
196+
197+
The following integrations are supported:
198+
199+
- Service Manager
200+
- System Center Virtual Machine Manager
201+
- Azure Monitor
202+
203+
System Center Orchestrator to Azure Automation is the recommendation on Azure equivalent services.
204+
205+
# [Agent mapping and configuration](#tab/agent-mapping-config)
206+
207+
To migrate from System Center Operations Manager agent to SCOM Managed Instance, see [High level overview of upgrading agents and running two environments](/system-center/scom/deploy-upgrade-overview#high-level-overview-of-upgrading-agents-and-running-two-environments-1).
208+
209+
---
210+
211+
### Supported artifacts for migration
212+
213+
- Management Packs and Overrides
214+
- Dashboard
215+
- User roles and permissions
216+
- Notification subscriptions
217+
- Groups
218+
- 1P Integrations
219+
- Agent mapping and configuration
220+
- Gateways
221+
- Custom and 3P Solutions
222+
223+
## Next steps
224+
225+
[Create a SCOM Managed Instance on Azure](create-operations-manager-managed-instance.md).

‎articles/azure-monitor/scom-manage-instance/monitor-health-scom-managed-instance.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
ms.assetid:
3+
title: Azure Monitor SCOM Managed Instance Service Health Dashboard
4+
description: With Azure Monitor SCOM Managed Instance Service Health Dashboard, you can now view the health of SCOM Managed Instance service in real-time.
5+
author: PriskeyJeronika-MS
6+
ms.author: v-gjeronika
7+
manager: jsuri
8+
ms.date: 05/22/2024
9+
ms.service: azure-monitor
10+
ms.subservice: operations-manager-managed-instance
11+
ms.topic: concept-article
12+
---
13+
14+
# Azure Monitor SCOM Managed Instance Service Health Dashboard
15+
16+
With Azure Monitor SCOM Managed Instance Service Health Dashboard, you can now view the health of SCOM Managed Instance service in real-time.
17+
18+
## Key capabilities
19+
20+
Resource Health capability allows you to do the following:
21+
22+
- Monitors your resource and lets you know if it’s running as expected.
23+
- Help you diagnose and get support for service problems that affect your Azure resources.
24+
- Reports on the current and past health of your resources.
25+
26+
For more information, see [Azure Resource Health overview](/azure/service-health/resource-health-overview?WT.mc_id=Portal-Microsoft_Azure_Health).
27+
28+
To troubleshoot the problems in your service, see the following:
29+
30+
- [Troubleshoot issues with Azure Monitor SCOM Managed Instance](./troubleshoot-scom-managed-instance.md).
31+
- [Troubleshoot commonly encountered errors while validating input parameters](./troubleshooting-input-parameters-scom-managed-instance.md).
32+
- Use the [troubleshooting tool](https://portal.azure.com/#view/Microsoft_Azure_Support/TroubleshootV2Blade/assetId/%2Fsubscriptions%2F5a87dd7e-200a-4e94-8cd6-a9461de63755%2FresourceGroups%2Fsaipwus2rg1%2Fproviders%2FMicrosoft.Scom%2FmanagedInstances%2Fsaipscom1) to get recommended solutions.

0 commit comments

Comments
 (0)