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
After you set up integration with Azure Monitor logs for your Automation State Configuration data, a
75
-
**Log search** button will appear on the **DSC Nodes** blade of your automation account. Click the
76
-
**Log Search** button to view the logs for DSC node data.
74
+
After you set up integration with Azure Monitor logs for your Automation State Configuration data, they can be viewed by selecting **Logs** in the **Monitoring** section in the left pane of the State Configuration (DSC) page.
You can also view the logs by searching in Azure Monitor logs. See [Find data using log searches](https://docs.microsoft.com/azure/azure-monitor/log-query/log-query-overview). Type the following query to find your State Configuration logs.
92
87
93
-
You can also narrow the query by the operation name. For example:
Copy file name to clipboardExpand all lines: articles/automation/automation-windows-hrw-install.md
+23-19Lines changed: 23 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,9 @@ ms.topic: conceptual
10
10
11
11
You can use the Hybrid Runbook Worker feature of Azure Automation to run runbooks directly on the computer that's hosting the role and against resources in the environment to manage those local resources. Runbooks are stored and managed in Azure Automation and then delivered to one or more designated computers. This article describes how to install the Hybrid Runbook Worker on a Windows machine.
12
12
13
+
> [!NOTE]
14
+
This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.3.0). For Az module installation instructions, see [Install the Azure PowerShell module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.4.0).
15
+
13
16
## Installing the Windows Hybrid Runbook Worker
14
17
15
18
To install and configure a Windows Hybrid Runbook Worker, you can use one of the three following methods:
@@ -25,12 +28,12 @@ To install and configure a Windows Hybrid Runbook Worker, you can use one of the
25
28
26
29
The minimum requirements for a Windows Hybrid Runbook Worker are:
27
30
28
-
* Windows Server 2012 or later.
29
-
* Windows PowerShell 5.1 or later ([download WMF 5.1](https://www.microsoft.com/download/details.aspx?id=54616)).
30
-
* .NET Framework 4.6.2 or later.
31
-
* Two cores.
32
-
* 4 GB of RAM.
33
-
* Port 443 (outbound).
31
+
* Windows Server 2012 or later
32
+
* Windows PowerShell 5.1 or later ([download WMF 5.1](https://www.microsoft.com/download/details.aspx?id=54616))
33
+
* .NET Framework 4.6.2 or later
34
+
* Two cores
35
+
* 4 GB of RAM
36
+
* Port 443 (outbound)
34
37
35
38
To get more networking requirements for the Hybrid Runbook Worker, see [Configuring your network](automation-hybrid-runbook-worker.md#network-planning).
36
39
@@ -45,17 +48,18 @@ After you successfully deploy a runbook worker, review [Run runbooks on a Hybrid
45
48
46
49
Perform the following steps to automate the installation and configuration of the Windows Hybrid Worker role:
47
50
48
-
1. Download the New-OnPremiseHybridWorker.ps1 script from the [PowerShell Gallery](https://www.powershellgallery.com/packages/New-OnPremiseHybridWorker) directly from the computer running the Hybrid Runbook Worker role or from another computer in your environment. Copy the script to the worker.
49
-
50
-
The New-OnPremiseHybridWorker.ps1 script requires the following parameters during execution:
51
+
1. Download the New-OnPremiseHybridWorker.ps1 script from the
52
+
[PowerShell Gallery](https://www.powershellgallery.com/packages/New-OnPremiseHybridWorker) directly from the computer running the Hybrid Runbook Worker role or from another computer in your environment. Copy the script to the worker. The New-OnPremiseHybridWorker.ps1 script requires the following parameters during execution:
51
53
52
-
**AutomationAccountName* (mandatory): The name of your Automation account.
53
54
**AAResourceGroupName* (mandatory): The name of the resource group that's associated with your Automation account.
54
55
**OMSResourceGroupName* (optional): The name of the resource group for the Log Analytics workspace. If this resource group is not specified, *AAResourceGroupName* is used.
55
-
**HybridGroupName* (mandatory): The name of a Hybrid Runbook Worker group that you specify as a target for the runbooks that support this scenario.
56
-
**SubscriptionID* (mandatory): The Azure subscription ID that your Automation account is in.
56
+
**SubscriptionID* (mandatory): The Azure subscription ID that your Automation Account is in.
57
+
**TenantID* (optional): The identifier of the tenant organization associated with your Automation Account.
57
58
**WorkspaceName* (optional): The Log Analytics workspace name. If you don't have a Log Analytics workspace, the script creates and configures one.
58
-
59
+
**AutomationAccountName* (mandatory): The name of your Automation Account.
60
+
**HybridGroupName* (mandatory): The name of a Hybrid Runbook Worker group that you specify as a target for the runbooks that support this scenario.
61
+
**Credential* (optional): The credentials to use when logging in to the Azure environment.
62
+
59
63
> [!NOTE]
60
64
> When enabling solutions, only certain regions are supported for linking a Log Analytics workspace and an Automation Account.
61
65
>
@@ -75,7 +79,7 @@ Perform the following steps to automate the installation and configuration of th
75
79
76
80
4. You're prompted to agree to install NuGet, and you're prompted to authenticate with your Azure credentials.
77
81
78
-
5. After the script is finished, the **Hybrid Worker Groups** page shows the new group and the number of members. If it's an existing group, the number of members is incremented. You can select the group from the list on the **Hybrid Worker Groups** page and select the **Hybrid Workers** tile. On the **Hybrid Workers** page, you see each member of the group listed.
82
+
5. After the script is finished, the **Hybrid Worker Groups** page shows the new group and the number of members. If it's an existing group, the number of members is incremented. You can select the group from the list on the **Hybrid Worker Groups**page and select the **Hybrid Workers** tile. On the **Hybrid Workers** page, you see each member of the group listed.
79
83
80
84
### Manual deployment
81
85
@@ -91,10 +95,10 @@ If you don't already have a Log Analytics workspace, first review the [Azure Mon
91
95
92
96
The Automation solution adds functionality for Azure Automation, including support for Hybrid Runbook Worker. When you add the solution to your Log Analytics workspace, it automatically pushes worker components to the agent computer that you will install in the next step.
93
97
94
-
To add the **Automation** solution to your workspace, run the following PowerShell.
98
+
To add the **Automation** solution to your workspace, run the following PowerShell cmdlet.
#### 3. Install the Log Analytics agent for Windows
@@ -103,15 +107,15 @@ The Log Analytics agent for Windows connects computers to an Azure Monitor Log A
103
107
104
108
To install the agent on the computer, follow the instructions at [Connect Windows computers to Azure Monitor logs](../log-analytics/log-analytics-windows-agent.md). You can repeat this process for multiple computers to add multiple workers to your environment.
105
109
106
-
When the agent has successfully connected to your Log Analytics workspace, after a few minutes you can run the following query to verify it is sending heartbeat data to the workspace:
110
+
When the agent has successfully connected to your Log Analytics workspace after a few minutes, you can run the following query to verify that it is sending heartbeat data to the workspace:
107
111
108
112
```kusto
109
113
Heartbeat
110
114
| where Category == "Direct Agent"
111
115
| where TimeGenerated > ago(30m)
112
116
```
113
117
114
-
In the search results returned, you should see heartbeat records for the computer indicating it is connected and reporting to the service. The heartbeat record is forwarded from every agent by default to its assigned workspace. You can verify that the agent has correctly downloaded the Automation solution when it has a folder called **AzureAutomationFiles** in C:\Program Files\Microsoft Monitoring Agent\Agent. To confirm the version of the Hybrid Runbook Worker, you can browse to C:\Program Files\Microsoft Monitoring Agent\Agent\AzureAutomation\ and note the \\*version* subfolder.
118
+
In the search results returned, you should see heartbeat records for the computer indicating it is connected and reporting to the service. The heartbeat record is forwarded from every agent by default to its assigned workspace. You can verify that the agent has correctly downloaded the Automation solution when it has a folder called **AzureAutomationFiles** in C:\Program Files\Microsoft Monitoring Agent\Agent. To confirm the version of the Hybrid Runbook Worker, browse to C:\Program Files\Microsoft Monitoring Agent\Agent\AzureAutomation\ and note the \\*version* subfolder.
115
119
116
120
#### 4. Install the runbook environment and connect to Azure Automation
117
121
@@ -146,7 +150,7 @@ Runbooks can use any of the activities and cmdlets defined in the modules that a
146
150
147
151
Because the primary purpose of the Hybrid Runbook Worker feature is to manage local resources, you most likely need to install the modules that support these resources. For information on installing Windows PowerShell modules, see [Installing Modules](/powershell/scripting/developer/windows-powershell).
148
152
149
-
Modules that are installed must be in a location referenced by the **PSModulePath** environment variable so that the hybrid worker can automatically import them. For more information, see [Modifying the PSModulePath Installation Path](/powershell/scripting/developer/windows-powershell).
153
+
Modules that are installed must be in a location referenced by the **PSModulePath**environment variable so that the hybrid worker can automatically import them. For more information, see [Modifying the PSModulePath Installation Path](/powershell/scripting/developer/windows-powershell).
0 commit comments