This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 45%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF8%3C/text%3E%3C/svg%3E)
Is it possible for SCOM 2019 agents to communicate with SCOM 2022 management servers?
When upgrading from SCOM 2019 to SCOM 2022, is it necessary to upgrade the agents simultaneously, or can the agents be upgraded at a later time?
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
Answer accepted by question author
the communication should not be a problem.
kevin holman also wrote a great article about the upgrade from SCOM2019 to 2022:
https://kevinholman.com/2022/09/27/upgrade-from-scom-2019-to-scom-2022-checklist/
i think the "pitfall" is the system-requirement from the new SCOM2022 agent and the dependencies (.NET and powershell minimum versions)
i would update the agents during the migration. the new agent should be compatible with the old SCOM2019-environment, if you have to fallback.
I am not sure of the official guidance but in my experience, this should not be an issue (upgrading the agents before or after migration). Testing is always a good approach. I did see once where 2012 agents appeared to be causing high CPU on DCs when connected to SCOM 2016. There does not appear to be any hard agent version requirements.