Skip to content

Commit e1b51f6

Browse files
authored
Merge pull request #182653 from SGSneha/13Dec-HybridWorkerV1
Added note on V1 and V2
2 parents d8c3d32 + 26622e5 commit e1b51f6

File tree

4 files changed

+25
-1
lines changed

4 files changed

+25
-1
lines changed

articles/automation/automation-hrw-run-runbooks.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -375,7 +375,6 @@ When starting a runbook using PowerShell, use the `RunOn` parameter with the [St
375375
```azurepowershell-interactive
376376
Start-AzAutomationRunbook -AutomationAccountName "MyAutomationAccount" -Name "Test-Runbook" -RunOn "MyHybridGroup"
377377
```
378-
379378
## Logging
380379
381380
To help troubleshoot issues with your runbooks running on a hybrid runbook worker, logs are stored locally in the following location:

articles/automation/automation-linux-hrw-install.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ The Linux Hybrid Runbook Worker executes runbooks as a special user that can be
1616

1717
After you successfully deploy a runbook worker, review [Run runbooks on a Hybrid Runbook Worker](automation-hrw-run-runbooks.md) to learn how to configure your runbooks to automate processes in your on-premises datacenter or other cloud environment.
1818

19+
> [!NOTE]
20+
> A hybrid worker can co-exist with both platforms: **Agent based (V1)** and **Extension based (V2)**. If you install Extension based (V2) on a hybrid worker already running Agent based (V1), then you would see two entries of the Hybrid Runbook Worker in the group. One with Platform Extension based (V2) and the other Agent based (V1). [**Learn more**](/azure/automation/extension-based-hybrid-runbook-worker-install#install-extension-based-v2-on-existing-agent-based-v1-hybrid-worker).
21+
22+
1923
## Prerequisites
2024

2125
Before you start, make sure that you have the following.

articles/automation/automation-windows-hrw-install.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ Azure Automation stores and manages runbooks and then delivers them to one or mo
1616

1717
After you successfully deploy a runbook worker, review [Run runbooks on a Hybrid Runbook Worker](automation-hrw-run-runbooks.md) to learn how to configure your runbooks to automate processes in your on-premises datacenter or other cloud environment.
1818

19+
> [!NOTE]
20+
> A hybrid worker can co-exist with both platforms: **Agent based (V1)** and **Extension based (V2)**. If you install Extension based (V2)on a hybrid worker already running Agent based (V1), then you would see two entries of the Hybrid Runbook Worker in the group. One with Platform Extension based (V2) and the other Agent based (V1). [**Learn more**](/azure/automation/extension-based-hybrid-runbook-worker-install#install-extension-based-v2-on-existing-agent-based-v1-hybrid-worker).
21+
22+
1923
## Prerequisites
2024

2125
Before you start, make sure that you have the following.

articles/automation/extension-based-hybrid-runbook-worker-install.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,10 @@ Azure Automation stores and manages runbooks and then delivers them to one or mo
1818

1919
After you successfully deploy a runbook worker, review [Run runbooks on a Hybrid Runbook Worker](automation-hrw-run-runbooks.md) to learn how to configure your runbooks to automate processes in your on-premises datacenter or other cloud environment.
2020

21+
22+
> [!NOTE]
23+
> A hybrid worker can co-exist with both platforms: **Agent based (V1)** and **Extension based (V2)**. If you install Extension based (V2)on a hybrid worker already running Agent based (V1), then you would see two entries of the Hybrid Runbook Worker in the group. One with Platform Extension based (V2) and the other Agent based (V1). [**Learn more**](#install-extension-based-v2-on-existing-agent-based-v1-hybrid-worker).
24+
2125
## Prerequisites
2226

2327
### Machine minimum requirements
@@ -123,6 +127,19 @@ You can also add machines to an existing hybrid worker group.
123127

124128
:::image type="content" source="./media/extension-based-hybrid-runbook-worker-install/hybrid-worker-group-platform.png" alt-text="Platform field showing agent or extension based.":::
125129

130+
## Install Extension-based (V2) on existing Agent-based (V1) Hybrid Worker
131+
132+
A hybrid worker can co-exist with both platforms: **Agent based (V1)** and **Extension based (V2)**. To install Extension based (V2) on a hybrid worker that already has an Agent based (V1):
133+
134+
1. Under **Process Automation**, select **Hybrid Workers groups** and then your existing hybrid worker group to go to the **Hybrid Worker Group** page.
135+
1. Under **Hybrid worker group**, select **Hybrid Workers**.
136+
1. Select **+ Add** to go to the **Add machines as hybrid worker** page.
137+
1. Select the checkbox next to existing Agent based (V1) Hybrid worker.
138+
1. Select **Add** to add the machine to the group. </br>
139+
140+
The **Platform** column shows the same worker as both **Agent based (V1)** and **Extension based (V2)**. Delete the Agent based (V1) Hybrid Worker after you are sure on the working of Extension based (V2) worker.
141+
142+
126143
## Delete a Hybrid Runbook Worker
127144

128145
You can delete the Hybrid Runbook Worker from the portal.

0 commit comments

Comments
 (0)