JDisc Cloud Discovery for Mobile Device Management: Discover SOTI Devices Easily

Mobile Device Management is no longer a luxury in today’s enterprise landscape, it’s a necessity. Managing mobile and remote devices effectively is critical for security, compliance, and visibility. Platforms like  SOTI MobiControl have become essential in helping IT teams control Android and Windows endpoints across distributed environments. However, there’s often a missing piece: how do you integrate this wealth of mobile device management data into your broader IT asset inventory?

That’s why we’re excited to bring native support for SOTI MobiControl within our Cloud Discovery module in JDisc Discovery!

With this new feature, JDisc bridges the gap between Mobile Device Management and IT asset discovery, providing seamless insight into your mobile infrastructure directly within your central inventory database.

📱 Why SOTI Mobile Device Management Discovery in JDisc Matters

In addition, SOTI MobiControl helps IT teams manage Android and Windows devices across complex deployments (iOS may be partially supported but hasn’t been validated yet). With our integration:

• You no longer need to maintain a separate asset source for mobile data.
• Devices enrolled in SOTI now appear alongside desktops, servers, printers, and cloud instances.
• You can track compliance, hardware details, and connectivity—all in one place, automatically discovered.

📁 How Mobile Device Management Groups Appear in JDisc

JDisc mirrors the Device Groups structure from SOTI:

• JDisc preserves parent and child groups during discovery.
• It also maps device assignments directly from SOTI.

This structure helps you retain context about how devices are grouped and managed inside SOTI, making navigation and reporting more intuitive.

📱 Mobile Device Management Inventory: What JDisc Discovers

Each enrolled device in SOTI is reflected in JDisc as a complete inventory object. For each device, we fetch:

• Device type and model (e.g., Samsung Galaxy Tab Active, Zebra handhelds)
• OS version and build
• Serial numbers, IMEI, and phone numbers
• Hardware details such as memory and SIM information
• Compliance state and security status

This lets you enrich your inventory with valuable data from your mobile fleet, without manual exports or API coding.

🔧 How to Get Started

Integrating SOTI into JDisc is straightforward, but some setup is required on both sides—in JDisc and inside your SOTI environment.

📌 Prerequisites

First, ensure that your organization is using either:

• A web-hosted (cloud) version of SOTI MobiControl, or
• A locally installed (on-premises) instance.

JDisc supports both options, but it’s important that your SOTI server is reachable by the JDisc Discovery system, either over the internet (for cloud setups) or within your internal network (for local setups).

Next, you’ll need to create a dedicated API user in your SOTI MobiControl system with read-only permissions to expose device and group data. If you’re unsure how to do this, there is a short tutorial video (minutes 7:35-9:00) that walks you through the setup process step by step.

🔄 JDisc Configuration Steps

1. Go to: Discovery → Configuration → Cloud.
2. Open the SOTI tab.
3. Click “Add SOTI Server” and fill in the connection details:
   • For cloud/web-based SOTI installations:
     • In the Server Name field, enter the base URL of your SOTI environment. For example:
       a00XXXXX.mobicontrol.cloud
       (The full URL used internally by SOTI might look like https://a00XXXXX.mobicontrol.cloud/MobiControl/WebConsole, but for JDisc, the base domain is sufficient.)
     • Provide the Username, Password, Client ID, and Client Secret associated with the API user.
   • For local/on-premise SOTI installations:
     • The Server Name can be any label of your choice—it does not affect the connection.
     • You must correctly specify the Server Address (FQDN or IP) and the Server Port.
       • If your SOTI server uses HTTPS on port 443 (the default), simply leave the port as-is.
4. Save the configuration.

🚀 Running the Discovery

Once your SOTI server is configured, you’ll need to trigger a Cloud Discovery Job (not a traditional IP/network scan). This will initiate API communication, allowing JDisc to:

• Retrieve device group structures
• Import all enrolled Android and Windows devices
• Populate your central IT inventory with detailed mobile asset data

To start the discovery process, run a Cloud Discovery Job (not a standard network scan). This ensures the SOTI integration is properly queried, and devices are synchronized into your inventory.

🤝 Why SOTI Mobile Device Management Matters

With mobile endpoints playing a central role in modern IT, integrating SOTI MobiControl with JDisc provides:

• Unified visibility: Mobile and traditional devices on the same pane of glass.
• Better compliance: Track security posture and detect policy gaps across platforms.
• Smarter reporting: Correlate mobile data with licensing, lifecycle, and ownership.

If you’re already using JDisc Discovery and SOTI, this is the perfect time to connect the dots. And if you haven’t yet explored our other integrations—like AWS, Azure, or VMware—check out our Cloud Discovery modules to expand your visibility further.

Stay secure, stay informed,
Raphael