What are the version numbers and detail OEM versions/builds of the two devices?

Have you tried using a different agent version/build for S10e?

Do you have any feature-control, kiosk mode and application-run-control  policies via profile/scripts  applied to the devices?  If so, have you tested your S10e with those policies revoked?

Have you downloaded Mobicontrol device log file from your problematic S10e to see if there are any related warning/error log entries? 

Raymond,

You shouldn't be working this late.... 

S10E: 

What deploy rule you is using? Legacy or AE?

AE.

Hi Jason,

As I am currently based in Hong Kong, it was morning 5 hours ago when I sent my last post in this thread.   So, it's not late for me.  Also, as I am not paid a single penny by my company to post anything here,  I should in principle be only contributing to this forum outside my normal working hours.

So now, I know that both your devices are using AE device agent v14.4.3 and their OEM versions.   But you haven't provided information related to by other three questions, which I cut and paste below:

1. Have you tried using a different agent version/build for S10e?

2. Do you have any feature-control, kiosk mode and application-run-control  policies via profile/scripts  applied to the devices?  If so, have you tested your S10e with those policies revoked?

3. Have you downloaded Mobicontrol device log file from your problematic S10e to see if there are any related warning/error log entries? 

For (1), just in case you are not aware of, you can use Soti Stage programmer app downloadable for free from Google Play Store to enroll your AE device with any MobiControl device agent version of your choice.

Good Evening Raymond, 

I meant no disrespect for my comment of working so late. I just know in this field I have found myself working much later and earlier than normal. So it was meant more of a laugh than anything else. You do great work here on this site. I lurk a lot and just read what other people are seeing. And you try to assist others as much as possible. The other might kick me out if you changed up the times you were on.

So with that said lets move on. I am sorry I had thought I covered the 3 things but upon reading my post I see where in fact i did not.

1. Have you tried using a different agent version/build for S10e?

- We have various Units running various Builds: 14.1.4.1010 is the lowest and the highest is the current build.

2. Do you have any feature-control, kiosk mode and application-run-control  policies via profile/scripts  applied to the devices?  If so, have you tested your S10e with those policies revoked?

- No Kiosk mode devices - Yes to feature control and application run control policies. (Not all devices have the same policies as it based upon your position and department you are in) I have even taken on unit like I was mentioning in my last post and enrolled it in what I like to call my clean room (Group) Only policy assigned to said device is Authentication as this is a must across the company as well as minimal feature control. (Only have disable factory reset, disable smart boot, disable installation from unknown sources, and disable doze mode) Application deployment is all done thru Managed Playstore.

3. Have you downloaded Mobicontrol device log file from your problematic S10e to see if there are any related warning/error log entries?

One of my employees did and sent to me but I have not reviewed them as when I was typing this post it got pushed to the back of my mind as other fires I have been trying to put out all day were burning. I will review it today

Thanks

Jason

Hi Jason,

Are you kidding me?  I don't feel a bit of disrespect.  On the contrary, I felt like the comment is from my love ones, asking me why I am working so late, and then kicking my ass to hit my bed.     Regarding working hours on a global scale, even I myself don't know which hours I will be active on this forum in the near future,  as I am looking forward to leaving my hometown again and work in another time-zone.

Returning to your problem, it seems like the problem is not related to particular device agent based on your input for (1).  Your descriptions in (2) also rule out most problem related to kiosk or applicaton-run-control.  I thus have to guess that there might be something unusual with your S10e firmware and/or default options in your AE feature-control profile.  Without any log file to look into, I need to make an educated guess on the culprit.

You are lucky that your problematic device is a Samsung device.  You can simply try sending the following script to your device to see if your problem can be fixed:

  writesecureprofstring DeviceFeature DisableSettings 0
  apply featurecontrol

Good luck.

Raymond,

Best of luck to where you are heading. Sounds like you are really looking forward to the change.

Well so this saga gets better. My 4 examples we had last night. When I reached out to them this morning (Because I wanted to try that script) 3 of the 4 said hey, it works this morning. So then I was like let me enroll same device that failed on me into that group. And nope mine worked to. So I tried that script on the 1 that said they had the problem and it was not able to fix the issue. 

Very odd that "they just started working. Still banging my head on this one.