I see.  You are actually using Android Enterprise (Andorid-For-Work) device agent for your Samsung hardware.

It should work OK if your Samsung device is properly configured to managed-device mode for Android-Enterprise, and your  server has been configured with proper Android-Enterprise policies/rules.  

Did you perform factory reset for your Samsung device to get it in managed-device mode?

Your created profiles were probably for Android+ platform, and therefore would't be deployed to the device.  You have to create  new profiles for "Android Enterprise" in v14.x ("Android-For-Work" in v13.x)  platform to be targeted to your Samsung device using the current device agent. 

It's a pity I could not successfully insert an image I captured a moment ago to show you where to choose the platform.  I understand now why you said it's simpler to type the information rather than including the screenshot.  It had been easy and straightforward to do (just show a file-browser prompt for forum user to select the local image file to be uploaded) before Soti changed this forum user-interface two weeks ago.  But now, what the hell should anyone input in the new "source" field to get an image included!

Maybe convert the devices to the ELM version? You should be able to do so from the Folder structure, although this view has certainly changed in 14.x

Thanks for the reply,

However I don't appear to have that option available, I'm assuming because its not the specific Samsung Agent but the standard android+ one that the app installs.

You won't see that option if your device agent is already a Samsung ELM device agent.   You can confirm by tapping on the Mobicontrol device agent, and check the version reported in the "Device Configuration" tab.  There should be a "(ELM)" suffix  at the end if it is an ELM device agent.

You mentioned that you could remote-control, wipe, etc, but profile could not be deployed.   What are the status of the profile(s) reported in your web console or on the device agent "Device Configuation->Profiles" tab?  Did you wait for hours or even days and the profile still didin't get deployed?   What version/build number was your server before you upgraded it to v14.0?  Were your Deployment Server, Management Server and SQL server all installed in the same MS-Server host?

HI,

Yes its definitely not the Samsung or ELM one

• Device Kind = Android Plus
• Agent Version - 13.5.1.110

Yes the device is communicating with SOTI, shows connected and I appear to be able to so most things other than assign a profile, If I assign a profile to the device is simply does nothing. The configurations section shows no profiles at all. I applied it yesterday and nothing has happened as yet.

We moved from version 13.2.3193 to version 14. Our console is fully in the cloud version so SOTI did all of the upgrade. However this did exactly the same on version 13.2, but we believed the issue was related to the app installing agent 13.5 and because we were on V13.2. on our console that was the issue.

In general, version 13.5 device agents can talk properly to v13.2 server, and should not be a problem.

Could you post a screenshot of the Active MDM API reported in the Device Agents's "Device Configuration" tab ?

What Samsung model is your device?  And what Android firmware version?

Sure,

Easier if I just type it

• Agent Version - 13.5.0 Build 1110
• Active MDM API - Work managed device, RC1 (1.4.2.362)
• Agent Mode - User

Hi Joe, 

Which section did you choose when configuring your profile?  If your device is enrolled as Enterprise (Formerly Android for work) it should be an Enterprise (Formerly Android for work) profile also.

Hope this helps!

Hi,

Thanks for all the help so far with this you've been very helpful. I've created a new profile using "Android Enterprise" which seems to have got me a bit further and added a package to profile which successfully installed on the device when I assigned the new profile so were making progress here. :)

However we make use of the lockdown screens on our devices which appears to be called "Kiosk Mode" when creating an enterprise profile (not sure why its named differently). The lock down screen doesn't seem to apply when I assign the profile however, any thoughts?

HI,

Profile needed and authentication profile which then kicked in the lock screen :)

As of now I think that's me sorted and can now get on with provisioning 200+ phones a lot quicker.

first time I've used this support forum and must say its been very helpful. In particular thanks Raymond you've been a great help here.

Hi Joe,

It's great to hear that you can deploy your profiles now.

Kiosk mode payload of Android-Enterprise profile should work just the same as lockdown payload in previous Android+ platform, though our own tests on the former so far have not been as extensive as for the latter.    If you still can't get  your intended lockdown menu on your devices, you can start a new discussion topic and give more details and/or screenshots of the problem.   I would also like to know if anything is overlooked in my previous tests.