Client Configuration

Here you can perform the following configurations on your Android device:

Edit

Out of Compliance Time



The user response timeout limit after which the enforcement action is applied.



Enforcement action after compliance timeout



Enforcement action when a user doesn’t perfom actions that leads to a compliant device status



Data Collection Frequency



Frequency with which device/GPS-information is to be collected



Device Heartbeat Frequency



Interval in which the device should contact the AppTec360 Server


Min. 1 minute


Max. 24 hours



Enable Location Updates



If activated, the device sends location updates to the AppTec360 Server



Location Update Time



Determines in what time intervals the device sends location updates to AppTec360



Use Google Location Accuracy for Location Update



If activated, the network location will be used for location updates (if this was deactivated under “Restrictions”, then this setting will not affect anything)



Use GPS Location for Location Update



If activated, the GPS will be used for location updates



Allow Mock (Fake) Locations



Allows the forging of location information via third party apps



Lost Connection Action



If enabled, you can specify an action for the case that a device doesn’t get a connection to the MDM server in the heartbeat interval. For example, if the device has a heartbeat time of 5 minutes, it connects to the server at 10:35 AM. After that the device leaves the Wi-Fi range. The next heartbeat at 10:40 AM will fail, and the specified action will be executed.



Action



The action that is to be taken, as soon as a device becomes non-compliant.



  • Lock Device = lock device

  • Wipe Device = device will be restored to factory settings

  • Wipe Device & SD Card = device will be restored to factory settings and SD Card storage will be deleted



Threshold



You can specifiy a threshhold of failed Heartbeats which are necessary to trigger the specified action.


Edit

Policy Enforcement Mode



Default:



Users will be prompted periodically to execute outstanding actions



Lazy Policy Enforcement:



Users will never be prompted to execute outstanding actions. All open action will be shown in the AppTec360 Client



Aggressive Policy Enforcement:



Users will be prompted non stop to execute outstanding actions



AppTec360 Version Lock



If enabled, a version code for the AppTec360 MDM Client can be specified. The AppTec360 client will only update to the specified version. Newer versions will be ignored. A downgrade is NOT possible.



Version Code



Version code for the AppTec360 MDM Client to be locked on to.



Disable AppTec360 Notification



If disabled the AppTec360 Client won’t show a Notification in the Notification Bar. Thus users can close the AppTec360 client via the task manager. If the AppTec360 client is closed, several features including Kiosk Mode and App Black/Whitelisting will not work properly.


Samsung devices offer a protection mechanism for the AppTec360 Client. The notification is disabled by default on Samsung devices that support the KNOX APIs.


The notification shouldn’t be disabled devices with Android 8.0 or higher.


This site is registered on wpml.org as a development site. Switch to a production site key to remove this banner.