Skip to content

Commit f6b0a26

Browse files
fixed warnings
1 parent 30ac1d0 commit f6b0a26

File tree

5 files changed

+8
-8
lines changed

5 files changed

+8
-8
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@
1111
"redirect_document_id": false
1212
},
1313
{
14-
"source_path_from_root": "/articles/azure-monitor/scom-manage-instance/scom-managed-instance-faq.yml",
15-
"redirect_url": "/azure/azure-monitor/scom-manage-instance/common-questions",
14+
"source_path_from_root": "/articles/azure-monitor/scom-manage-instance/common-questions.md",
15+
"redirect_url": "/azure/azure-monitor/scom-manage-instance/scom-managed-instance-faq",
1616
"redirect_document_id": false
1717
},
1818
{

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ To create a SCOM Managed Instance, follow these steps:
125125
1. Under **Review + create**, review all the inputs given so far, and then select **Create**. Your deployment is created on Azure. Creation of a SCOM Managed Instance takes up to an hour.
126126

127127
>[!NOTE]
128-
>If the deployment fails, delete the instance and all the associated resources, and then create the instance again. For more information, see [Delete an instance](./common-questions.md#other-queries).
128+
>If the deployment fails, delete the instance and all the associated resources, and then create the instance again. For more information, see [Delete an instance](./scom-managed-instance-faq.yml#other-queries).
129129
130130
1. After the deployment is finished, select **Go to resource**.
131131

@@ -135,4 +135,4 @@ To create a SCOM Managed Instance, follow these steps:
135135

136136
- [Troubleshoot commonly encountered errors while validating input parameters](troubleshooting-input-parameters-scom-managed-instance.md)
137137
- [Troubleshoot issues with Azure Monitor SCOM Managed Instance](troubleshoot-scom-managed-instance.md)
138-
- [Azure Monitor SCOM Managed Instance frequently asked questions](common-questions.md)
138+
- [Azure Monitor SCOM Managed Instance frequently asked questions](scom-managed-instance-faq.yml)

articles/azure-monitor/scom-manage-instance/monitor-arc-enabled-vm-with-scom-managed-instance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ SCOM Managed Instance users will be able to:
4646

4747
With SCOM Managed Instance, you can monitor Linux workloads that are on-premises and behind a gateway server. At this stage, we don't support monitoring Linux VMs hosted in Azure. For more information, see [How to monitor on-premises Linux VMs](/system-center/scom/manage-deploy-crossplat-agent-console).
4848

49-
For more information, see [Azure Monitor SCOM Managed Instance frequently asked questions](common-questions.md).
49+
For more information, see [Azure Monitor SCOM Managed Instance frequently asked questions](scom-managed-instance-faq.yml).
5050

5151
## Use Arc channel for Agent configuration and monitoring data
5252

articles/azure-monitor/scom-manage-instance/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@
8181
- name: Troubleshoot commonly encountered errors while validating input parameters
8282
href: troubleshooting-input-parameters-scom-managed-instance.md
8383
- name: FAQs
84-
href: common-questions.md
84+
href: scom-managed-instance-faq.yml
8585
- name: Security
8686
items:
8787
- name: Managed Identity

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ To create a SCOM Managed Instance, follow these steps:
141141
1. Under **Review + create**, review all the inputs given so far, and then select **Create**. Your deployment is created on Azure. Creation of a SCOM Managed Instance takes up to an hour.
142142

143143
>[!NOTE]
144-
>If the deployment fails, delete the instance and all the associated resources, and then create the instance again. For more information, see [Delete an instance](./common-questions.md#other-queries).
144+
>If the deployment fails, delete the instance and all the associated resources, and then create the instance again. For more information, see [Delete an instance](./scom-managed-instance-faq.yml#other-queries).
145145
146146
1. After the deployment is finished, select **Go to resource**.
147147

@@ -151,4 +151,4 @@ To create a SCOM Managed Instance, follow these steps:
151151

152152
- [Troubleshoot commonly encountered errors while validating input parameters](troubleshooting-input-parameters-scom-managed-instance.md)
153153
- [Troubleshoot issues with Azure Monitor SCOM Managed Instance](troubleshoot-scom-managed-instance.md)
154-
- [Azure Monitor SCOM Managed Instance frequently asked questions](common-questions.md)
154+
- [Azure Monitor SCOM Managed Instance frequently asked questions](scom-managed-instance-faq.yml)

0 commit comments

Comments
 (0)