Integration
OPSI in IDA: software deployment and inventory on the ticket
OPSI distributes software and knows every managed client. IDA brings that view into the service desk: which client belongs to which customer, what is installed on it - and what has to disappear again when a device leaves.
What IDA reads from OPSI
- Managed clients with their OPSI ID and domain
- Installed and assigned software packages
- Hardware inventory of the clients
- Status of the most recent actions
What IDA does with it
- Clients appear at the right customer - matched by subnet and domain, not by device name
- The ticket shows the device with its software, without a detour into the OPSI web interface
- Device offboarding: a device can be removed from OPSI and the other connected systems in one pass
Who it is for
IT service providers deploying with OPSI who do not want to maintain inventory and tickets separately.
Setup: Store a service account for the OPSI server and assign customers by subnet or domain - the sync then runs on its own.
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.
Vendor website: OPSI. OPSI is a trademark of its respective owner; IDA connects to the system technically, which implies no partnership.
Related
- OCS Inventory - Inventory & deployment
- Device offboarding - Processes
Questions about the OPSI integration
Can IDA deploy software through OPSI?
IDA reads the estate and shows it in the context of customer and ticket. Deployment itself stays in OPSI - IDA is the bracket, not the replacement.
What happens when a device is retired?
Device offboarding removes it across systems: OPSI or OCS together with the backup, security and MDM connections, where they are active. No orphaned object stays behind for you to keep paying for.
Everything in one interface - for you too
30 days free, no payment details. Every integration is included at no extra cost.