Offline Android device not enrolling - Invalid URL

Offline Android device not enrolling - Invalid URL

Hello,

I have a few devices that i can enroll as a work profile but not as an enterprise device. We require the enterprise solution so we can remote control the devices if and when they need some troubleshooting.

Our MobiControl server sits on xxx.xxx.53.53 and the Zebra MC93s are situated on a closed WiFi Network that gives the device xxx.xxx.55.124

Both IPs are reachable from both sides. I can ping the server from the Android device and i can ping the device from the 53 subnet.

 

The WiFi that the scanners are has no internet connection and is an internal network. I asked the question before if anyone has come across being unable to enroll devices and i was told that there should be no issue enrolling these scanners on a network that is on our own WAN with no internet connection. We are unable to give the devices internet connection due to security policies in the warehouses we are located.

Our enrollment server address that the rule generates is xxx.xxx.53.108 but when i try the server address on the enrollment part of the MobiControl app on the device, it throws a "Invalid URL" prompt. When using the Enrollment ID i just get an "Enrollment Failed" message.

 

Does anyone have any pointers i can try?

6 Answers

Order By:   Standard | Newest | Votes
JCMOD@SOTI | posted this 27 July 2020

Hi Adam,

 

Sounds like a few issues here, ensure the DMA Address is accessible to the devices, regardless if they're internal or external.

 

Regarding the Add Device Rule, if you right-click it within MobiControl Web Console, then press "Update Enrollment Profile". Does it reflect "Enrollment ID updated" in the logs? If it errors, look into authorizing SOTI Services on the server. Reference https://www.soti.net/mc/help/v14.3/en/setup/installing/soti_services.html for that.

 

Hope this helps, let me know how it goes?

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0
Adam | posted this 27 July 2020

Hi JC,

Can confirm the DMA is contactable from the devices.

When updating the Enrollment Profile, it does indeed error: "The server could not complete your request. An internal error occured."

Taking a look at the reference now.

Thanks.

  • 0
  • 0
Raymond Chan | posted this 28 July 2020

Have you successfully enrolled the same device into work-profile mode within the same closed Wifi network?

  

Did you use Managed Google Play account, Managed Google Account or skip either of them completely in your add-devices rule?

 

  • 0
  • 0
Adam | posted this 29 July 2020

We can enroll the devices on the closed network as work profiles fine. No issues with that.

This will allow us to remote VIEW the devices with no problems. This is not what we need. We need to be able to remote CONTROL the devices. To which it need to be installed as an Enterprise device.

We have also used all 3 options regarding the accounts. No luck.

 

  • 0
  • 0
JCMOD@SOTI | posted this 29 July 2020

You mentioned the enrollment URL reflects xxx.xxx.53.108 and your MC server sits on xxx.xxx.53.53. Is the 108 your public-facing & internal-facing side, is this also the primary agent address? Does the enrollment URL load on the same network of the device you're trying to enroll via AE? Feel free to raise a Support Case via support.eu@soti.net and send me the case # via my SOTI Central profile and we can jump on a GoToMeeting session and figure it out then and there.

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0
Adam | posted this 30 July 2020

so the server where the admin utility is located is sat on 53.53

Primary agent address is 53.53


Device Management Address is 53.108

Management Service address is 53.108

Deployment server FQDN/IP is 53.53

 

Both are not internet facing as it is a closed network. Our argument is that we shouldn't need to have any type of internet connection because it shouldn't need to go out to the internet to enroll on our own MobiControl server.

 

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback