No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
My Customer as an internal fleet of Zebra Products linked to this on-premise server and wants to drive Samsung Phones on A14 that should be outside in data connection.What should be exactly the best practice ? Using Samsung Knox enrollment or Knox LME Work Profile and Google profile As he holds many firewalling rules In each case, what connectivity should be preserved, from on premise server to outside, and from outside to inside ?Any registration and DNS needed ?
Hi all, When starting with SOTI MobiControl we made a choice to put the server on-premises.This because, back then, there where only on-premises devices that needed to be managed.All connected either by internal LAN or WiFi. Now, from within the organization, came the question to have a device connected by 4G and not only being used on-premises. Question: What is the best practice? Moving server to DMZ zone? (not preferred) Second DS server in DMZ zone? Setting up FW rules? ... Any advice, best practice approach is welcome. Greetings,Karel.
Hello all, I have the following scenario with a customer. He is using a MobiControl on premise installation, version 15.1.1, in his internal network. Currently every MC part is installed on one main server (Deployment Server, Management Server, SQL DB). He wants to add a second Deployment Server in his DMZ to make the SOTI MC environment externally available. I installed and configured a lot of SOTI MC servers in the past but never added a second Deployment Server to an existing one. The question is, are there any things to keep in mind while installing a second Deployment Server? I am aware of opening ports between the main server and the second server and installing the Deployment Server with the SOTI MC 15.1.1 installation setup on the second server (only with the Deployment Server checked in the setup). Thank you in advance for your answer!
My client has On Premise installation, and i use enrollment URL & their close network to enroll the device to MC. Their device is Honeywell CT50 and i enroll it to A+. one strange thing is, 2 device can't enroll to the MC after i wrote down the enrollment URL in MC apps (while use close network). So i change the network, i use the WiFi, and suddenly it works, the device enroll to MC. It make me confuse since it's on Prem, so i dont think the open network can read the server. is there any particular thing that i need to check? the device going well, nothing happened after the enrollment, but i just want to share it here to prevent some future problem. Thank!
Port 5494 and 443 have been forwarded from the firewall to the server, but the devices fail enrollment (No connection)!? I try to enroll Zebra TC57's. I use Enterprise Agent (and plugin) downloaded from Soti's webpage. In the Admin Utility I have configured Primary Agent address with the public IP address of the firewall. Secondary Agent address is configured with the local IP address of the MobiControl server. Device Management Address holds the FQDN of the firewall. After that the add-devices rule has been created. I download the agent.apk and the mcsetup.ini to the device and install. After that the agent.apk is started. Everything looks OK until the device tries to connect. Probably basic to many of you. I have installed many on-premise systems, but enrollment has always been done via local network. Can someone help !? Thanks Jan
Inquiry: Mobicontrol documentation that are found online is not enough or vagued.“Mobicontrol Administration Utility – Deployment Server” Site Name – can I input a unique sitename? Or it is recommended to use the default? Deployment Server Name – can I input a unique deployment server name? Or it is recommended to use the default? Primary Agent Address and Port Is this the address for communication between device agent and soti server? Should I use FQDN resolvable from internal and external network? Another scenario: Public IP with port forwarded to 5494 – ex: 1.2.3.4:44 Secondary Agent Address and Port Private IP with port 5494 Device Management Address and Port What is the difference between “Primary Agent Address” ? FQDN via port 443 ? Management Service Address and Port Is this the address the Webconsole users should contact to? Is it recommended also to use FQDN? Override Local Management Service Address Disable Deployment Server FQDN/IP and Port FQDN of Deployment Server that is resolvable from internal and external network
Hello. Is it possible to set up MobiControl Cloud as an additional management and deployment server for a local (on Premise) installation? Regards,
Based on the other topic I've read, it is possible to setup an offline instance. We can bypass SOTI Services by sideloading device agents, skins etc. I just want to know what are the features we can't use or things that we can't do between different OS (Android, iOS, Windows, Linux) if we are planning to setup an instance on an offline environment. Thanks
I have an environment that is completely locked down and any requests for public internet access are being denied? How can I improve the performance of MobiControl in a fully offline environment? I'm available to perform registration successfully offline, but access to other SOTI services like the Remote Control skins repo and the central CA are resulting in a relatively hindered experience. Can you sideload the skins into the environment, bypassing the service? Can you get around the certificate related issues during enrollments and check ins at the device level (Android). Another issue that I'm seeing is that the Enrollment rule creation fails to provide me with a local enrollment url. I would expect the enrollment ID to not be generated given it not having access to the central Enrollment service, but shouldn't a local enrollment url be generated?
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points
Highly experienced members with valuable inputs. Should have more than 700 points
Beginners taking the initiative. Should have more than 500 points
