SOTI Pulse Logo

Soti Profile not applied

Solved
SD
Steven De Bruyne
Febelco cvba

Good morning,

I'm a soti newbie so hopefully if anybody can help me that would be great.

We're using Soti Mobicontrol Version: 14.3.3.1111 and are working only with Android devices.

We have a profile applied for our samsung SM-A52SF devices (OS version 12).  This profile is applied on 15 of our 16 devices.  Under the configurations tab no Profile is assigned for 1 device.

When I look under the profile I see this profile applied to the group where all 16 devices are located.

Can anybody give me a direction on where to look.  Is there any logging that I can consult.

Regards

Steven

android
2 years ago
SOTI MobiControl
ANSWERS
RC
Raymond Chan Diamond Contributor
2 years ago

Hi Steven,

Based on the MDM API's you reported, your problematic device should have been enrolled in classic Android+ mode (with Samsung ELM OEM specific device agent) while all the other 15 are enrolled in Android-Enterprise device-owner mode (with generic AE device agent).  Your profile should be an AE profile and thus will only be deployed to those 15 devices.  To fix your current problem,  you should delete the device icon of the problematic device from your web-console, perform a device factory-reset, and use either the afw#mobicontrol hashtag or QR-code/NFC approach to enrol the device onto the system again.  You should make sure you use the enrollment ID associated with your Android-Enterprise Add-Devices rule, which should be different from that associated with a classic Android+ Add-devices rule you used in the previous enrollment of this device.

Solution
SD
Steven De Bruyne
2 years ago

 perform a device factory-reset, and use the afw#mobicontrol hashtag did the trick.

RC
Raymond Chan Diamond Contributor
2 years ago

Is the problematic device running the same firmware version/build and device agent version as the other 15?

What about the "supported (MDM) APIs reported in the "Device Details' tab of this device  in the web-console? Are they exactly the same as the other 15 devices?

Is there any problems using any device actions (e.g. lock, disable passcode lock, etc.) on this device?

SD
Steven De Bruyne
2 years ago

Thanks for your reply Raymond.

I did a cross reference.

First column is the device that doesn't receive the profile.

Device Kind:             Samsung ELM  vs      Android Plus
Agent Version:          15.2.2.1020       vs     15.1.3.1071
Android API Level     31                      vs     33
Supported API's SamsungMdmV57, Samsung RC v1, 839 vs     SamsungMdmV57, Samsung RC v1, 839, Work Managed Device

RS
Rafael Schäfer
2 years ago

I'm pretty sure you already checked but is there maybe in the attachement of the profile a filter configured that maybe excludes this device?

SD
Steven De Bruyne
2 years ago

Thanks for the tip.  No Filter is configured that may exclude this device.  Could be helpfull with other deployments.

Similar Discussions