Skip to content

Commit de0db8e

Browse files
committed
updated vmextension troubleshoot article
1 parent 4c76d53 commit de0db8e

File tree

1 file changed

+6
-11
lines changed

1 file changed

+6
-11
lines changed

articles/azure-monitor/platform/vmext-troubleshoot.md

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.service: log-analytics
1111
ms.topic: conceptual
1212
ms.tgt_pltfrm: na
1313
ms.workload: infrastructure-services
14-
ms.date: 01/08/2018
14+
ms.date: 06/06/2019
1515
ms.author: magoedte
1616
---
1717

@@ -40,16 +40,11 @@ If the *Microsoft Monitoring Agent* VM extension is not installing or reporting,
4040
* You can also review the VM agent log file `C:\WindowsAzure\logs\WaAppAgent.log`
4141
* If the log does not exist, the VM agent is not installed.
4242
* [Install the Azure VM Agent](../../azure-monitor/learn/quick-collect-azurevm.md#enable-the-log-analytics-vm-extension)
43-
2. Confirm the Microsoft Monitoring Agent extension heartbeat task is running using the following steps:
44-
* Log in to the virtual machine
45-
* Open task scheduler and find the `update_azureoperationalinsight_agent_heartbeat` task
46-
* Confirm the task is enabled and is running every one minute
47-
* Check the heartbeat logfile in `C:\WindowsAzure\Logs\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent\heartbeat.log`
48-
3. Review the Microsoft Monitoring Agent VM extension log files in `C:\Packages\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent`
49-
4. Ensure the virtual machine can run PowerShell scripts
50-
5. Ensure permissions on C:\Windows\temp haven’t been changed
51-
6. View the status of the Microsoft Monitoring Agent by typing the following in an elevated PowerShell window on the virtual machine `(New-Object -ComObject 'AgentConfigManager.MgmtSvcCfg').GetCloudWorkspaces() | Format-List`
52-
7. Review the Microsoft Monitoring Agent setup log files in `C:\Windows\System32\config\systemprofile\AppData\Local\SCOM\Logs`
43+
2. Review the Microsoft Monitoring Agent VM extension log files in `C:\Packages\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent`
44+
3. Ensure the virtual machine can run PowerShell scripts
45+
4. Ensure permissions on C:\Windows\temp haven’t been changed
46+
5. View the status of the Microsoft Monitoring Agent by typing the following in an elevated PowerShell window on the virtual machine `(New-Object -ComObject 'AgentConfigManager.MgmtSvcCfg').GetCloudWorkspaces() | Format-List`
47+
6. Review the Microsoft Monitoring Agent setup log files in `C:\Windows\System32\config\systemprofile\AppData\Local\SCOM\Logs`
5348

5449
For more information, see [troubleshooting Windows extensions](../../virtual-machines/extensions/oms-windows.md).
5550

0 commit comments

Comments
 (0)