{"id":1313,"date":"2024-03-20T11:10:29","date_gmt":"2024-03-20T10:10:29","guid":{"rendered":"https:\/\/kb.apptec360.com\/manual\/?post_type=knowledgebase&p=1313"},"modified":"2024-04-30T07:58:56","modified_gmt":"2024-04-30T05:58:56","slug":"client-configuration","status":"publish","type":"knowledgebase","link":"https:\/\/kb.apptec360.com\/manual\/knowledgebase\/android-enterprise-fully-managed-device-configuration\/general\/device-settings\/client-configuration\/","title":{"rendered":"Client Configuration"},"content":{"rendered":"\n

Here you can perform the following configurations on your Android device:<\/p>\n\n\n\n\n\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t
Edit<\/a><\/caption>\n

\n

Out of Compliance Time<\/p>
\n <\/td>


\n

The user response timeout limit after which the enforcement action is applied.<\/p>
\n <\/td>\n<\/tr>\n


\n

Enforcement action after compliance timeout<\/p>
\n <\/td>


\n

Enforcement action when a user doesn’t perfom actions that leads to a compliant device status<\/p>
\n <\/td>\n<\/tr>\n


\n

Data Collection Frequency<\/p>
\n <\/td>


\n

Frequency with which device\/GPS-information is to be collected<\/p>
\n <\/td>\n<\/tr>\n


\n

Device Heartbeat Frequency<\/p>
\n <\/td>


\n

Interval in which the device should contact the AppTec360 Server<\/p>
\n

Min. 1 minute<\/p>
\n

Max. 24 hours<\/p>
\n <\/td>\n<\/tr>\n


\n

Enable Location Updates<\/p>
\n <\/td>


\n

If activated, the device sends location updates to the AppTec360 Server<\/p>
\n <\/td>\n<\/tr>\n

<\/td>
\n

Location Update Time<\/p>
\n <\/td>


\n

Determines in what time intervals the device sends location updates to AppTec360<\/p>
\n <\/td>\n<\/tr>\n

<\/td>
\n

Use Google Location Accuracy for Location Update<\/p>
\n <\/td>


\n

If activated, the network location will be used for location updates (if this was deactivated under “Restrictions”, then this setting will not affect anything)<\/p>
\n <\/td>\n<\/tr>\n

<\/td>
\n

Use GPS Location for Location Update<\/p>
\n <\/td>


\n

If activated, the GPS will be used for location updates<\/p>
\n <\/td>\n<\/tr>\n

<\/td>
\n

Allow Mock (Fake) Locations<\/p>
\n <\/td>


\n

Allows the forging of location information via third party apps<\/p>
\n <\/td>\n<\/tr>\n


\n

Lost Connection Action<\/p>
\n <\/td>


\n

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.<\/p>
\n <\/td>\n<\/tr>\n

<\/td>
\n

Action<\/p>
\n <\/td>


\n

The action that is to be taken, as soon as a device becomes non-compliant.<\/p>
\n


    \n
  • Lock Device = lock device<\/li>
    \n
  • Wipe Device = device will be restored to factory settings<\/li>
    \n
  • Wipe Device & SD Card = device will be restored to factory settings and SD Card storage will be deleted<\/li>
    \n <\/ul>
    \n <\/td>\n<\/tr>\n
<\/td>
\n

Threshold<\/p>
\n <\/td>


\n

You can specifiy a threshhold of failed Heartbeats which are necessary to trigger the specified action.<\/p>
\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n\t\n\t\n\t\n\t\n\t\n\t
Edit<\/a><\/caption>\n

\n

Policy Enforcement Mode<\/p>
\n <\/td>


\n

Default:<\/p>
\n <\/td>


\n

Users will be prompted periodically to execute outstanding actions<\/p>
\n <\/td>\n<\/tr>\n


\n

Lazy Policy Enforcement:<\/p>
\n <\/td>


\n

Users will never be prompted to execute outstanding actions. All open action will be shown in the AppTec360 Client<\/p>
\n <\/td>\n<\/tr>\n


\n

Aggressive Policy Enforcement:<\/p>
\n <\/td>


\n

Users will be prompted non stop to execute outstanding actions<\/p>
\n <\/td>\n<\/tr>\n


\n

AppTec360 Version Lock<\/p>
\n <\/td>


\n

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.<\/p>
\n <\/td>\n<\/tr>\n

<\/td>
\n

Version Code<\/p>
\n <\/td>


\n

Version code for the AppTec360 MDM Client to be locked on to.<\/p>
\n <\/td>\n<\/tr>\n


\n

Disable AppTec360 Notification<\/p>
\n <\/td>


\n

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.<\/p>
\n

Samsung devices offer a protection mechanism for the AppTec360 Client. The notification is disabled by default on Samsung devices that support the KNOX APIs.<\/p>
\n

The notification shouldn’t be disabled devices with Android 8.0 or higher.<\/p>
\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n

<\/div>\n","protected":false},"parent":1311,"menu_order":0,"template":"","class_list":["post-1313","knowledgebase","type-knowledgebase","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/kb.apptec360.com\/manual\/wp-json\/wp\/v2\/knowledgebase\/1313","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kb.apptec360.com\/manual\/wp-json\/wp\/v2\/knowledgebase"}],"about":[{"href":"https:\/\/kb.apptec360.com\/manual\/wp-json\/wp\/v2\/types\/knowledgebase"}],"version-history":[{"count":6,"href":"https:\/\/kb.apptec360.com\/manual\/wp-json\/wp\/v2\/knowledgebase\/1313\/revisions"}],"predecessor-version":[{"id":6662,"href":"https:\/\/kb.apptec360.com\/manual\/wp-json\/wp\/v2\/knowledgebase\/1313\/revisions\/6662"}],"up":[{"embeddable":true,"href":"https:\/\/kb.apptec360.com\/manual\/wp-json\/wp\/v2\/knowledgebase\/1311"}],"wp:attachment":[{"href":"https:\/\/kb.apptec360.com\/manual\/wp-json\/wp\/v2\/media?parent=1313"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}