Skip to content

Commit 775abea

Browse files
fixed warnings
1 parent cb137a2 commit 775abea

File tree

7 files changed

+0
-40
lines changed

7 files changed

+0
-40
lines changed
1.79 MB
Loading
Loading
Loading

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

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -219,7 +219,3 @@ To migrate from System Center Operations Manager agent to SCOM Managed Instance,
219219
- Agent mapping and configuration
220220
- Gateways
221221
- 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: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,4 @@ For more information, see [Azure Resource Health overview](/azure/service-health
2727

2828
To troubleshoot the problems in your service, see the following:
2929

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).
3230
- 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.

articles/azure-monitor/scom-manage-instance/overview.md

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -98,21 +98,3 @@ In customer subscription, SCOM Managed Instance, creates a Virtual Machine Scale
9898

9999
Operations Manager Management server and monitored agents are connected through ER/VPN. Agents establish session with Operations Manager Management server using the Kerberos authentication, where Operations Manager Virtual Machine Scale Sets VMs are joined to the AD domain of the monitored agents.
100100

101-
## Next steps
102-
103-
To create SCOM Managed Instance, follow these steps:
104-
105-
- [Step 1. Register the SCOM Managed Instance resource provider](register-scom-managed-instance-resource-provider.md).
106-
- [Step 2. Create separate subnet in a VNet](create-separate-subnet-in-vnet.md).
107-
- [Step 3. Create a SQL Managed Instance](create-sql-managed-instance.md).
108-
- [Step 4. Create a Key vault](create-key-vault.md).
109-
- [Step 5. Create a user assigned identity](create-user-assigned-identity.md).
110-
- [Step 6. Create a computer group and gMSA account](create-gmsa-account.md).
111-
- [Step 7. Store domain credentials in Key vault](store-domain-credentials-in-key-vault.md).
112-
- [Step 8. Create a static IP](create-static-ip.md).
113-
- [Step 9. Configure the network firewall](configure-network-firewall.md).
114-
- [Step 10. Verify Azure and internal GPO policies](verify-azure-and-internal-gpo-policies.md).
115-
- [Step 11. SCOM Managed Instance self-verification of steps](self-verification-of-steps.md).
116-
- [Step 12. Create a SCOM Managed Instance](create-operations-manager-managed-instance.md).
117-
118-
[Migrate from Operations Manager on-premises to Azure Monitor SCOM Managed Instance](migrate-to-operations-manager-managed-instance.md).

articles/azure-monitor/scom-manage-instance/tutorial-create-scom-managed-instance.md

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -36,22 +36,6 @@ This tutorial describes how to create an instance of the service (a SCOM Managed
3636
- West US 2
3737
- West US 3
3838

39-
## Prerequisites
40-
41-
Before you create a SCOM Managed Instance, follow these steps:
42-
43-
- [Step 1. Register the SCOM Managed Instance resource provider](register-scom-managed-instance-resource-provider.md).
44-
- [Step 2. Create separate subnet in a VNet](create-separate-subnet-in-vnet.md).
45-
- [Step 3. Create a SQL Managed Instance](create-sql-managed-instance.md).
46-
- [Step 4. Create a Key vault](create-key-vault.md).
47-
- [Step 5. Create a user assigned identity](create-user-assigned-identity.md).
48-
- [Step 6. Create a computer group and gMSA account](create-gmsa-account.md).
49-
- [Step 7. Store domain credentials in Key vault](store-domain-credentials-in-key-vault.md).
50-
- [Step 8. Create a static IP](create-static-ip.md).
51-
- [Step 9. Configure the network firewall](configure-network-firewall.md).
52-
- [Step 10. Verify Azure and internal GPO policies](verify-azure-and-internal-gpo-policies.md).
53-
- [Step 11. SCOM Managed Instance self-verification of steps](self-verification-of-steps.md).
54-
5539
## Create a SCOM Managed Instance
5640

5741
To create a SCOM Managed Instance, follow these steps:

0 commit comments

Comments
 (0)