Merge pull request #108045 from MGoedtel/task1688235

updated troubleshooting for UM

Author: PRMerger18

articles/automation/troubleshoot/update-management.md

@@ -4,7 +4,7 @@ description: Learn how to troubleshoot and resolve issues with the Update Manage
 services: automation
 author: mgoedtel
 ms.author: magoedte
-ms.date: 03/02/2020
+ms.date: 03/17/2020
 ms.topic: conceptual
 ms.service: automation
 manager: carmonm
@@ -19,6 +19,38 @@ If you encounter issues while you're trying to onboard the solution on a virtual
 
 The following section highlights specific error messages and possible resolutions for each. For other onboarding issues see [Troubleshoot solution onboarding](onboarding.md).
 
+## Scenario: You receive the error "Failed to enable the Update solution"
+
+### Issue
+
+When you attempt to enable the Update Management solution in your Automation account, you encounter the following error:
+
+```error
+Error details: Failed to enable the Update solution
+```
+
+### Cause
+
+This error can occur for the following reasons:
+
+1. The network firewall requirements for the Log Analytics agent may not be configured correctly, causing the agent to fail resolving the DNS URLs.
+
+2. Solution targeting is misconfigured and the machine is not receiving updates as expected.
+
+You may also notice the machine shows with a status of **Non-compliant** under **Compliance**, however **Agent update readiness** is reporting the agent is **Disconnected**.
+
+### Resolution
+
+* Run the troubleshooter for [Windows](update-agent-issues.md#troubleshoot-offline) or [Linux](update-agent-issues-linux.md#troubleshoot-offline), depending on the OS.
+
+* Go to [Network planning](../automation-hybrid-runbook-worker.md#network-planning) to learn about which addresses and ports must be allowed for Update Management to work.  
+
+* Go to [Network planning](../../azure-monitor/platform/log-analytics-agent.md#network-requirements) to learn about which addresses and ports must be allowed for Log Analytic agent to work.
+
+* Check for scope configuration problems. [Scope configuration](../automation-onboard-solutions-from-automation-account.md#scope-configuration) determines which machines get configured for the solution. If your machine is showing up in your workspace but not in the **Update Management** portal, you'll need to configure the scope configuration to target the machines. To learn how to configure the scope configuration, see [Onboard machines in the workspace](../automation-onboard-solutions-from-automation-account.md#onboard-machines-in-the-workspace).
+
+* Remove the worker configuration by following the steps [deleting the hybrid runbook worker](../automation-hybrid-runbook-worker.md#remove-a-hybrid-runbook-worker). 
+
 ## Scenario: Superseded update indicated as missing in Update Management
 
 ### Issue
@@ -65,7 +97,7 @@ You experience the following symptoms:
 
 This issue can be caused by local configuration issues or by improperly configured scope configuration.
 
-You might have to reregister and reinstall the Hybrid Runbook Worker.
+You might have to re-register and reinstall the Hybrid Runbook Worker.
 
 You might have defined a quota in your workspace that's been reached and that's preventing further data storage.