Skip to content

Commit ffde09a

Browse files
authored
Merge pull request #74299 from MGoedtel/UpdateAzMonAgents423
updated agent manage article
2 parents f03398f + 4df23c3 commit ffde09a

File tree

1 file changed

+89
-2
lines changed

1 file changed

+89
-2
lines changed

articles/azure-monitor/platform/agent-manage.md

Lines changed: 89 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,77 @@ ms.service: log-analytics
1111
ms.workload: na
1212
ms.tgt_pltfrm: na
1313
ms.topic: conceptual
14-
ms.date: 03/30/2018
14+
ms.date: 04/23/2019
1515
ms.author: magoedte
1616
---
1717

1818
# Managing and maintaining the Log Analytics agent for Windows and Linux
1919

20-
After initial deployment of the Log Analytics Windows or Linux agent in Azure Monitor, you may need to reconfigure the agent, or remove it from the computer if has reached the retirement stage in its lifecycle. You can easily manage these routine maintenance tasks manually or through automation, which reduces both operational error and expenses.
20+
After initial deployment of the Log Analytics Windows or Linux agent in Azure Monitor, you may need to reconfigure the agent, upgrade it, or remove it from the computer if has reached the retirement stage in its lifecycle. You can easily manage these routine maintenance tasks manually or through automation, which reduces both operational error and expenses.
21+
22+
## Upgrading agent
23+
24+
The Log Analytics agent for Windows and Linux can be upgraded to the latest release manually or automatically depending on the deployment scenario and environment the VM is running in. The following methods can be used to upgrade the agent.
25+
26+
| Environment | Installation Method | Upgrade method |
27+
|--------|----------|-------------|
28+
| Azure VM | Log Analytics agent VM extension for Windows/Linux | Agent is automatically upgraded by default unless you configured your Azure Resource Manager template to opt out by setting the property *autoUpgradeMinorVersion* to **false**. |
29+
| Custom Azure VM images | Manual install of Log Analytics agent for Windows/Linux | Updating VMs to the newest version of the agent needs to be performed from the command line running the Windows installer package or Linux self-extracting and installable shell script bundle.|
30+
| Non-Azure VMs | Manual install of Log Analytics agent for Windows/Linux | Updating VMs to the newest version of the agent needs to be performed from the command line running the Windows installer package or Linux self-extracting and installable shell script bundle. |
31+
32+
### Upgrade Windows agent
33+
34+
To update the agent on a Windows VM to the latest version not installed using the Log Analytics VM extension, you either run from the Command Prompt, script or other automation solution, or by using the MMASetup-\<platform\>.msi Setup Wizard.
35+
36+
You can download the latest version of the Windows agent from your Log Analytics workspace, by performing the following steps.
37+
38+
1. Sign in to the Azure portal.
39+
40+
2. In the Azure portal, click **All services**. In the list of resources, type **Log Analytics**. As you begin typing, the list filters based on your input. Select **Log Analytics workspaces**.
41+
42+
3. In your list of Log Analytics workspaces, select the workspace.
43+
44+
4. In your Log Analytics workspace, select **Advanced settings**, then select **Connected Sources**, and finally **Windows Servers**.
45+
46+
5. From the **Windows Servers** page, select the appropriate **Download Windows Agent** version to download depending on the processor architecture of the Windows operating system.
47+
48+
>[!NOTE]
49+
>During the upgrade of the Log Analytics agent for Windows, it does not support configuring or reconfiguring a workspace to report to. To configure the agent, you need to follow one of the supported methods listed under [Adding or removing a workspace](#adding-or-removing-a-workspace).
50+
>
51+
52+
#### To upgrade using the Setup Wizard
53+
54+
1. Sign on to the computer with an account that has administrative rights.
55+
56+
2. Execute **MMASetup-\<platform\>.exe** to start the Setup Wizard.
57+
58+
3. On the first page of the Setup Wizard, click **Next**.
59+
60+
4. In the **Microsoft Monitoring Agent Setup** dialog box, click **I agree** to accept the license agreement.
61+
62+
5. In the **Microsoft Monitoring Agent Setup** dialog box, click **Upgrade**. The status page displays the progress of the upgrade.
63+
64+
6. When the **Microsoft Monitoring Agent configuration completed successfully.** page appears, click **Finish**.
65+
66+
#### To upgrade from the command line
67+
68+
1. Sign on to the computer with an account that has administrative rights.
69+
70+
2. To extract the agent installation files, from an elevated command prompt run `MMASetup-<platform>.exe /c` and it will prompt you for the path to extract files to. Alternatively, you can specify the path by passing the arguments `MMASetup-<platform>.exe /c /t:<Full Path>`.
71+
72+
3. Run the following command, where D:\ is the location for the upgrade log file.
73+
74+
```dos
75+
setup.exe /qn /l*v D:\logs\AgentUpgrade.log AcceptEndUserLicenseAgreement=1
76+
```
77+
78+
### Upgrade Linux agent
79+
80+
Upgrade from prior versions (>1.0.0-47) is supported. Performing the installation with the `--upgrade` command will upgrade all components of the agent to the latest version.
81+
82+
Run the following command to upgrade the agent.
83+
84+
`sudo sh ./omsagent-*.universal.x64.sh --upgrade`
2185
2286
## Adding or removing a workspace
2387
@@ -26,10 +90,15 @@ After initial deployment of the Log Analytics Windows or Linux agent in Azure Mo
2690
#### Update settings from Control Panel
2791
2892
1. Sign on to the computer with an account that has administrative rights.
93+
2994
2. Open **Control Panel**.
95+
3096
3. Select **Microsoft Monitoring Agent** and then click the **Azure Log Analytics** tab.
97+
3198
4. If removing a workspace, select it and then click **Remove**. Repeat this step for any other workspace you want the agent to stop reporting to.
99+
32100
5. If adding a workspace, click **Add** and on the **Add a Log Analytics Workspace** dialog box, paste the Workspace ID and Workspace Key (Primary Key). If the computer should report to a Log Analytics workspace in Azure Government cloud, select Azure US Government from the Azure Cloud drop-down list.
101+
33102
6. Click **OK** to save your changes.
34103
35104
#### Remove a workspace using PowerShell
@@ -104,8 +173,11 @@ To configure the agent to communicate to the service through a proxy server or [
104173
#### Update settings using Control Panel
105174

106175
1. Sign on to the computer with an account that has administrative rights.
176+
107177
2. Open **Control Panel**.
178+
108179
3. Select **Microsoft Monitoring Agent** and then click the **Proxy Settings** tab.
180+
109181
4. Click **Use a proxy server** and provide the URL and port number of the proxy server or gateway. If your proxy server or Log Analytics gateway requires authentication, type the username and password to authenticate and then click **OK**.
110182

111183
#### Update settings using PowerShell
@@ -160,7 +232,9 @@ Use one of the following procedures to uninstall the Windows or Linux agent usin
160232
161233
#### Uninstall from Control Panel
162234
1. Sign on to the computer with an account that has administrative rights.
235+
163236
2. In **Control Panel**, click **Programs and Features**.
237+
164238
3. In **Programs and Features**, click **Microsoft Monitoring Agent**, click **Uninstall**, and then click **Yes**.
165239
166240
>[!NOTE]
@@ -170,7 +244,9 @@ Use one of the following procedures to uninstall the Windows or Linux agent usin
170244
The downloaded file for the agent is a self-contained installation package created with IExpress. The setup program for the agent and supporting files are contained in the package and need to be extracted in order to properly uninstall using the command line shown in the following example.
171245
172246
1. Sign on to the computer with an account that has administrative rights.
247+
173248
2. To extract the agent installation files, from an elevated command prompt run `extract MMASetup-<platform>.exe` and it will prompt you for the path to extract files to. Alternatively, you can specify the path by passing the arguments `extract MMASetup-<platform>.exe /c:<Path> /t:<Path>`. For more information on the command-line switches supported by IExpress, see [Command-line switches for IExpress](https://support.microsoft.com/help/197147/command-line-switches-for-iexpress-software-update-packages) and then update the example to suit your needs.
249+
174250
3. At the prompt, type `%WinDir%\System32\msiexec.exe /x <Path>:\MOMAgent.msi /qb`.
175251
176252
### Linux agent
@@ -186,14 +262,23 @@ Perform the following steps to configure the Log Analytics agent for Windows to
186262
[!INCLUDE [log-analytics-agent-note](../../../includes/log-analytics-agent-note.md)]
187263
188264
1. Sign on to the computer with an account that has administrative rights.
265+
189266
2. Open **Control Panel**.
267+
190268
3. Click **Microsoft Monitoring Agent** and then click the **Operations Manager** tab.
269+
191270
4. If your Operations Manager servers have integration with Active Directory, click **Automatically update management group assignments from AD DS**.
271+
192272
5. Click **Add** to open the **Add a Management Group** dialog box.
273+
193274
6. In **Management group name** field, type the name of your management group.
275+
194276
7. In the **Primary management server** field, type the computer name of the primary management server.
277+
195278
8. In the **Management server port** field, type the TCP port number.
279+
196280
9. Under **Agent Action Account**, choose either the Local System account or a local domain account.
281+
197282
10. Click **OK** to close the **Add a Management Group** dialog box and then click **OK** to close the **Microsoft Monitoring Agent Properties** dialog box.
198283
199284
### Linux agent
@@ -202,7 +287,9 @@ Perform the following steps to configure the Log Analytics agent for Linux to re
202287
[!INCLUDE [log-analytics-agent-note](../../../includes/log-analytics-agent-note.md)]
203288
204289
1. Edit the file `/etc/opt/omi/conf/omiserver.conf`
290+
205291
2. Ensure that the line beginning with `httpsport=` defines the port 1270. Such as: `httpsport=1270`
292+
206293
3. Restart the OMI server: `sudo /opt/omi/bin/service_control restart`
207294
208295
## Next steps

0 commit comments

Comments
 (0)