The NinjaRMMAgent relies on WMI calls for all of its reporting. As such, if there are existing WMI problems on a machine (which is well-documented as being an issue within the Microsoft community), NinjaOne will highlight this problem.
- Ninja is a symptom of WMI issues — not the cause.
- Performance counters can often be the culprit. Check out this Microsoft documentation on rebuilding performance counter library values.
The WMI Performance Adapter service not running, or running under a user rather than as System, can also cause issues. Windows provides information on setting up WMI activity logging here.
- Additionally, you should run sfc /scannow to eliminate corruption as a possible cause.
Other helpful tool: