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
|`tenant`| Required | The directory tenant that you want to request permission from. Can be provided in GUID or friendly name format OR generically referenced with `common` as seen in the example. |
52
+
|`tenant`| Required | The directory tenant that you want to request permission from. Can be provided in GUID or friendly name format OR generically referenced with `organizations` as seen in the example. Do not use 'common', as personal accounts cannot provide admin consent except in the context of a tenant. To ensure best compatibility with personal accounts that manage tenants, use the tenant ID when possible. |
53
53
|`client_id`| Required | The **Application (client) ID** that the [Azure portal – App registrations](https://go.microsoft.com/fwlink/?linkid=2083908) experience assigned to your app. |
54
54
|`redirect_uri`| Required |The redirect URI where you want the response to be sent for your app to handle. It must exactly match one of the redirect URIs that you registered in the app registration portal. |
55
55
|`state`| Recommended | A value included in the request that will also be returned in the token response. It can be a string of any content you want. Use the state to encode information about the user's state in the app before the authentication request occurred, such as the page or view they were on. |
Copy file name to clipboardExpand all lines: articles/active-directory/hybrid/how-to-connect-password-hash-synchronization.md
+2-6Lines changed: 2 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,13 +118,9 @@ It is typical to force a user to change their password during their first logon,
118
118
119
119
The temporary password functionality helps to ensure that the transfer of ownership of the credential is completed on first use, to minimize the duration of time in which more than one individual has knowledge of that credential.
120
120
121
-
To support temporary passwords in Azure AD for synchronized users, you can enable the *ForcePasswordResetOnLogonFeature* feature, by running the following command on your Azure AD Connect server, replacing <AADConnectorName> with the connector name specific to your environment:
121
+
To support temporary passwords in Azure AD for synchronized users, you can enable the *ForcePasswordResetOnLogonFeature* feature, by running the following command on your Azure AD Connect server:
Caveat: Forcing a user to change their password on next logon requires a password change at the same time. AD Connect will not pick up the force password change flag by itself, it is supplemental to the detected password change that occurs during password hash sync.
Copy file name to clipboardExpand all lines: articles/active-directory/hybrid/reference-connect-sync-attributes-synchronized.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -425,7 +425,7 @@ These attributes are written back from Azure AD to on-premises Active Directory
425
425
| msExchSafeRecipientsHash| ms-Exch-SafeRecipientsHash |X |||Filtering: Writes back on-premises filtering and online safe and blocked sender data from clients. |
426
426
| msExchSafeSendersHash| ms-Exch-SafeSendersHash |X |||Filtering: Writes back on-premises filtering and online safe and blocked sender data from clients. |
427
427
| msExchUCVoiceMailSettings| ms-Exch-UCVoiceMailSettings |X |||Enable Unified Messaging (UM) - Online voice mail: Used by Microsoft Lync Server integration to indicate to Lync Server on-premises that the user has voice mail in online services. |
428
-
| msExchUserHoldPolicies| ms-Exc-hUserHoldPolicies|X |||Litigation Hold: Enables cloud services to determine which users are under Litigation Hold. |
428
+
| msExchUserHoldPolicies| ms-Exch-UserHoldPolicies|X |||Litigation Hold: Enables cloud services to determine which users are under Litigation Hold. |
429
429
| proxyAddresses| proxyAddresses |X |X |X |Only the x500 address from Exchange Online is inserted. |
430
430
| publicDelegates| ms-Exch-Public-Delegates |X |||Allows an Exchange Online mailbox to be granted SendOnBehalfTo rights to users with on-premises Exchange mailbox. Requires Azure AD Connect build 1.1.552.0 or after. |
You can also use the same cmdlet to import a module from PowerShell Gallery directly. Make sure to grab **ModuleName** and **ModuleVersion** from [PowerShell Gallery](https://www.powershellgallery.com).
In the Azure portal, navigate to your Automation Account and select **Modules** under **Shared Resources**. Click **+ Add a module**. Select a **.zip** file that contains your module and click **Ok** to start to import process.
Copy file name to clipboardExpand all lines: articles/automation/troubleshoot/update-agent-issues-linux.md
+20-21Lines changed: 20 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,39 +1,39 @@
1
1
---
2
-
title: Understand the Linux agent check results in Azure Update Management
3
-
description: Learn how to troubleshoot issues with the Update Management agent.
2
+
title: Understand the Linux Hybrid Runbook Worker health in Azure Update Management
3
+
description: Learn how to troubleshoot issues with the Hybrid Runbook Worker on Linux that supports Update Management.
4
4
services: automation
5
-
author: bobbytreed
6
-
ms.author: robreed
7
-
ms.date: 04/22/2019
5
+
author: mgoedtel
6
+
ms.author: magoedte
7
+
ms.date: 12/03/2019
8
8
ms.topic: conceptual
9
9
ms.service: automation
10
10
ms.subservice: update-management
11
11
manager: carmonm
12
12
---
13
13
14
-
# Understand the Linux agent check results in Update Management
14
+
# Understand the Linux Hybrid Runbook Worker health 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 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 to troubleshoot a non-Azure machine.
30
30
31
31
32
32
33
33
> [!NOTE]
34
34
> The checks require the VM to be running. If the VM is not running you are presented with a button to **Start the VM**.
35
35
36
-
On the **Troubleshoot Update Agent** page, click **Run Checks**, to start the troubleshooter. The troubleshooter uses [Run command](../../virtual-machines/linux/run-command.md) to run a script on the machine to verify the dependencies that the agent has. When the troubleshooter is complete, it returns the result of the checks.
36
+
On the **Troubleshoot Update Agent** page, click **Run Checks**, to start the troubleshooter. The troubleshooter uses [Run command](../../virtual-machines/linux/run-command.md) to run a script on the machine to verify the dependencies. When the troubleshooter is complete, it returns the result of the checks.
@@ -45,7 +45,7 @@ When complete, the results are returned in the window. The check sections provid
45
45
46
46
### Operating system
47
47
48
-
The OS check, verifies if the Hybrid Runbook Worker is running one of the following Operating Systems:
48
+
The operating system check verifies if the Hybrid Runbook Worker is running one of the following Operating Systems:
49
49
50
50
|Operating system |Notes |
51
51
|---------|---------|
@@ -56,14 +56,14 @@ The OS check, verifies if the Hybrid Runbook Worker is running one of the follow
56
56
57
57
## Monitoring agent service health checks
58
58
59
-
### OMS agent
59
+
### Log Analytics agent
60
60
61
-
This check ensures that the OMS Agent for Linux is installed. For instructions on how to install it, see [Install the agent for Linux](../../azure-monitor/learn/quick-collect-linux-computer.md#install-the-agent-for-linux
61
+
This check ensures that the Log Analytics agent for Linux is installed. For instructions on how to install it, see [Install the agent for Linux](../../azure-monitor/learn/quick-collect-linux-computer.md#install-the-agent-for-linux
62
62
).
63
63
64
-
### OMS Agent status
64
+
### Log Analytics agent status
65
65
66
-
This check ensures that the OMS Agent for Linux is running. If the agent isn't running, you can run the following command to attempt to restart it. For more information on troubleshooting the agent, see [Linux Hybrid Runbook worker troubleshooting](hybrid-runbook-worker.md#linux)
66
+
This check ensures that the Log Analytics agent for Linux is running. If the agent isn't running, you can run the following command to attempt to restart it. For more information on troubleshooting the agent, see [Linux Hybrid Runbook worker troubleshooting](hybrid-runbook-worker.md#linux)
@@ -75,7 +75,7 @@ This check determines if the agent is reporting to multiple workspaces. Multi-ho
75
75
76
76
### Hybrid Runbook Worker
77
77
78
-
This check verifies if the OMS Agent for Linux has the Hybrid Runbook Worker package. This package is required for Update Management to work.
78
+
This check verifies if the Log Analytics agent for Linux has the Hybrid Runbook Worker package. This package is required for Update Management to work.
79
79
80
80
### Hybrid Runbook Worker status
81
81
@@ -95,7 +95,7 @@ This check makes sure that the machine has access to the internet.
95
95
96
96
### Registration endpoint
97
97
98
-
This check determines if the agent can properly communicate with the agent service.
98
+
This check determines if the Hybrid Runbook Worker can properly communicate with Azure Automation the Log Analytics workspace.
99
99
100
100
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 for Hybrid Workers](../automation-hybrid-runbook-worker.md#network-planning)
101
101
@@ -174,5 +174,4 @@ Passed: TCP test for {ods.systemcenteradvisor.com} (port 443) succeeded
174
174
175
175
## Next steps
176
176
177
-
To troubleshoot additional issues with your Hybrid Runbook Workers, see [Troubleshoot - Hybrid Runbook Workers](hybrid-runbook-worker.md)
178
-
177
+
To troubleshoot additional issues with your Hybrid Runbook Workers, see [Troubleshoot - Hybrid Runbook Workers](hybrid-runbook-worker.md)
Copy file name to clipboardExpand all lines: articles/automation/troubleshoot/update-agent-issues.md
+13-14Lines changed: 13 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,39 +1,39 @@
1
1
---
2
-
title: Understand the Windows agent check results in Azure Update Management
3
-
description: Learn how to troubleshoot issues with the Update Management agent.
2
+
title: Understand the Windows Hybrid Runbook Worker health in Azure Update Management
3
+
description: Learn how to troubleshoot issues with the Hybrid Runbook Worker on Windows that supports Update Management.
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
11
11
manager: carmonm
12
12
---
13
13
14
-
# Understand the Windows agent check results in Update Management
14
+
# Understand the Windows Hybrid Runbook Worker health 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
33
33
> [!NOTE]
34
-
> To check the health of an agent, the VM must be running. If the VM isn't running, a **Start the VM** button appears.
34
+
> To check the health of the Hybrid Runbook Worker, the VM must be running. If the VM isn't running, a **Start the VM** button appears.
35
35
36
-
On the **Troubleshoot Update Agent** page, select **Run checks** to start the troubleshooter. The troubleshooter uses [Run Command](../../virtual-machines/windows/run-command.md) to run a script on the machine to verify agent dependencies. When the troubleshooter is finished, it returns the result of the checks.
36
+
On the **Troubleshoot Update Agent** page, select **Run checks** to start the troubleshooter. The troubleshooter uses [Run Command](../../virtual-machines/windows/run-command.md) to run a script on the machine to verify dependencies. When the troubleshooter is finished, it returns the result of the checks.
0 commit comments