Device Actions Test

Administrators can configure automated actions on the Device Manager, using which the device manager can perform actions based on user or device properties, events, or the existence of applications on devices.

For example, you can configure the following Automated Actions:

  • You can automatically notify users whose iOS or Android devices is jailbroken or rooted that they are in violation of company policy and that the device will be selectively wiped if the device is not brought into compliance.
  • You can automatically enforce a geo-fencing policy whereby if a user's device leaves a defined geographical perimeter, the device is blocked from accessing your organization's email, is selectively wiped, or is revoked.
  • You can alertusers automatically when mobile devices are roaming domestically or internationally and that they may be charged extra for the service.
  • You can wipe a user's device automatically when the user leaves the company, and can disable the user's Active Directory account, so that the user can no longer access your organization's data.
  • You can place a user's device into an Out Of Compliance state automatically if the user installs a blacklisted app, and you can send the user a notification informing them that they have broken the organization's mobile app policy.

To understand the workload imposed by these actions on the server, measure the efficiency of the server in performing these actions, and proactively isolate bottlenecks in the execution of these actions, administrators should use the Device Actions test. This test tracks the automated actions triggered on the XenMobile MDM server, reports the number and nature of actions completed by the server and the count of actions pending on the server, and thus points to probable bottlenecks in the execution of these actions.

Target of the test : A Citrix XenMobile MDM

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the XenMobile MDM server monitored

Configurable parameters for the test
  1. Test period - How often should the test be executed
  2. Host - The host for which the test is to be configured.
  3. WSDL url – This test connects to XenMobile’s REST Web Services API to pull out the required metrics. For this, you need to configure the test with the URL for connecting to the REST Web Services API. By default, eG Enterprise automatically discovers this URL and displays the same against wsdl url.   
  4. username and password – Specify the credentials of a XenMobile Device Manager web console user with the Administrator role.
  5. CONFIRM PASSWORD – Confirm the password by retyping it here.
  6. ssl – Indicate whether/not the XenMobile MDM server is SSL-enabled. By default, this flag is set to No.
  7. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability
    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

 

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Full wipes completed:

Indicates the number of full wipes completed.

Number

If a device is stolen or lost, you can send a request to have all data on a device be erased. This is called a Full wipe.

Pending full wipes:

Indicates the number of full wipes that are still pending.

Number

A steady increase in the value of this measure could indicate that the server is taking too long to process full wipe requests. It could also indicate that erasing a device could not complete in full; this can happen if the "current holder" of the device has time to turn the device off before the content of the memory card is completely deleted. As such, they may still have access to data on the device. If the wipe of the device is not done and it is retrieved, you can cancel the wipe command.

Corporate wipes completed:

Indicates the number of corporate wipes completed by the server.

Number

When a corporate/selective wipe is performed, only the corporate data from the end user’s device is deleted, leaving the personal data intact.

Pending corporate wipes:

Indicates the number of corporate wipes still pending on the server.

Number

A steady increase in the value of this measure could indicate that the server is taking too long to process corporate wipe requests.

Locks completed:

Indicates the number of device locks completed.

Number

If the device is lost, but you are not sure it was stolen, you can remotely "lock" the device.

For Android and Windows Mobile devices, the system will then generate a PIN code that will be set in the device if the user had not set a PIN code already. To access the device, the user will have to type that PIN code.

Pending locks:

Indicates the number of device locks pending on the server.

Number

A steady increase in the value of this measure could indicate that the server is taking too long to process device locks.

Tracks completed:

Indicates the number of device tracks completed.

Number

 

Pending tracks:

Indicates the number of device tracks that are still pending on the server.

Number

A steady increase in the value of this measure could indicate that the server is taking too long to perform device tracking.