What happens when the 2X MDM client is not able to connect to the server?

0
Share on FacebookTweet about this on TwitterShare on LinkedInShare on Google+Email this to someonePrint this pagePin on PinterestShare on TumblrBuffer this pageShare on RedditShare on StumbleUpon

There are two scenarios which should be considered:

1. Session time out applies

Wifi/3G/LTE is enabled on the device but cannot connect to the 2X MDM server.

In this case, the 2X MDM client shall attempt to connect to the 2X MDM server over port 587. If port 587 is being blocked by a firewall or internet connectivity is not available, the 2X MDM client shall attempt to reconnect in 2 seconds, and if unsuccessful, double the connect session time out  and continue to increment the session time out until reaching a value of 30 minutes.

2. Session time out does not apply

Wifi/3G/LTE is disabled by the user and further re-enabled.

In this case, the 2X MDM app detects that network has been re-established and instantly attempts to ping the 2X MDM server and re-connect, therefore conserving battery usage.

 

Sean Bianco is the marketing documentalist and technical writer at Parallels. With a bachelor’s degree in Information Technology and Networking and a three year background in software quality assurance testing and usability engineering, Sean is a subject matter expert in mobility and smartphone, app and device management. He is well-versed in developing technical articles and determining market trends. His excellent analytical and problem-solving skills, with emphasis on understanding relationships between technical problems, result in sound and effective business solutions.