Deployment Server

The Deployment Server section of the SOTI MobiControl Administration Utility displays the connection settings of the deployment server.

Note: Exercise caution whenever modifying any connection settings to ensure the uninterrupted connection of your SOTI MobiControl system.


Site Name	Displays the site name of the SOTI MobiControl deployment.
Deployment Server Name	Displays the deployment server(s) name.
Primary Agent Address and Port	Displays the primary address (IP or FQDN format) for device connectivity as well as its associated port. It is recommended that you specify a DNS resolvable hostname instead of a static IP as a DNS resolvable hostname is less likely to change. Connecting through a Proxy Note: Supported for Windows Mobile/CE and Windows Desktop Classic devices only. Other device types will continue to connect directly to the SOTI MobiControl deployment server. If your devices require proxy access for the device agents to connect to the SOTI MobiControl deployment server, use the following settings: If using a web proxy: http://`Username`:`Password`@`ProxyServer`:`ProxyPort`/`DeploymentServerAddress`:`DeploymentServerPort` If using a socks firewall/proxy, use one of: socks://`Username`:`Password`@`ProxyServer`:`ProxyPort`/`DeploymentServerAddress`:`DeploymentServerPort` socks://`ProxyServer`:`ProxyPort`/`DeploymentServerAddress`:`DeploymentServerPort`
Secondary Agent Address and Port	Displays the secondary address for device connectivity in IP or FQDN format as well as its associated port. See Primary Agent Address and Port for more information.
Device Management Address and Port	Displays the external FQDN address and associated port that iOS and Android devices use for connectivity. Note: Ensure the port number for the Device Management Address matches the port number for The Deployment Server will listen for incoming HTTPS request on in the Ports section.
Management Service Address and Port	Displays the management service address in FQDN as well as its associated port number.
Override Local Management Service Address	When enabled, the management service address uses the FQDN and port specified underneath this checkbox when it builds requests. Use this option in deployments with multiple management services, where most of the management services use a default load-balanced address while the single one not behind the load balancer uses the management service override with its own FQDN to ensure all requests point back to itself. Note: This option is only available in environments where the management service is installed on the same computer as SOTI MobiControl Administration Utility.
Device Agent Access Available	Indicates if network traffic to the indicated primary and secondary IP or FQDN and port are functional.
Device Management Access Available	Indicates if network traffic to the indicated external FQDN and HTTPS port are functional.
Management Service Access Available	Indicates if network traffic to the indicated management service address and port are functional.

Management Console Connection Settings

These settings determine the connection between the deployment server and the management service.


Deployment Server FQDN/IP and Port	Displays the address (in IP or FQDN format) used by the management service to connect to the deployment server.
Alternate Deployment Server FQDN/IP and Port	Displays an alternative address (in IP or FQDN format) used by the management service to connect to the deployment server.

Device Connection Sensitivity

These settings determine a device connection sensitivity.


Send Test Message to Devices Every	Determines how often test messages are sent to devices from the deployment server.
Maximum Time Waiting for Reply	Dictates how long the deployment server waits for a reply from the device after a test message is sent.

Advanced Server Configuration

These settings allow you to perform advanced configuration on your server.


Minimum Threads	Sets the minimum number of service threads. This value is twice the number of processor cores available on the deployment server.
Optimum Threads	Sets the maximum number of service threads. This value is 16 times the number of processor cores available on the deployment server.
Maximum Burst Threads	Sets the maximum number of service threads based on Server Configurations. This value is 256 times the number of processor cores available on the deployment server.
Check for Rule Changes Every	Determines how often the deployment server should check the database for changes to rules.
Check for Device Schedule Changes Every	Determines how often the deployment server should check the database for changes to device schedules.