Hello Shahjahan Syed Mohd,

Thank you for requesting a response from Soti Support Staff.

When installing MC, please ensure you are meeting the system requirements for the version you are installing.  

For quick reference, I have included a link to our Help File and have changed the version in the top right corner to 15.2 for you, our latest version. 

ihttps://www.soti.net/mc/help/v15.2/en/setup/installing/system_requirements.html?hl=system%2Crequirements

Please confirm you have met these requirements before installing.   If this is not the root of your inquiry please start by telling us more information about your installation.

Regards, 

Hi,

Thanks for your reply.

If we have devices all over Canada, do we have to have a domain to make provision package work?

Hello Shahjahan,

Thank you for your response, It is recommended to have a proper domain name or FQDN for the server where MobiControl is installed. But even if you're using an IP address for the server, please make sure you open ports on the server which is required for devices to communicate.

Following is the Network Ports link -
https://www.soti.net/mc/help/v15.2/en/setup/installing/network_ports.html?hl=network%2Cports

SOTI Services - 
https://www.soti.net/mc/help/v15.2/en/setup/installing/soti_services.html?hl=soti%2Cservices

Please let me know if this helps you.

Regards,

Hi Shahjajan,

Your description of "having devices all over Canada" doesn't have much meaning in revealing your situation.  I am actually very surprised why someone can provide you with any answer when you haven't clearly revealed sufficient details of your case such as

- Are your devices and MobiControl server restricted to closed corporate networks (i.e. have no internet access)  when you said "LOCAL" insallation? Is the network closed 24 hours at all time, or can the devices/server be TEMPORARILY connected to the internet during the provisioning?  OR do you just mean on-premises MobiControl server when you said "LOCAL"?

- What is/are the device platform(s) you are interested in?  What are the device mode e.g.  BYOD/COPE for Android Enterprise devices, supervised/un-supervised and VPP/non-VPP for Apple devices, etc.)

- Do you mean private enterprise app (i.e. .apk for Android, .ipa for Apple, etc.) when you refer to package to be provision?  Or apps or other nature (e.g. web app, or app from  App-store) ?

- What MDM policies will be deployed to your devices in each platform of interest.  (as some features require support from external servers that might need to verify the identity of your MobiControl server)

...

etc.

If you are not too clear about answers to the above, or the answers will vary a lot with time, then my answer would be a "yes" to cater for any unforeseeable use case and for any tightening of security to be introduced by platform owner such as Google/Apple/Microsoft.  After all, adding a dedicated sub-domain for the MDM server to an existing company owned domain virtually cost nothing extra, and the cost of buying a FIXED-DOMAIN (i.e. non wild-card) SSL certificate for such sub-domain from some reputable CA vendors such as Godaddy is very low (should be around USD 150-200 per year on average for some vendors).

If due to your very limited use case,  you can save so little cost for now and use a local or public IP address for your MobiControl server, but then in the future you have to cover more device platform or some MDM policies that need the FQDN and  SSL certificate, your MobiControl server likely need to be reconfigured and some, if not all,  previously enrolled devices likely need to be re-enrolled or even factory reset (depending on the platforms and modes).  The time-/labour-cost of your IT team as well as any consultancy/professional-service charges for making such transition properly will definitely be much much higher than the domain/SSL cost. 

So why not do it right for ANY possible use-cases from day one?  To my corporate/governemental customers in Hong Kong, the logical answer to your question is obvious and a no-brainer.