Cross-system process
Device offboarding: one device, every system, one pass
A device is retired - and stays behind in five systems: the inventory, the backup, the endpoint protection, the MDM, the directory. IDA clears it in one pass and records what was actually removed.
What IDA reads from Device offboarding
- The device in every connected system
- Status per system
What IDA does with it
- One process instead of five portal rounds
- A record of what was removed and what was not - instead of silent partial success
- No orphaned objects you keep paying licence fees for
Who it is for
Anyone who retires devices regularly - and does not want to pay for the ones that never got retired in somebody elses portal.
Setup: Uses whichever systems are active for you: inventory through OPSI or OCS, plus backup, endpoint protection and MDM where connected.
Every integration in IDA has its own switch. Turn it off and it disappears completely - including the columns, filters and reports that belong to it. You only see what you actually use.
Related
- OPSI - Inventory & deployment
- OCS Inventory - Inventory & deployment
- Acronis Cyber Protect - Security & backup
- Bitdefender GravityZone - Security & backup
Questions about the Device offboarding integration
What happens if one system is unreachable?
The process reports it. A partial success is logged as a partial success and not presented as done.
Everything in one interface - for you too
30 days free, no payment details. Every integration is included at no extra cost.