fixed warnings

Author: SnehaSudhirG

articles/automation/troubleshoot/update-agent-issues-linux.md

@@ -25,7 +25,7 @@ This article discusses how to run the troubleshooter for Azure machines from the
 
 ## Start the troubleshooter
 
-For Azure machines, select the **troubleshoot** link under the **Update Agent Readiness** column in the portal to open the Troubleshoot Update Agent page. For non-Azure machines, the link brings you to this article. To troubleshoot a non-Azure machine, see the instructions in the "Troubleshoot offline" section.
+For Azure machines, select the **troubleshoot** link under the **Update Agent Readiness** column in the portal to open the Troubleshoot Update Agent page. For non-Azure machines, the link brings you to this article. To troubleshoot a non-Azure machine, see the instructions in the **Troubleshoot offline** section.
 
 ![VM list page](../media/update-agent-issues-linux/vm-list.png)
 
@@ -59,7 +59,7 @@ If the asset tag is different than 7783-7084-3265-9085-8269-3286-77, then reboot
 
 ### Monitoring Agent
 
-To fix this, install Azure Log Analytics Linux agent and ensure it communicates the required endpoints. For more information, see [Install Log Analytics agent on Linux computers](../azure-monitor/agents/agent-linux.md).
+To fix this, install Azure Log Analytics Linux agent and ensure it communicates the required endpoints. For more information, see [Install Log Analytics agent on Linux computers](../../azure-monitor/agents/agent-linux.md).
 
 This task checks if the folder is present - 
 
