Skip to content

Commit 4341898

Browse files
committed
updated article per PM input
1 parent ed6458c commit 4341898

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

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

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to troubleshoot issues with the Update Management agent.
44
services: automation
55
author: mgoedtel
66
ms.author: magoedte
7-
ms.date: 11/25/2019
7+
ms.date: 12/03/2019
88
ms.topic: conceptual
99
ms.service: automation
1010
ms.subservice: update-management
@@ -13,20 +13,20 @@ manager: carmonm
1313

1414
# Understand the Windows agent check results in Update Management
1515

16-
There may be many reasons your machine isn't showing **Ready** in Update Management. In Update Management, you can check the health of a Hybrid Worker agent to determine the underlying problem. This article discusses how to run the troubleshooter for Azure machines from the Azure portal and Non-Azure machines in the [offline scenario](#troubleshoot-offline).
16+
There may be many reasons your machine isn't showing **Ready** in Update Management. In Update Management, you can check the health of a Hybrid Runbook Worker agent to determine the underlying problem. This article discusses how to run the troubleshooter for Azure machines from the Azure portal and non-Azure machines in the [offline scenario](#troubleshoot-offline).
1717

1818
The following list are the three readiness states a machine can be in:
1919

20-
* **Ready** - The update agent is deployed and was last seen less than 1 hour ago.
21-
* **Disconnected** - The update agent is deployed and was last seen over 1 hour ago.
22-
* **Not configured** - The update agent isn't found or hasn't finished onboarding.
20+
* **Ready** - The Hybrid Runbook Worker is deployed and was last seen less than 1 hour ago.
21+
* **Disconnected** - The Hybrid Runbook Worker is deployed and was last seen over 1 hour ago.
22+
* **Not configured** - The Hybrid Runbook Worker isn't found or hasn't finished onboarding.
2323

2424
> [!NOTE]
2525
> There may be a slight delay between what the Azure portal shows and the current state of the machine.
2626
2727
## Start the troubleshooter
2828

29-
For Azure machines, clicking the **Troubleshoot** link under the **Update Agent Readiness** column in the portal launches the **Troubleshoot Update Agent** page. For Non-Azure machines, the link brings you to this article. See the [offline instructions](#troubleshoot-offline) to troubleshoot a Non-Azure machine.
29+
For Azure machines, clicking the **Troubleshoot** link under the **Update Agent Readiness** column in the portal launches the **Troubleshoot Update Agent** page. For non-Azure machines, the link brings you to this article. See the [offline instructions](#troubleshoot-offline) to troubleshoot a non-Azure machine.
3030

3131
![Update management list of virtual machines](../media/update-agent-issues/vm-list.png)
3232

@@ -45,7 +45,7 @@ Results are shown on the page when they're ready. The checks sections show what'
4545

4646
### Operating system
4747

48-
The operating system check verifies whether the Hybrid Runbook Worker is running one of these operating systems:
48+
The operating system check verifies whether the Hybrid Runbook Worker is running one of the following operating systems:
4949

5050
|Operating system |Notes |
5151
|---------|---------|
@@ -200,5 +200,4 @@ CheckResultMessageArguments : {}
200200

201201
## Next steps
202202

203-
To troubleshoot more issues with your Hybrid Runbook Workers, see [Troubleshoot Hybrid Runbook Workers](hybrid-runbook-worker.md).
204-
203+
To troubleshoot more issues with your Hybrid Runbook Workers, see [Troubleshoot Hybrid Runbook Workers](hybrid-runbook-worker.md).

0 commit comments

Comments
 (0)