Skip to content

Commit 060f563

Browse files
Merge pull request #224553 from SnehaSudhirG/20Jan-AUMDocUpdate
added a new section
2 parents d1d6dbb + 2438bef commit 060f563

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

articles/automation/update-management/overview.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -170,6 +170,20 @@ Customers who have invested in Microsoft Endpoint Configuration Manager for mana
170170

171171
Update Management relies on the locally configured update repository to update supported Windows systems, either WSUS or Windows Update. Tools such as [System Center Updates Publisher](/configmgr/sum/tools/updates-publisher) allow you to import and publish custom updates with WSUS. This scenario allows Update Management to update machines that use Configuration Manager as their update repository with third-party software. To learn how to configure Updates Publisher, see [Install Updates Publisher](/configmgr/sum/tools/install-updates-publisher).
172172

173+
174+
## Update Windows Log Analytics agent to latest version
175+
176+
Update Management requires [Log Analytics agent](../../azure-monitor/agents/log-analytics-agent.md)  for its functioning. We recommend you to update Windows Log Analytics agent (also known as Windows Microsoft Monitoring Agent (MMA)) to the latest version to reduce security vulnerabilities and benefit from bug fixes. Log Analytics agent versions prior to [10.20.18053 (bundle) and 1.0.18053.0 (extension)](../../virtual-machines/extensions/oms-windows.md#agent-and-vm-extension-version) use an older method of certificate handling and hence it is not recommended. Older Windows Log Analytics agents would not be able to connect to Azure and Update Management would stop working on them.
177+
178+
You must update Log Analytics agent to the latest version, by following below steps: 
179+
180+
Check the current version of Log Analytics agent for your machine:  Go to the installation path - *C:\ProgramFiles\Microsoft Monitoring Agent\Agent* and right-click on *HealthService.exe* to check **Properties**. In the **Details** tab, the field **Product version** provides version number of the Log Analytics agent.
181+
182+
If your Log Analytics agent version is prior to [10.20.18053 (bundle) and 1.0.18053.0 (extension)](../../virtual-machines/extensions/oms-windows.md#agent-and-vm-extension-version), upgrade to the latest version of the Windows Log Analytics agent, following these [guidelines](../../azure-monitor/agents/agent-manage.md). 
183+
184+
>[!NOTE]
185+
> During the upgrade process, update management schedules might fail. Ensure to do this when there is no planned schedule.
186+
173187
## Next steps
174188

175189
* Before enabling and using Update Management, review [Plan your Update Management deployment](plan-deployment.md).

0 commit comments

Comments
 (0)