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/azure-monitor/agents/azure-monitor-agent-windows-client.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article describes the instructions to install the agent on Win
4
4
ms.topic: conceptual
5
5
author: shseth
6
6
ms.author: shseth
7
-
ms.date: 10/18/2022
7
+
ms.date: 1/9/2023
8
8
ms.custom: references_region
9
9
ms.reviewer: shseth
10
10
@@ -329,20 +329,23 @@ In order to update the version, install the new version you wish to update to.
329
329
3. The 'ServiceLogs' folder contains log from AMA Windows Service, which launches and manages AMA processes
330
330
4. 'AzureMonitorAgent.MonitoringDataStore' contains data/logs from AMA processes.
331
331
332
-
### Common issues
332
+
### Common installation issues
333
333
334
334
#### Missing DLL
335
335
- Error message: "There's a problem with this Windows Installer package. A DLL required for this installer to complete could not be run. …"
336
336
- Ensure you have installed [C++ Redistributable (>2015)](/cpp/windows/latest-supported-vc-redist?view=msvc-170&preserve-view=true) before installing AMA:
337
337
338
+
#### Not AAD joined
339
+
Error message: "Tenant and device ids retrieval failed"
340
+
1. Run the command `dsregcmd /status`. This should produce the output as `AzureAdJoined : YES` in the 'Device State' section. If not, join the device with an AAD tenant and try installation again.
341
+
338
342
#### Silent install from command prompt fails
339
343
Make sure to start the installer on administrator command prompt. Silent install can only be initiated from the administrator command prompt.
340
344
341
345
#### Uninstallation fails due to the uninstaller being unable to stop the service
342
346
- If There's an option to try again, do try it again
343
347
- If retry from uninstaller doesn't work, cancel the uninstall and stop Azure Monitor Agent service from Services (Desktop Application)
344
348
- Retry uninstall
345
-
346
349
#### Force uninstall manually when uninstaller doesn't work
347
350
- Stop Azure Monitor Agent service. Then try uninstalling again. If it fails, then proceed with the following steps
348
351
- Delete AMA service with "sc delete AzureMonitorAgent" from admin cmd
@@ -351,6 +354,8 @@ Make sure to start the installer on administrator command prompt. Silent install
351
354
- Delete AMA data/logs. They're stored in `C:\Resources\Azure Monitor Agent` by default
352
355
- Open Registry. Check `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure Monitor Agent`. If it exists, delete the key.
353
356
357
+
### Post installation/Operational issues
358
+
Once the agent is installed successfully (i.e. you see the agent service running but don't see data as expected), you can follow standard troubleshooting steps listed here for [Windows VM](./azure-monitor-agent-troubleshoot-windows-vm.md) and [Windows Arc-enabled server](azure-monitor-agent-troubleshoot-windows-arc.md) respectively.
354
359
355
360
## Questions and feedback
356
361
Take this [quick survey](https://forms.microsoft.com/r/CBhWuT1rmM) or share your feedback/questions regarding the client installer.
0 commit comments