What is the version and build number of your device agent?

Did you get  error message  saying that there is no connection? Or error message  that "only supports devices running OS 6.0 or below" ?  You shouldn't have both for the same agent if the connection was consistently stable.  Please clarify.

Hi Tom,  

I will assume you not using the latest agent 13.5, perhaps you are.  Can you try to navigate to our site soti.net/OEM and download the latest agent for Samsung devices to see if this helps to get the devices enrolled.   

Interesting that you can side load the agent on the devices but cannot load the agent from the Playstore.  Where are you getting the agent that you place on the devices from in the first place?

Either way knowing the agent versions you are experiencing this with and perhaps a screenshot will help with providing you a resolution to this. 

Hi,

Thank you for your reply. I have attached a screen shot of the 4 apps we can download and try in the Playstore, none of these work and will not enroll the devices. When we try using this method we either get an invalid enrollment ID, or the Connection to Server times out. The enrollment is definitely valid as it works when we manually download the agent. 

We download this from the rules tab, as attached. Any enrollment ID works fine using this method. We download the APK agent which is named by default as SamsungElmMobiControl1410.apk

I hope that information is of some use, is 1410 not the latest agent?

https://ibb.co/mw22On

https://ibb.co/mD0YUS

With your updated post, I begin to understand what your problem is.

The four apk's downloadable from Google Play store are device agent "installer", rather than the real device agents. The real agent is always subsequently downloaded from your deployment server to the device.   If you have chosen your platform (between Generic Andrlod, Android-Plus and Android-Enterprise) for your device, then the agent to be used is well defined.  I assume you are using Android+ for your Samsung device, so you only need to try the Samsung agent installer.  Unfortunately the Samsung agent installer currently on Google Play store supports up to Android 6.x devices.  So you cannot use this enrollment approach for your Android 7.x devices.  You don't need to waste time to try any more.

You have at least the following options for your v7.x (but not 8.x, which requires some additional adjustments for each case) Samsung devices:

1.  Wait for Soti to release another Samsung agent installer that supports Android 7.x/8.x devices on the Google Play Store.  (But I don't know if there will be any, or when it will be ready if there is one).

2. Send the real Samsung device agent apk file obtained from the add-devices rule pop-up menu option (as in your screenshot https://ibb.co/mw22On)  onto the device by whatever means available, use a file manager to run this apk and enter your enrollment ID to enroll.  (If you also send the .ini file associated with the add-devices rule to the same directory as the apk file on the device before running the apk, there is no need to input the enrollment ID.)

3. Start any web browser on your 7.x devices, and browse to the "Enrollment URL" as defined in the summary tab in your add-devices rule, choose the Samsung device agent item and click the download button.  Use a file manager to run the downloaded apk and enter your enrollment ID to enroll.

Hi Raymond,

Thank you very much for your response.

Highly frustrating regarding point number 1, this is by far the easiest method for us so to not be able to download the app straight from the playstore would be highly beneficial.

We may have to go with number 2, as number 3 doesn't appear to work for us either. We just get File not found no matter which enrollment URL we try. Could be a fault on our end but I can't see anything obviously wrong.

Thanks.

I've never got a "File not found" error for Samsung device enrollment in hundreds of MobiControl server instances in the last five years. 

There's another post recently talking about no device agents after installation of latestv 13.4.  Although I haven't got similar problem in our v13.4 server of the same version/build number, I can rule out possibility of hidden problem in your server installation.   I believe you may consider upgrading your server to the latest v14.1.2, downloadable at

  http://download.soti.net/MobiControl/MobiControl1412Setup_1937_release.exe

Give it a go, and see if the installation program can get things right.  Besides, there are many fixes and new features for this patch.  I have it installed for over 3 weeks and so far haven't found any noticeable issues.

Good luck.

Hi Raymond,

Thank you again for your input. I wasn't aware there was a newer release available, we are running 14.1.0.1152 so I will download the installer you have kindly provided the link for an update our system. Then I will see how we get on with our issues then.

Thanks again,

Tom.