An APM bug that has to do with .NET 2.0 shipped with UR3 for System Center Operations Manager 2016. Microsoft continues to work on ultimately solving the issue, but its just not fixed yet.
In an update that essentially uses the old Ace Ventura Pet Detective line, “If I’m not back in five minutes, just wait longer,” the company provides some additional symptoms of the problem and gives some workarounds…
- SCOM 2016 Agent can be replaced with SCOM 2012 R2 Agent, it’s forward-compatible with SCOM 2016 Server and APM feature will continue to work with the older bits
- SCOM 2016 Agent can be reinstalled with NOAPM=1 switch in msiexec.exe setup command line, APM feature will be excluded from setup
Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in San Francisco in 2017!