Registered Applications

Document created by user.oxriBaJeN4 Employee on Sep 16, 2015Last modified by user.oxriBaJeN4 Employee on May 24, 2017
Version 4Show Document
  • View in full screen mode

This article outlines the use of the Registered Applications view to manage device authentication sessions and interrogate the device estate regarding Mimecast software versions and details of the device hosting the Mimecast application.

 

Applies to:

  • Administrators with Registered Applications selected as part of their Role.

 

In this article:

 

Overview

Registered Applications are end user devices that have registered with one of Mimecast's mobile, desktop or continuity services. These include:

  • Mimecast for Outlook
  • Mimecast for Mac
  • Mimecast Mobile
  • Mimecast Mobile for BlackBerry
  • Mimecast Mobile for Windows Phone

 

Information regarding the device, the application software and registration details are provided for all users within your environment who have access to Mimecast applications. Administrators can determine whether certain devices require application software updates, and identify devices that have not registered for an extended period of time. The Registered Applications view also provides the ability to Revoke application authentication sessions.

 

Using the 'View By' drop-down

There are two main views:

  • Operating System - Provides a list view of all registered authentication sessions.
  • User - Groups all registered authentication sessions by email address.

 

Using the 'Status' drop-down

When applications register during the authentication process a device specific session is created. The Status column reflects the validity of the session:

 

Status
Description
ActiveThe authentication session has been active within the timeframe of the Authentication TTL value set in the relevant Authentication Profile.
ExpiredThe authentication session has not been in use within the timeframe of the Authentication TTL value set in the relevant Authentication Profile. Expired entries will remain visible in the Administration Console for 6 months after they have expired.
RevokedAn administrator has revoked the authentication session. Revoked entries will remain visible in the Administration Console for 6 months after they have been actioned.

 

Once an authentication session has been revoked the next time the application is used all Mimecast application data is removed and the user is logged out.

Authentication sessions for web applications and portals are not reflected.

 

Viewing version information for an application across the device estate

It may sometimes be a requirement to interrogate the device estate to identify devices operating legacy or outdated versions of Mimecast applications. Registered Applications provides this capability through the use of the Search, Application and Version drop-downs.

 

An example may be that Mimecast announces the end of life of a major version of Mimecast for Outlook. Administrators may wish to provide a report reflecting each user that requires to be updated to the latest version. Follow the steps below to provide this data:

  1. Navigate to Services / Applications | Registered Applications.
  2. From the menu bar, select the required applications filter from the applications dropdown:

    If the aim is to Export the results of the query, Mimecast recommends using the Operating System view for this task.

  3. Select the relevant application version from the versions dropdown.

    Only versions that have been in use within the organization will be reflected. If a user is upgraded to a newer version, and the authentication session is simply refreshed rather than a new session being created, then the version information will be updated. The previous outdated version will no longer be reflected.

  4. Results for the filtered view are displayed. These may be exported to a spreadsheet by selecting Export.

    Last Registration reflects the date and time the authentication session was last registered with Mimecast. This may be useful for understanding when the device was last used.

Viewing application and version information for a single user

It may sometimes be a requirement to interrogate the device estate to identify which Mimecast applications a specific user has accessed. Registered Applications provides this capability through the use of the Search field.

 

An example may be that there is a requirement to report upon the to Mimecast applications that a specific user has accessed. Follow the steps below to provide this data:

  1. Navigate to Services / Applications | Registered Applications.
  2. Enter the email address or name of the user into the Search field.

    Mimecast recommends using the User view for this task.

  3. Expand the accordion for the relevant user, all authentication sessions for this user are displayed. These may be exported to a spreadsheet by selecting Export.

    Last Registration reflects the date and time the authentication session was last registered with Mimecast. This may be useful for understanding when the device was last used.

Additional reading

Attachments

    Outcomes