A SCOM user can currently use SCOM agent or Log Analytics agent (aka MMA) to monitor Virtual machines & send data to SCOM servers and optionally, send the data to Azure Log Analytics workspace. However, Microsoft has notified all Log Analytics Agent users about its deprecation roadmap and has recommended to migrate to Azure Monitor Agent as documented at Migrate from legacy agents to Azure Monitor Agent. As the deprecation data of August 31, 2024, is nearing, please refer to the table below for high level recommendations.
|Timeline –>||Currently||Until Aug2024(recommendation)||After Aug2024(Recommended agent)|
|Send data to SCOM Servers||SCOM Agent||SCOM Agent||SCOM Agent|
|MMA||Migrate to SCOM Agent|
|Send data to LA workspace||SCOM Agent||Migrate to AMA||AMA|
Lastly, the following FAQs should help you with concerns on the validity & supportability of SCOM agents. Feel free to post your queries in the comments section, if any.
- What are the current supported versions of SCOM? How can I distinguish if I am using SCOM agent or Log Analytics agent?
All the supported versions of SCOM Agents are listed in the below articles. Any version that is not listed here is not supported for communication with SCOM servers. For quick reference, agent versions 10.20.x are Log Analytics build. SCOM 2016, 2019 and 2022 agent builds are 8.0.x, 10.19.x and 10.22.x respectively. Refer to the table for the full list of version numbers.
SCOM 2022 Agent version
SCOM 2019 Agent version
SCOM 2016 Agent version
- How do I check the version of a SCOM agent?
Refer to below steps to identify the version of an agent. Cross check the version to the list displayed in Agent version articles.
1. On SCOM Operations Console > Administration > Agent Managed > Check the “Version” Colum.
2. On a SCOM Management Server, run the below in PowerShell
Get-SCOMAgent –name server.domain.com | select displayname,version
3. On the specified agent machine > Control Panel > Microsoft Monitoring Agent > Properties > “Product Version” property.
4. Run the below in PowerShell on the agent-managed machine:
$Agent = get-itemproperty -path “HKLM:SOFTWAREMicrosoftMicrosoft Operations Manager3.0Setup";$Agent.CurrentVersion
- When will Log Analytics Agent go out of support?
Aug 31, 2024. More information at We're retiring the Log Analytics agent in Azure Monitor on 31 August 2024 | Azure updates | Microsoft Azure
- Will SCOM agent be supported when Log Analytics agent go out of support?
Yes, the lifecycle of SCOM agent is dependent on the lifecycle of SCOM software. The agent is supported as defined in Microsoft lifecycle policy. Refer to System Center 2022 Operations Manager and System Center 2019 Operations Manager to view the Support end dates.
- Can I use SCOM agent to send data to Azure Log Analytics workspace?
You can use SCOM agent to send data to LA workspace until Aug 31, 2024. After that date, the scenario will be unsupported, and you should use Azure Monitor Agent (AMA) to send data to Log Analytics workspace. You can continue to use the SCOM agent to send data to SCOM servers.
- Can I use SCOM agent to send data to SCOM server?
Yes – There is no change to the core functionality of SCOM Agent.
- What should I do to send data to Azure Log Analytics workspace?
You can install Azure Monitoring Agent side-by-side SCOM agent on the desired machine. SCOM agents will send data to SCOM servers while AMA will send data to Azure.
- Should I migrate from Log Analytics agent to SCOM agent? If yes, how?
To send monitoring data to SCOM server, you should use supported agent i.e., SCOM agents (refer to Q#1). To migrate from Log Analytics Agent to SCOM Agent, follow below steps.
- If you are using SCOM 2022 application, use SCOM2022 installer EXE to install SCOM agent on the same machine and then upgrade to latest Update Rollup. This is in-place upgrade.
- If you are using SCOM 2019 application, you uninstall Log Analytics agent, use SCOM2019 installer EXE to install SCOM agent on the same machine and then upgrade to latest Update Rollup.