RMM integration
Omnia Manage and SuperOps
Omnia Manage reads your SuperOps clients and their devices and keeps each client’s asset register current from them, with the history of every change on one timeline.
What it brings in
- Devices for every SuperOps client you link to a client in Omnia Manage.
- Make, model, serial number, operating system, processor, memory, storage and last seen.
- The assigned user, where SuperOps has one.
How it behaves
- The RMM is the source for last seen, status and the assigned user. Name, make, model, operating system, processor, memory, storage and platform are filled in from it only when Intune doesn’t already manage the device, and an empty value never clears one.
- Devices are matched within a client by serial number, so a laptop that’s also in Intune or another RMM is one asset, not two.
- A device not seen for the offline threshold is marked inactive and flagged for review, and one removed from the RMM is marked the same way.
- Anything you set by hand, including a status, is never overwritten by a sync.
- A client’s first sync is silent, so connecting a large estate doesn’t send a flood of new-device emails.
Good to know
- Devices with no serial number, such as some virtual machines, are skipped and counted in the sync result.
Questions
Does Omnia Manage replace SuperOps?
No. SuperOps stays your RMM. Omnia Manage reads from it and adds what an RMM doesn’t keep: the history behind each device, refresh budgets, warranty dates, licences and contracts.
Does it write anything back to SuperOps?
No. It reads devices and doesn’t change anything in SuperOps.
What if a device is in both SuperOps and Intune?
It’s one asset, matched on serial number. Intune’s details win where Intune manages the device, and SuperOps still supplies last seen and the assigned user.
Try it free for 14 days
Set up in a couple of minutes, with everything included. Then £79 a month plus VAT during early access.