You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/troubleshoot/update-agent-issues.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to troubleshoot issues with the Update Management agent.
4
4
services: automation
5
5
author: mgoedtel
6
6
ms.author: magoedte
7
-
ms.date: 11/25/2019
7
+
ms.date: 12/03/2019
8
8
ms.topic: conceptual
9
9
ms.service: automation
10
10
ms.subservice: update-management
@@ -13,20 +13,20 @@ manager: carmonm
13
13
14
14
# Understand the Windows agent check results in Update Management
15
15
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).
17
17
18
18
The following list are the three readiness states a machine can be in:
19
19
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.
23
23
24
24
> [!NOTE]
25
25
> There may be a slight delay between what the Azure portal shows and the current state of the machine.
26
26
27
27
## Start the troubleshooter
28
28
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.
30
30
31
31

32
32
@@ -45,7 +45,7 @@ Results are shown on the page when they're ready. The checks sections show what'
45
45
46
46
### Operating system
47
47
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:
0 commit comments