Skip to content

Commit e7ea9ff

Browse files
committed
updated sentence
1 parent 4050bba commit e7ea9ff

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automation/troubleshoot/update-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ This error can occur for the following reasons:
3737

3838
2. Solution targeting is misconfigured and the machine is not receiving updates as expected.
3939

40-
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**.
40+
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**.
4141

4242
### Resolution
4343

@@ -47,7 +47,7 @@ You may also notice the machine shows with a status of **Non compliant** under *
4747

4848
* 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.
4949

50-
* 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 do this, see [Onboard machines in the workspace](../automation-onboard-solutions-from-automation-account.md#onboard-machines-in-the-workspace).
50+
* 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).
5151

5252
* Remove the worker configuration by following the steps [deleting the hybrid runbook worker](../automation-hybrid-runbook-worker.md#remove-a-hybrid-runbook-worker).
5353

0 commit comments

Comments
 (0)