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/automation-linux-hrw-install.md
+19-9Lines changed: 19 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Deploy an agent-based Linux Hybrid Runbook Worker in Automation
3
3
description: This article tells how to install an agent-based Hybrid Runbook Worker to run runbooks on Linux-based machines in your local datacenter or cloud environment.
## <aname="remove-linux-hybrid-runbook-worker"></a>Remove the Hybrid Runbook Worker
222
222
223
-
You can use the command `ls /var/opt/microsoft/omsagent`on the Hybrid Runbook Worker to get the workspace ID. A folder is created that is named with the workspace ID.
223
+
Run the following commands on agent-based Linux Hybrid Worker:
1. Under **Process Automation**, select **Hybrid worker groups** and then your hybrid worker group to go to the **Hybrid Worker Group** page.
233
+
1. Under **Hybrid worker group**, select **Hybrid Workers**.
234
+
1. Select the checkbox next to the machine(s) you want to delete from the hybrid worker group.
235
+
1. Select **Delete** to remove the agent-based Linux Hybrid Worker.
236
+
237
+
238
+
> [!NOTE]
239
+
> - This script doesn't remove the Log Analytics agent for Linux from the machine. It only removes the functionality and configuration of the Hybrid Runbook Worker role.
240
+
> - After you disable the Private Link in your Automation account, it might take up to 60 minutes to remove the Hybrid Runbook worker.
241
+
> - After you remove the Hybrid Worker, the Hybrid Worker authentication certificate on the machine is valid for 45 minutes.
228
242
229
-
> [!NOTE]
230
-
> - This script doesn't remove the Log Analytics agent for Linux from the machine. It only removes the functionality and configuration of the Hybrid Runbook Worker role. </br>
231
-
> - After you disable the Private Link in your Automation account, it might take up to 60 minutes to remove the Hybrid Runbook worker.
232
-
> - After you remove the Hybrid Worker, the Hybrid Worker authentication certificate on the machine is valid for 45 minutes.
1. Under **Process Automation**, select **Hybrid worker groups** and then your hybrid worker group to go to the **Hybrid Worker Group** page.
255
+
1. Under **Hybrid worker group**, select **Hybrid Workers**.
256
+
1. Select the checkbox next to the machine(s) you want to delete from the hybrid worker group.
257
+
1. Select **Delete** to remove the agent-based Windows Hybrid Worker.
252
258
253
-
1. Open a PowerShell session in Administrator mode and run the following command with your URL and primary access key values. Use the `Verbose` parameter for a detailed log of the removal process. To remove stale machines from your Hybrid Worker group, use the optional `machineName` parameter.
259
+
> [!NOTE]
260
+
> - After you disable the Private Link in your Automation account, it might take up to 60 minutes to remove the Hybrid Runbook worker.
261
+
> - After you remove the Hybrid Worker, the Hybrid Worker authentication certificate on the machine is valid for 45 minutes.
Copy file name to clipboardExpand all lines: articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md
+29-19Lines changed: 29 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Migrate an existing agent-based hybrid workers to extension-based-workers
3
3
description: This article provides information on how to migrate an existing agent-based hybrid worker to extension based workers.
4
4
services: automation
5
5
ms.subservice: process-automation
6
-
ms.date: 03/15/2023
6
+
ms.date: 03/30/2023
7
7
ms.topic: how-to
8
8
#Customer intent: As a developer, I want to learn about extension so that I can efficiently migrate agent based hybrid workers to extension based workers.
1. Under **Process Automation**, select **Hybrid worker groups** and then your hybrid worker group to go to the **Hybrid Worker Group** page.
821
+
1. Under **Hybrid worker group**, select **Hybrid Workers**.
822
+
1. Select the checkbox next to the machine(s) you want to delete from the hybrid worker group.
823
+
1. Select **Delete** to remove the agent-based Windows Hybrid Worker.
818
824
819
-
1. Open a PowerShell session in Administrator mode and run the following command with your URL and primary access key values. Use the `Verbose` parameter for a detailed log of the removal process. To remove stale machines from your Hybrid Worker group, use the optional `machineName` parameter.
> - After you disable the Private Link in your Automation account, it might take up to 60 minutes to remove the Hybrid Runbook worker.
826
-
> - After you remove the Hybrid Worker, the Hybrid Worker authentication certificate on the machine is valid for 45 minutes.
825
+
> [!NOTE]
826
+
> - After you disable the Private Link in your Automation account, it might take up to 60 minutes to remove the Hybrid Runbook worker.
827
+
> - After you remove the Hybrid Worker, the Hybrid Worker authentication certificate on the machine is valid for 45 minutes.
827
828
828
829
#### [Linux Hybrid Worker](#tab/lin-hrw)
829
830
830
-
You can use the command `ls /var/opt/microsoft/omsagent`on the Hybrid Runbook Worker to get the workspace ID. A folder is created that is named with the workspace ID.
831
+
Run the following commands on agent-based Linux Hybrid Worker:
> - This script doesn't remove the Log Analytics agent for Linux from the machine. It only removes the functionality and configuration of the Hybrid Runbook Worker role. </br>
838
-
> - After you disable the Private Link in your Automation account, it might take up to 60 minutes to remove the Hybrid Runbook worker.
839
-
> - After you remove the Hybrid Worker, the Hybrid Worker authentication certificate on the machine is valid for 45 minutes.
837
+
1.```python
838
+
rm -r /home/nxautomation
839
+
```
840
+
1. Under **Process Automation**, select **Hybrid worker groups** and then your hybrid worker group to go to the **Hybrid Worker Group** page.
841
+
1. Under **Hybrid worker group**, select **Hybrid Workers**.
842
+
1. Select the checkbox next to the machine(s) you want to delete from the hybrid worker group.
843
+
1. Select **Delete** to remove the agent-based Linux Hybrid Worker.
844
+
845
+
846
+
> [!NOTE]
847
+
> - This script doesn't remove the Log Analytics agent for Linux from the machine. It only removes the functionality and configuration of the Hybrid Runbook Worker role. </br>
848
+
> - After you disable the Private Link in your Automation account, it might take up to 60 minutes to remove the Hybrid Runbook worker.
849
+
> - After you remove the Hybrid Worker, the Hybrid Worker authentication certificate on the machine is valid for 45 minutes.
0 commit comments