@@ -78,12 +78,14 @@ process_name = "omsagent"
 ps aux | grep %s | grep -v grep" % (process_name) 
 ```
 
-For more information, see [Troubleshoot issues with the Log Analytics agent for Linux](../azure/azure-monitor/agents/agent-linux-troubleshoot).
+For more information, see [Troubleshoot issues with the Log Analytics agent for Linux](../../azure-monitor/agents/agent-linux-troubleshoot.md)
+
 
 ### Multihoming
 This check determines if the agent is reporting to multiple workspaces. Update Management doesn't support multihoming.
 
-To fix this issue, purge the OMS Agent completely and reinstall it with the [workspace linked with Update management](../azure-monitor/agents/agent-linux-troubleshoot#purge-and-re-install-the-linux-agent). 
+To fix this issue, purge the OMS Agent completely and reinstall it with the [workspace linked with Update management](../../azure-monitor/agents/agent-linux-troubleshoot.md#purge-and-reinstall-the-linux-agent)
+
 
 Validate that there are no more multihoming by checking the directories under this path:
 
@@ -143,7 +145,7 @@ You can validate the task by running the **HTTP_PROXY** command.
 
 ### IMDS connectivity check
 
-To fix this issue, allow access to IP **169.254.169.254**. For more information, see [Access Azure Instance Metadata Service](../virtual-machines/windows/instance-metadata-service.md#access-azure-instance-metadata-service). 
+To fix this issue, allow access to IP **169.254.169.254**. For more information, see [Access Azure Instance Metadata Service][Azure Instance Metadata Service (Windows)](../../virtual-machines/windows/instance-metadata-service.md#azure-instance-metadata-service-windows)
 
 After the network changes, you can either rerun the Troubleshooter or run the below commands to validate: 
 
@@ -159,9 +161,9 @@ This check makes sure that the machine has access to the internet and can be ign
 
 This check determines if the Hybrid Runbook Worker can properly communicate with Azure Automation in the Log Analytics workspace.
 
-Proxy and firewall configurations must allow the Hybrid Runbook Worker agent to communicate with the registration endpoint. For a list of addresses and ports to open, see [Network planning](../automation-hybrid-runbook-worker.md#network-planning).
+Proxy and firewall configurations must allow the Hybrid Runbook Worker agent to communicate with the registration endpoint. For a list of addresses and ports to open, see [Network planning](../automation-hybrid-runbook-worker.md#a-namenetwork-planninganetwork-planning)
 
-Fix this issue by allowing the prerequisite URLs. For more information, see [Update Management and Change Tracking and Inventory](../azure/automation/automation-network-configuration#update-management-and-change-tracking-and-inventory). 
+Fix this issue by allowing the prerequisite URLs. For more information, see [Update Management and Change Tracking and Inventory](../automation-network-configuration.md#update-management-and-change-tracking-and-inventory)
 
 Post the network changes you can either re-run the troubleshooter or CURL on provided jrds endpoint.
 
@@ -192,8 +194,7 @@ Curl on provided OMS endpoint
 
 ### Software Repositories
 
-Fix this issue by allowing the [prerequisite Repo URL for RHEL](../automation-network-configuration.md#update-management-and-change-tracking-and-inventory).
-
+Fix this issue by allowing the [prerequisite Repo URL for RHEL](https://learn.microsoft.com/azure/virtual-machines/workloads/redhat/redhat-rhui#troubleshoot-connection-problems-to-azure-rhui)
 Post making Network changes you can either rerun the Troubleshooter or
 Curl on software repositories configured in package manager. Refreshing repos sudo apt-get update would be helpful to confirm the communication as well.
 

articles/automation/troubleshoot/update-agent-issues.md

@@ -44,8 +44,7 @@ Results are shown on the page when they're ready. The checks sections show what'
 
 ### Operating system
 
-The operating system check verifies whether the Hybrid Runbook Worker is running [one of the supported operating systems](../update-management/operating-system-requirements.md#windows). 
-
+The operating system check verifies whether the Hybrid Runbook Worker is running [one of the supported operating systems](../update-management/operating-system-requirements.md#system-requirements)
 
 ### .NET 4.6.2
 
@@ -63,7 +62,8 @@ To fix, you need to download and install [Windows Management Framework 5.1](http
 
 This check determines whether you're using TLS 1.2 to encrypt your communications. TLS 1.0 is no longer supported by the platform. Use TLS 1.2 to communicate with Update Management.
 
-To fix, follow the steps to [Enable TLS 1.2](../agents/agent-windows?tabs=setup-wizard.md#configure-agent-to-use-tls-12).
+To fix, follow the steps to [Enable TLS 1.2](../../azure-monitor/agents/agent-windows.md#configure-agent-to-use-tls-12)
+
 
 ## Monitoring agent service health checks
 
@@ -93,11 +93,10 @@ Raise a support ticket if the issue is not fixed still.
 
 Check the event id 4502 (error event) in **Operations Manager** event logs and check the description.
 
-To troubleshoot, run the [MMA Agent Troubleshooter](../azure-monitor/agents/agent-windows-troubleshoot.md).
-
+To troubleshoot, run the [MMA Agent Troubleshooter](../../azure-monitor/agents/agent-windows-troubleshoot.md).
 
 ### VMs linked workspace
-See [Network requirements](./azure-monitor/agents/agent-windows-troubleshoot.md#connectivity-issues).
+See [Network requirements](../../azure-monitor/agents/agent-windows-troubleshoot.md#connectivity-issues).
 
 To validate: Check VMs connected workspace or Heartbeat table of corresponding log analytics.
 
@@ -158,7 +157,8 @@ After the network changes, you can either rerun the Troubleshooter or run the be
 
 ### Proxy settings
 
-If the proxy is enabled, ensure that you have access to the [prerequisite URLs](../automation-network-configuration#update-management-and-change-tracking-and-inventory). 
+If the proxy is enabled, ensure that you have access to the [prerequisite URLs](../automation-network-configuration.md#update-management-and-change-tracking-and-inventory)
+
 
 To check if the proxy is set correctly, use the below commands: 
 
@@ -171,9 +171,11 @@ or check the registry key **ProxyEnable** is set to 1 in
 
 ### IMDS endpoint connectivity
 
-To fix the issue, allow access to IP **169.254.169.254** </br> For more information see, [access Azure instance metadata service](../virtual-machines/windows/instance-metadata-service.md#access-azure-instance-metadata-service). 
+To fix the issue, allow access to IP **169.254.169.254** </br> For more information see, [access Azure instance metadata service](../../virtual-machines/windows/instance-metadata-service.md#access-azure-instance-metadata-service)
+
 
 After the network changes, you can either rerun the Troubleshooter or run the below commands to validate: 
+
 ```
 Invoke-RestMethod -Headers @{"Metadata"="true"} -Method GET -Uri http://169.254.169.254/metadata/instance?api-version=2018-02-01
 ```
@@ -221,16 +223,16 @@ Configure reboot according to Update Management schedule configuration.
 
 `AlwaysAutoRebootAtScheduledTime AlwaysAutoRebootAtScheduledTimeMinutes`
 
-For more information, see [Configure reboot settings](../troubleshoot/automation/update-management/configure-wuagent.md)
+For more information, see [Configure reboot settings](../update-management/configure-wuagent.md#configure-reboot-settings)
+
 
 ### WSUS Server configuration
 
-If the environment is set to get updates from WSUS, ensure that it is approved in WSUS before the update deployment. For more information, see [WSUS configuration settings](../troubleshoot/automation/update-management/configure-wuagent.md). If your environment is not using WSUS, ensure that you remove the WSUS server settings and [reset Windows update component](../troubleshoot/windows/deployment/update/windows-update-resources.md)
+If the environment is set to get updates from WSUS, ensure that it is approved in WSUS before the update deployment. For more information, see [WSUS configuration settings](../update-management/configure-wuagent.md#make-wsus-configuration-settings). If your environment is not using WSUS, ensure that you remove the WSUS server settings and [reset Windows update component](https://learn.microsoft.com/windows/deployment/update/windows-update-resources#how-do-i-reset-windows-update-components).
 
 ### Automatically download and install
 
-To fix the issue, disable the **AutoUpdate** feature. Set it to Disabled in the local group policy Configure Automatic Updates. For more information, see [Configure automatic updates](../troubleshoot/windows-server/administration/windows-server-update-services/deploy/4-configure-group-policy-settings-for-automatic-updates.md)
-
+To fix the issue, disable the **AutoUpdate** feature. Set it to Disabled in the local group policy Configure Automatic Updates. For more information, see [Configure automatic updates](https://learn.microsoft.com/windows-server/administration/windows-server-update-services/deploy/4-configure-group-policy-settings-for-automatic-updates#configure-automatic-updates).
 
 
 ## <a name="troubleshoot-offline"></a>Troubleshoot offline