Share via

Install AMA on Azure arc enable servers not working

lalajee 1,826 Reputation points
2024-09-04T10:04:03.3+00:00

Hi,

I'm try to install/setup AMA on azure arc enable servers but it mailing to start MonAgentManager.exe after 480 tries

Our Config

  • Gateway server (All firewall ports are allowed)
  • All our Azure Arc server which have AMA agent install should be talking to this gateway server to send all logs to azure

Done following

  • Install Azure Arc on all server which will required AMA
  • In Azure Arc under server -> Extensions I can see "AzureMonitorWindowsAgent" Succeeded
  • In Data collection Rules -> create new rule and server is showing under this rule
  • Link all policy to this azure arc enable servers
  • On-prem server I can see "C:\Resources" & "C:\Packages\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent\1.29.0.0"

Error

  • On ama server I dont see "C:\Resources\Directory\AMADataStore\mcs\mcsconfig.latest.xml"
  • On ama server MonAgentCore.exe process is not running

User's image

User's image

Question:

  • For Proxyaddress which address is use Gateway server address or proxy (All of the logs are transfer from gateway server)
  • How do you change proxy address if I need to?
Azure Monitor
Azure Monitor

An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.

Azure Arc
Azure Arc

A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amira Bedhiafi 41,386 Reputation points MVP Volunteer Moderator
    2026-04-23T17:27:09.4433333+00:00

    Hello Lalajee !

    Thank you for posting on MS Learn Q&A.

    I can see in your screenshot that AMA is clearly reading the proxyAddress value, so the setting is being passed into the agent.

    If that address is a standard corporate forward proxy, then yes, proxyAddress should point to that proxy.

    If that address is a Log Analytics Gateway / OMS Gateway server, then that is likely the problem. Azure Arc-enabled servers do not support Log Analytics Gateway as the proxy path for Arc connectivity and MS Gateway is not supported with Azure Arc enabled servers for AMA proxy connectivity scenarios. https://learn.microsoft.com/en-us/azure/azure-arc/servers/network-requirements

    In your case AMA cannot successfully retrieve its configuration from Azure Monitor Configuration Service through the current network path. Wheb C:\Resources\Directory\AMADataStore\mcs\mcsconfig.latest.xml is missing on an Arc enabled server, check DCR association and connectivity to AMCS. https://learn.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-troubleshoot-windows-arc

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.