Overview
You may see a notification indicating that:
Conflicting assignments detected across MDMs
This means the same asset exists in more than one connected MDM, but each system reports a different assigned user.
Since Dots cannot determine which assignment is correct, the asset remains unassigned to prevent incorrect ownership tracking.
What Does This Mean?
These assets:
Exist in multiple connected MDM integrations
Are assigned to different users in each MDM
Cannot be automatically reconciled by Dots
To maintain data accuracy and audit integrity, Dots does not prioritize one system over another by default.
As a result, the asset remains unassigned until the conflict is resolved.
Why This Happens?
This typically occurs in environments where:
Multiple MDM systems are active (e.g., during migration or regional management)
Devices are enrolled in more than one MDM
Assignment updates were made in only one system
Common causes include:
1. Conflicting Assignment Data Between MDMs
Each MDM reports a different assigned employee for the same serial number.
2. Incomplete or Delayed Synchronization
One system was updated, but the other still reflects outdated information.
3. MDM Migration in Progress
During transitions between MDM platforms, devices may temporarily exist in both systems with inconsistent assignments.
How to Resolve Conflicting Assignments
To resolve the issue, you’ll need to manually align the assignment data across systems.
Step 1: Identify the Asset
Locate the asset in Dots using the serial number
Note which MDM integrations are reporting the device
Step 2: Review Assignment in Each MDM
Log into each connected MDM and:
Search for the device by serial number
Confirm the assigned user in each system
Document which system contains the correct and most up-to-date assignment.
Step 3: Correct the Inconsistent MDM(s)
Update the assignment in the system(s) that contain incorrect data so that:
All MDMs reflect the same assigned user
The email matches the employee record in Dots
⚠️ Ensure email formatting is identical across systems to prevent additional mismatches.
Step 4: Trigger Synchronization
After correcting the assignment:
Trigger a manual sync (if available), or
Wait for the next automatic sync cycle
Once all connected MDMs report consistent data, Dots will automatically assign the asset.
Best Practices to Prevent Future Conflicts
Avoid managing the same device in multiple active MDMs long-term
During MDM migrations, define a clear source of truth
Ensure assignment updates are completed in all relevant systems
Regularly audit devices enrolled in more than one MDM