Look up devices
Find devices
Find devices
Finds devices in Workspace ONE UEM. All input fields are optional. The tool always includes the requester’s email as a fallback, so calling it with no inputs returns the requester’s devices. It can return more than one device. A
deviceId or serialNumber lookup is direct and is not limited to the requester’s devices, so it can return any device in your tenant.Tool name: @Find DevicesInput fields:deviceId- the Omnissa device ID. Use it for a precise lookup when more than one device matches.serialNumber- the device serial number.deviceName- the device friendly name. Matches the full name, ignoring case.platform- the device platform, for exampleApple,Android, orWinRT.
deviceId or serialNumber, Ravenna looks up that device directly. Otherwise, Ravenna searches the requester’s devices by email and applies the platform and deviceName filters.Output data:devices- matched devices, each withid,uuid,serialNumber,deviceName,userName,userEmail,platform,model,osVersion,ownership,complianceStatus,enrollmentStatus,lastSeen, andisSupervised.
- Look up a requester’s devices when troubleshooting a hardware or software issue
- Verify compliance and enrollment status before approving an access request
- Find a device’s serial number, model, or OS version for IT support
- Check when a device last checked in with Workspace ONE UEM
When a user reports a device issue, use @Find Devices to look up their devices in Omnissa. If multiple devices come back, ask which one they mean. If the device is not compliant, tell the user before troubleshooting.
@Find Devices is a read-only tool. Use to control how tools run in each rule.Setup
1
Install Omnissa integration
Follow the Omnissa setup guide to connect your Workspace ONE UEM tenant to Ravenna.
2
Configure agent
Open your agent’s settings and add the Omnissa tool under Tools. An admin has to attach each tool before an agent or rule can call it.
3
Create rules
Write that reference the Omnissa tool using @ mentions.
4
Test tools
Test your rules on a real request to verify the tool works as expected.
Best practices
- Start with the requester’s email. Call
@Find Deviceswithout inputs first. AddserialNumberordeviceIdonly when the user has more than one device. - Ask before assuming. When several devices match, have the agent list them and ask the requester to pick one.
- Use compliance as a gate. Check
complianceStatusin access-request rules before approving.
Learn more about configuring agents