Mobileiron Core and Connector 9.5.0.0 Release and Upgrade Notes

MobileIron Core and Connector
9.5.0.0 Release and Upgrade Notes

August 24, 2017
This document contains the following information:

About MobileIron Core
New features summary
Support and compatibility
Language support
Resolved issues
Known issues
Limitations
MobileIron Core upgrade information
Enterprise Connector upgrade information
Documentation resources
Proprietary and Confidential | Do Not Distribute

About MobileIron Core
MobileIron Core is a mobile management software engine that enables IT to set policies for mobile devices,
applications, and content. This enables Mobile Device Management, Mobile Application Management, and Mobile
Content Management capabilities.
Important Note for Mobile@Work for Android: Versions of Mobile@Work for Android prior to Mobile@Work
9.2.0.0 have known compatibility issues with this release of MobileIron Core and are not supported. Upgrade
Mobile@Work on all impacted devices before upgrading Core.
New features summary

This section provides summaries of new features developed for the current release of MobileIron Core. References
to documentation describing these features are also provided, when available.
General features
Android and Android enterprise features
iOS and macOS features
Windows features
AppConnect features
Enterprise Connector features
Standalone Sentry features
Go to https://community.mobileiron.com/welcome to search release notes describing features added to previous

releases. MobileIron Support credentials are required to access this site.
General features
This section summarizes new features which are common to all platforms or new features that are platform-
independent.
OAuth API configuration: Allows you to enable or disable the OAuth API. When disabled, you turn off Internet
access to the OAuth interface from routable IP addresses.
For details, see Access Control Lists: Portal ACLs in the latest MobileIron Core System Manager Guide.
Apps@Work branding: You can now brand Apps@Work on iOS and Android devices with your enterprise
name, color, and icons.
For details, see Apps@Work branding in the Apps@Work Guide.
Added CBA management for Office 365: Added Certificate Based Authentication (CBA) for Office 365 Email
ActiveSync (EAS) on Core to improve interoperability with Microsoft and enhance security. Issued
Authentication certificates are managed by Core (actions include issue, renewal, expiry, and revocation of
certificates).
SSH Configuration: The System Manager portal allows you to upload the public keys then enable or disable
public key and password authentications.
MobileIron Update Management: Provides view-only information to administrators for security patches for
compliance on user devices.
MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 2

User-provided certificate deletion: You can now specify in the Admin Portal that Core deletes user-provided
certificates private keys and passwords older than some number of days.
For details, see Configuring a user-provided certificate enrollment setting in the MobileIron Core Device
Management Guide.
Minor text changes on Admin Portal: Affects app configurations for an app in Apps > App Catalog.
Enhanced security: Removed the Generate CSR button and functionality from the Admin Portal. Core no
longer displays the RSA private key of local CAs, for enhanced security.
Disable analytics data collection: You can choose to disable analytics data collection. For details, see
Disabling analytics data collection in the Device Management Guide for Android Devices.
End user control of the camera: You can now allow the end user to control use of the camera. For details,
see Lockdown Policies in the Getting Started with MobileIron Core guide.
Android and Android enterprise features

This section summarizes new features which are specific to the Android and Android enterprise (Android for Work)
platforms.
Cross profile widgets: You can now apply a configuration to an Android app that enables it to be displayed as
a widget that can be used across different profiles. For details, see About Apps for Android enterprise in the
Device Management Guide for Android enterprise (Android for Work).
Disable system apps and restrict input methods: You can enable or disable the use of system apps such as
the camera or restrict the use of certain input methods to the device. For details, see Lockdown Policy in the
Active link in push notifications: A link will be included, if necessary, in notifications pushed to a device. The
link will open in the devices system browser. For details, see Setting Push Notifications in the Device
Management Guide for Android Devices.
Control use of biometric passwords: You can enable or disable the use of the fingerprint, face, or iris scan
unlock feature using the security policy. For details, see Security Policy in the Device Management Guide for
Android enterprise (Android for Work).
Bluetooth data sharing in the Samsung Knox workspace: The end user now has the ability to enable
bluetooth data sharing in the Samsung Knox workspace. For details, see Android Samsung Knox Container
settings in the Device Management Guide for Android Devices.
Set runtime permissions: Set runtime permissions for apps to always accept or always deny or to accept a
global configuration so that users are not prompted and cannot change the permission. For details, see About
Apps for Android enterprise in the Device Management Guide for Android enterprise (Android for Work).
Choose App distribution: You can choose to have your users receive apps using Apps@Work or Google
Play. For details, see Distributing your enterprise apps in the Google Play App catalog or in Apps@Work in
the Device Management Guide for Android enterprise (Android for Work).
Add a Google account to Android enterprise managed devices: You can add an account to Android
enterprise managed devices and set disallow modify accounts to true so that no other accounts can be added
or changed. For details, see Adding a Google Account to an Android enterprise managed device in the
MobileIron Tunnel support in the Samsung Knox Workspace: MobileIron Tunnel is supported in the
Samsung Knox Workspace on Android devices. For details, see the MobileIron Tunnel for Android Guide for
Administrators for version 3.0.0. Also see the product bulletin at https://community.mobileiron.com/docs/DOC-
6754.

iOS and macOS features
This section summarizes new features which are specific to the iOS and macOS platforms.
Restart or shutdown supervised iOS devices: In the Admin Portal, you can now restart or shutdown
supervised iOS devices running iOS 10.3 through the most recently released version supported by MobileIron.
For details, see Restarting or shutting down supervised iOS devices in the MobileIron Core Device
Management Guide for iOS Devices.
Play a sound when a supervised iOS device is in lost mode: In the Admin Portal, when you enable lost
mode for a supervised iOS device, you can specify that the device plays a sound. This option is available for
iOS 10.3 through the most recently released version supported by MobileIron.
For details, see Enable MDM lost mode in the MobileIron Core Device Management Guide for iOS Devices.
Networked Tethered added to iOS device details: In the Admin Portal, Networked Tethered is listed in
device details for devices running iOS 10.3 through the most recently released version supported by
MobileIron. You can use this field when creating dynamic labels, searching devices, or using appropriate
MobileIron Core V2 APIs. The value is true only if the device is tethered to a Mac with a USB connection so that
all network traffic from the iOS device uses the Macs Internet connection.
App update options: You can decide under what circumstances Core sends a request to update a given app
on iOS devices. Core can either send an update request to all devices, regardless of app updated status, or
only to those devices where Core determines the app is out of date, based on the date of installation.
For details, see Informing users of new apps and updates on iOS and macOS devices in the Apps@Work
Guide.
Support for access control, app control rules, and compliance actions on macOS devices: Core now
supports access control and compliance actions for macOS devices.
For details, see Managing Compliance and Working with Events in the MobileIron Core Device
Management Guide, and Using Policies in Getting Started with MobileIron Core.
New macOS policy violations event settings: You can now configure specific policy violation event settings
for macOS devices, including prohibited macOS versions, deactivated MDM profiles, and disabled FileVault
encryption.
For details, see Working with Events in the MobileIron Core Device Management Guide.
Apple DEP features: You can now configure the Apple DEP enrollment wait time directly in the DEP
enrollment profile. You can also add your own custom text to be displayed on Apple DEP devices, and create
administrator accounts for Apple DEP macOS devices.
For details, see Creating DEP enrollment profiles in the MobileIron Core Device Management Guide.
Send installation request to macOS devices: You can now send an app installation request on device
registration to macOS devices.
For details, see Managing Mobile Apps for iOS in the Apps@Work Guide.
Support for macOS in the App Catalog and Apps@Work on macOS devices: Core now supports macOS
apps in the App Catalog and Apps@Work on macOS devices. You can import macOS VPP apps and apply
them to or remove them from a macOS label. The typical actions are supported, such as Source Filter, Platform
Filter, device install count, Select Devices Installed in the Device Details tab, Send Installation Request, Force
Device Check-In, Retire, Export to CSV, view installed apps, view and edit macOS apps.
For details, see Managing Mobile Apps for iOS in the Apps@Work Guide.
Restrictions for macOS: Core allows you to create restrictions settings for macOS devices, as you would for
iOS devices.
For details, see macOS settings in the MobileIron Core Device Management Guide.
Apple VPP support for macOS devices: Core supports Apple VPP management for macOS devices,
including importing macOS VPP apps from the Apple VPP portal.

For details, see Using the Apple Volume Purchase Program (VPP) in the MobileIron Core Device
Management Guide.
Support for app control rules for macOS: Core supports the creation of app control rules for macOS
devices.
For details, see macOS settings in the MobileIron Core Device Management Guide.
Support for macOS Gatekeeper Control and FileVault 2 encryption on macOS devices: Core supports
encryption of macOS devices using FileVault 2, as well as the control of Gatekeeper features using System
policy control, System Policy Managed and System Policy Rule settings.
For details, see Managing Policies in the MobileIron Core Device Management Guide.
Windows features
This section summarizes new features which are specific to the Windows platform.
Application Scheduling: Allows administrators to specify a time when to silently deploy and install
applications on devices.
For details, see the Managing Apps on Windows Devices chapter in the latest MobileIron Core Apps@Work
Guide.
Application restrictions with Windows 10 Mobile: Allows administrators to use an updated API to match
capabilities of Windows Phone 8.1.
For details, see the Managing Apps on Windows Devices chapter in the latest MobileIron Core Apps@Work
Guide.
Device Management for Windows 10 Desktops: Allows administrators the ability to
- Add restrictions to the device, including Task Manager, Control Panel, File Explorer, and Registry Editor.
- Work with restricting USB Devices.
- Enable devices to send current OS information.
For details, see the MobileIron Bridge chapter in the latest MobileIron Core Device Management Guide.
Configuring Outlook for Windows 10 Desktops: Allows administrators to:
- Configure a profile for use with the Outlook client.
- Can be used with Office 2010 and 2013.
- Needs to have MobileIron Bridge.
Desktop Settings for Windows 10 Desktops: Allows administrators to:
- Setup screensaver, background, and lock screen configurations.
- Set up desktop shortcuts.
Delegated Administration features

This section summarizes new Delegated Administration features. For more details, see the Delegated
Administration Guide.
Certificate Management is enabled for Device Space: The device space administrator can manage and
view certificates.
Log and Events Management: The following roles have been added:
- View audit logs

- View MDM activity
- Manage certificates
- View certificates
- Manage event settings
- View event settings
- Manage events
- View events
NOTE: Manage Certificates and View Certificates roles are made available for Device Space.
Managing iOS restrictions: These configurations are supported for device space.
Retire Device and Export CSV roles: These are available for device space.
Managing Certificate configuration: Device space administrators can now manage certificate configurations
in his space.
Managing Certificate enrollment configuration: Device space administrators can now manage the following
certificate enrollment configuration in his space:
- Entrust
- Local
- SCEP
- Symantec Managed PKI
- Symantec Web Services Managed PKI
AppConnect features
There are no new features for AppConnect in this release.
Enterprise Connector features

There are no new features for Enterprise Connector in this release.
Standalone Sentry features

This section summarizes Standalone Sentry features which are new in this release.
Validate certificate chain: MobileIron Core validates the TLS identity certificate chain uploaded to Standalone
Sentry appliances.
For details, see the "Standalone Sentry certificate" section in the MobileIron Sentry Guide for MobileIron Core.
Support and compatibility

The information in this section includes the components MobileIron supports with this product.

Support policy
MobileIron defines supported and compatible as follows:
Supported product versions The functionality of the product and version with currently supported
releases was systematically tested as part of the current release and,
therefore, will be supported.
Compatible product versions The functionality of the product and version with currently supported
releases has not been systematically tested as part of the current
release, and therefore not supported. Based on previous testing (if
applicable), the product and version is expected to function with currently
supported releases.
MobileIron end of sale and support policy

For details on the MobileIron end of sale and support policy, go to https://community.mobileiron.com/docs/DOC-
1089.
MobileIron Core support and compatibility

This version of MobileIron Core is supported and compatible with the following product version/s:
Enterprise Connector
Reporting Database
Atlas
Monitor
Sentry
iOS
Mac OS
Android
Windows
Enterprise Connector
Product Supported Compatible
Enterprise Connector 9.4.0.0, 9.5.0.0 9.3.0.0
Reporting Database
Reporting Database 1.7.0.0, 1.8.0.0 1.6.0.0, 1.6.0.1

Atlas
Atlas 1.3 Not applicable. (v1.3 has been shipping for

many years. There is no previous version that
is compatible or even used.)
Monitor
Monitor 1.0, 1.1 Not applicable since all listed versions are
tested and supported.
Sentry
Standalone 9.0.2, 9.1.0 8.5.0
Integrated 6.2.1 6.1.1, 6.2.0
MobileIron Access R16 Not applicable since only the latest version is
available to all customers in Cloud.
iOS
iOS 9.0 to 10.3.3 8.0

Pending release of iOS 11 iOS 11 Beta 7
Mobile@Work 8.6.0, 9.0.1, 9.1.0, 9.5.0 8.0.2
Docs@Work 2.2.0, 2.2.1, 2.2.2 2.0.0, 2.1.0, 2.1.1, 2.1.2
Web@Work 2.0.0 1.9.2, 1.9.3
Apps@Work Container 1.3.0 when using 1.1.2, 1.2.0 when using Mobile@Work 8.6.0,
Mobile@Work 9.5.0 9.0.1, or 9.1.0
1.2.1 to 1.2.2 when using
Mobile@Work 8.6.0, 9.0.1, or
9.1.0
PIV-D Entrust app for iOS 1.3 1.1, 1.2
Tunnel 1.0.6, 2.2.0 2.1.1

Email+ 2.4.0, 2.4.1, 2.5.0 2.1.0 to 2.3.4
Help@Work 2.1.0, 2.1.1 2.0.2
Insight 5.1.1 Not applicable since all listed versions are

Mac OS
macOS/OS X macOS10.10 Not applicable since all listed versions are

OS X10.11, OS X10.12
Android
Android 4.2, 4.3, 4.4, 5.0, 5.1, 6.0, 7.0, Not applicable since all listed versions are
7.1, 8.0 tested and supported.
Zebra Android devices (Android
4.4, 5.1)
Mobile@Work 9.2.0.2, 9.3.0.2, 9.4.0.3, 9.5.0.0 Not applicable since all listed versions are
Docs@Work 1.8.0, 2.0.0, 2.1.0 Not applicable since all listed versions are
Docs@Work 1.7.0, 2.0.0, 2.1.0 Not applicable since all listed versions are
(Android enterprise) tested and supported.
Web@Work 2.0.0, 2.0.1 Not applicable. (The previous version,

Web@Work 1.9.1, is wrapped with wrapper
7.5.3, which is currently not supported.)
Apps@Work Not applicable. (Apps@Work is Not applicable. (Apps@Work is part of

part of Mobile@Work.) Mobile@Work.)
Secure Apps Manager 7.5.5.0, 7.6.0.0, 7.7.0.0, 7.8.0.0 Not applicable. (All listed versions are tested
and supported. AppConnect supports only 4
versions with any new version of MobileIron
Core.)
PIV-D Entrust app for 1.0 Not applicable.

Android

Tunnel 1.5.0, 2.0.0 1.4.0

(Android native)
(Android enterprise)
Email+ 2.5.0.0 (AppConnect enabled) 2.0.0.0 to 2.4.0.0 (AppConnect enabled)

2.5.0.0 (Android enterprise) 2.3.0.0 to 2.4.0.0 (Android enterprise)
1.4.0.0 to 1.6.3.0 (AppConnect and non-
AppConnect enabled)
Help@Work 2.1.0, 2.1.1 2.0.2
Insight 5.1.1 Not applicable since only the listed version is

Windows
Windows Windows Phone 8.1 Windows 10 Mobile SKU (1511, 1607, 1703*)
Windows 10 Mobile SKU (1607, Windows 10 Desktop SKU (1511, 1607,
1703*) 1703*)
Windows 10 Desktop SKU Note: Not all Windows 10 Mobile devices can
(1607, 1703) be upgraded to Windows version 1703. The
currently known list can be found at https://
www.windowscentral.com/windows-10-
mobile-creators-update-only-coming-11-
eligible-handsets
Apps@Work 9.5.0.5 Not applicable since only the listed version is

Tunnel 1.2.0 1.1.0
Supported browsers
The current version of MobileIron Core has the following browser support:
Browser Supported Compatible
Internet Explorer 11 8*, 9*, 10*
Edge Not supported Not compatible
Chrome >59 >59*
Firefox >=25 < 25*

Browser Supported Compatible
Safari Not supported 10.1*
Chrome - iPad Not supported Not compatible
Safari - iPad Not supported Not compatible
* This configuration is not covered under MobileIrons product warranty.
Supported browser resolution

Browser Resolution Supported Compatible
1280x1024 Yes Yes
1366x768 Yes Yes
1440x900 Yes Yes
Higher resolutions No Yes
* This configuration is not covered under MobileIrons product warranty.
Language support
MobileIron Core supports the following languages on devices for messages and apps:
Language support for MobileIron Core messages
Language support on Android and Android enterprise devices
Language support on iOS and macOS devices
Language support on Windows devices
Language support for MobileIron Core messages

MobileIron Core supports the following languages for messages sent to devices:
Chinese (Simplified)
Chinese (Traditional)
Dutch (Netherlands)
English
French (France)
German (Germany)
Italian (Italy)
Japanese
Korean
Polish

Portuguese (Brazilian)
Romanian (Romania)
Russian
Slovak
Spanish (Latin American)
Language support on Android and Android enterprise devices

Refer to Mobile@Work for Android Release Notes, for a complete list of supported languages for Android and
Android enterprise (Android for Work) devices.
Language support on iOS and macOS devices

Refer to Mobile@Work for iOS Release Notes, for a complete list of supported languages for iOS and macOS
devices.
Language support on Windows devices

MobileIron Core supports the following languages in client apps on Windows devices:
Chinese (Simplified)
Chinese (Traditional)
English
French (France)
German (Germany)
Japanese
Korean
Portuguese (Brazilian)
Russian
Spanish (Latin American)
Resolved issues
This section describes the following resolved issues fixed in the current release of MobileIron Core:
Resolved general issues
Resolved Android and Android enterprise issues
Resolved iOS and macOS issues
Resolved Windows issues
Resolved Enterprise Connector issues
Go to https://community.mobileiron.com/welcome to search release notes describing resolved issues fixed in

previous releases. MobileIron Support credentials are required to access this site.

Resolved general issues
This section describes resolved issues which are common to all platforms or are platform-independent.
VSP-46186: The performance of queue activation request process PUBLISH_APP_TO_LABEL has been
improved.
VSP-41890: There was severe performance degradation when customers were using white list app control
rules. As a result there as a slowdown in server processing and delay in reporting the compliance state of
devices. This issue has been resolved.
Customers that use Atlas are advised to run Atlas sync before upgrade.
VSP-46079: Problems with LDAP Sync requests in batch mode were introduced in Core 9.4.0.0. This has been
resolved.
VSP-40773: Email address validation is now consistent across the system.
VSP-46245: LDAP Sync batch processing removed group members from Core when any one of the batch
members DN on the LDAP server is changed to have unbalanced parenthesis. This has been fixed.
VSP-45983: Provisioning profiles for in-house apps can now be renewed successfully.
VSP-45368: Managed app configuration settings for an app in the MobileIron Core App Catalog on the Admin
Portal had an error. If the app specified a default value of 0 for a setting, the App Catalog did not display a 0.
The issue has been fixed.
VSP-45283: Deleting retired devices (and associated data settings) was deleting Core's history of certificate
data for the issued data. This has been resolved.
VSP-35955: The api/v2/devices API call returned the OS Update Status column twice. This has been fixed. For
Android the column will stay "OS Update Status" and for iOS/macOS it will be "Apple OS Update Status".
VSP-45317: If a registering device was incorrectly matched to multiple default polices of the same type, the
registration failed. This has been resolved.
VSP-46077: Core prevented the deletion of the Certificate configuration if it was referenced in the Wi-Fi
configuration. This has been resolved.
VSP-42799: Some device model names contain commas, which can cause problems when generating a
comma-separated list of devices in a CSV file. This has been resolved.
VSP-45231: Core was unable to add app restriction configurations for iOS apps with bundle identifiers missing
a period (.). This has been resolved.
VSP-25917: Core no longer collects app version information.
VSP-43345: Application compliance checks would scan through trashed records in app_control_failure, which
resulted in performance degradation. This has been fixed and no longer happens.
VSP-44116: When the userAccountControl value was used in custom attributes, and if the value is other than
*account_disabled(2) or locked_out(16) or password_expired (8388608)*, Core stored the value as 0 in the
database. This has been resolved.
VSP-44372: The api/v2/labels API was not returning device information. This has been resolved.
VSP-44386: Clicking the Name field was not sorting the identifiers for the compliance actions in the Policies &
Configs > Compliance Actions page. This has been resolved.
VSP-44777: Managed App Config schema URL used http instead of https. This has been resolved.
VSP-43124: Apps@Work now uses high resolution app icons.
VSP-44681: Core now deletes app_control_failure records for retired devices, saving space in the database.
VSP-41625: The time zone conversion is now consistent on different browser on Windows machines.
VSP-40458: It was not possible to copy/paste a phone number from the devices grid. It is now possible.
VSP-42558: Event description was reverting to default text if it is edited. This has been fixed.

VSP-43918: The LDAP group removal from the Admin Portal was showing the group name twice in the popup
window when the group is assigned to a space. This has been resolved.
VSP-44333: The sort on label Type was not working as expected. This has been resolved.
VSP-46266: Removing a label associated with a device for the second time (using the API) displayed the
wrong message. This has been fixed.
VSP-30512: When password policy is set to optional, General password required section is now editable on the
device under System Preferences.
VSP-43211: Enabling or disabling attachment control and regenerating encryption key failed to update
modified_at timestamp in mi_app_setting while bumping the version number for the Docs@Work configuration.
This has been resolved.
VSP-42663: When retiring a device while the Device Details tab is open, and then re-registering the same
device by adding a single device, the new device record would not show until you refreshed the page. This has
been resolved.
VSP-45026: The App Control rule for the disallowed app event alert had an incorrect French translation. This
has been resolved.
VSP-40854: If the app update sends a message to update an application for a specific device that is blocked
because the Core server assumes that the application is already at the latest version, the administrator can use
the send message option to force the update. In this case, Core will sends the command to install the
application regardless of whether the Core server thinks the device is already at the latest version.
VSP-44390: The file name in the file upload field now shows only the file name, and not the full path of the file.
Resolved Android and Android enterprise issues

This section describes resolved issues which are specific to the Android and Android enterprise (Android for Work)
platforms.
VSP-46191: On Samsung Knox devices, the Mobile@Work client did not display the password field correctly
on the Exchange Email setup screen. This issue is resolved.
Newly added devices will prompt the user to enter the password. Existing devices must have the Exchange
configuration pushed down to them again.
VSP-45315 and VSP-45316: There are no longer resource errors when uploading Android in-house apps.
VSP-40375: MobileIron Core 9.5.0.0 has an upgraded APK Tool that can work with in-house Android apps built
using the Android 7 platform.
VSP-43866: Tapping rating stars or outside Install button no longer results in installation of the app in Android
Apps@Work. Only tapping on Install button results in installation of the app.
VSP-43895: Redundant, and possibly conflicting, layouts were occurring when more than one Core instance
publishes the Custom Google Play layout. This has been resolved.
VSP-21655: Google Play-App search with special characters was not displaying proper results. This issue has
been resolved.
VSP-44656: Setting the mandatory property to true for non AppConnect Android apps no longer updates
'ENFORCE_VERSION' property to true using v2 API.
VSP-42105: Core 9.5.0.0 added validation that the MNC value for the Samsung APN configuration is 2 or 3
digits.
VSP-43283: Using Core 9.5.0.0 and mutual authentication for the Android client, the larger 64KB payload size
is now supported if using Mobile@Work 9.4.0.0 or 9.5.0.0
Resolved iOS and macOS issues

This section describes resolved issues which are specific to the iOS and macOS platforms.
VSP-45803: The System iOS Enterprise AppStore SCEP updated the default signature to SHA256 for
customers who installed Core before 8.5.0.0 or for customers who already had SHA256 as the default. This
has been resolved.
VSP-43339: Core replaces legacy iOS and DEP Enrollment CA certificates during upgrade, and issues new
iOS and DEP Enrollment CA certificates signed with the SHA384 algorithm.
VSP-45628: Different userIDs for the same macOS device will no longer prevent the Core server from pushing
the required configurations to the device.
VSP-44242: Core no longer incorrectly assigns macOS DEP devices to the default system iOS label during
initial registration.
VSP-45051: If an iOS device was locked or in a NotNow state, failure to install a managed app to the device
because of its state would prevent other policies or commands from running. This has been resolved. Now, if
an iOS device is locked or in NotNow state and a managed app fails to install as a result, then other policies or
commands can continue to run on this device, if those policies or commands can run on a device in a locked or
NotNow state.
VSP-45548: If Core synchronization with Apple DEP took more than 30 seconds, then the attempt to manually
check for updates in the Apple DEP screen would stall. This has been resolved. Now, the Apple DEP check for
updates screen will wait 120 seconds before timing out.
VSP-44631: iOS in-house app upload would fail, producing errors such as "Invalid request" or "Bad request".
This has been resolved.
VSP-42591: Core could not enable the Apple Education feature when Apple Education was configured with an
outbound HTTP proxy. This has been resolved.
VSP-43869: The Apple activation bypass lock action now supports the use of HTTP outbound proxy on Core.
VSP-44577: Core will no longer request managed app configurations for iOS in-house apps.
Resolved Windows issues

This section describes resolved issues which are specific to the Windows platform.
VSP-45800: Windows SCEP subject fields containing only substitution variables failed expansion. This has
been resolved.
VSP-44280: Registrations failed when Core System Default Language and Device Language was set to
Chinese. This has been resolved.
VSP-35696: Windows Phone 10 device users can now launch Apps@Work on Connected Cloud.
VSP-44305: When users upgrade to Core 9.5.0.0, they can now export and import GPO configurations created
using the GPO Editor in this release.
VSP-45785: After upgrading Core to 9.5.0.0, the Windows Phone Enrollment SCEP updates the default
signature to SHA256.
VSP-43237: Enabling CDN for all platforms resulted in users not being able to download and install Windows
in-house apps because the selected Windows apps distribution is not supported on CDN. Users can now
download and install Windows in-house apps from Core, even when CDN is enabled for other platforms.
VSP-43290: When the silent install was set to No, retrying to install an in-house application stopped. This has
been resolved.
VSP-43922: The Windows GPO configuration showed "&lt/&gt" when using "</>" to create a name. This has
been resolved.

Resolved Enterprise Connector issues
There are no resolved Enterprise Connector issues in this release.
Known issues
This section describes the following issues which are found in the current release of MobileIron Core:
Known general issues
Known Android and Android enterprise issues
Known iOS and macOS issues
Known Windows issues
Known Sentry issues
Go to https://community.mobileiron.com/welcome to search release notes describing known issues found in

previous releases. MobileIron Support credentials are required to access this site.
Known general issues

This section describes known issues which are common to all platforms or are platform-independent.
VSP-46872: When entering a port number to the port field of the App Tunnel rules, you cannot enter a "0" using
the number pad on the keyboard.
Workaround: Add the "0" using the number row on top of the keyboard.
VSP-45100: "Assigning the User" portal role action is being tracked as "Assign Space Admin" instead of
"Modify user role".
VSP-46258: For the first time when the administrator changes the SSL Configuration, it sends an error "Fail to
load protocols", however navigating to other tab and getting back, Outgoing SSL Configuration is loaded
properly.
VSP-46660: If the system is set up to support public key based authentication and a backup of this system is
made, restoring a new system from this backup with the 'Exclude system configs' option enabled incorrectly
preserves the public key authentication.
VSP-41543: Device logs cannot be viewed by the administrator if two devices are registered by the same user
without phone numbers.
VSP-46509: The System Manager portal has provision for configuring 4 NIC ports only; however, the M2600
appliance has 6 NICs.
VSP-46548: When High Availability mode is configured, the master node logs the error message "Could not
load host key: /etc/ssh/ssh_host_dsa_key" in /var/log/messages. This does not impact HA functionality.
VSP-46327: The default settings for exporting logs shows the export type as HTTPS and the alternate location
incorrectly as Host/IP. The alternate location should instead show 'URL'.
VSP-42664: "Show Version" does not display the appliance model number.
VSP-46426: The application does not restrict specifying multiple actions for a combination of service, source,
and destination.
VSP-44415: MapQuest URL is unreachable if TLSv1 is identified as the selected Outgoing SSL configuration.
VSP-46209: When creating an event setting without users, SMS and push notifications are not generated.

VSP-45463: The "Revoke Device Certificate" action is not captured in audit logs for SCEP certificates.
VSP-41170: If you enable/disable RDB/SNMP, the Iptables service should be running, otherwise an error
message is displayed.
VSP-46283: The clish command 'show system meminfo' prints an error message referring to an unsupported
command. This impacts the summary information only.
VSP-46185: Importing policies that do not support encryption improperly results in errors logged. This does not
impact functionality in any way.
VSP-46494: In System Manager, when the default update repository has been selected and there are no
updates available, attempting to update, Core displays an error message instead of indicating no updates are
available.
VSP-46620: Core 9.5.0.0 might not successfully re-push configurations that reference the Sentry certificate if
the Sentry certificate is updated and the cert is self-signed or of CSR (cert signing request) type.
VSP-46322: When un-encrypted Wi-Fi configurations are first updated, after upgrading to 9.5.0.0, the system
logs an ERROR message instead of a WARN message.
VSP-46586: Running the Show System Disk command on M2500 and M2600 appliances displays an INQUIRY
FAILED message after displaying available disks. This does not impact product functionality.
Known Android and Android enterprise issues

There are no known issues which are specific to the Android and Android enterprise (Android for Work) platforms.
VSP-46365: If an Android device is associated with a configuration that contains trusted certificates with a
certificate chain of 2 or more, the policy though sent to the device on check-in might not show as being applied
on the device.
VSP-46560: Android enterprise devices after upgrading to MobileIron Core 9.5.0.0 will not have the updated
lockdown policies automatically pushed to the device. Therefore, three new lockdown policies could show
client values with conflicting server values because the new values have not been pushed to the device yet.
These lockdown policies are:
- Allow contact sharing over Bluetooth
- Ensure Verify Apps
- USB Debug
Workaround: Edit the lockdown policy to force a repush.
VSP-45069: An error occurs on the MobileIron Admin Portal when you configure certificate authentication
using AppTunnel with TCP tunneling for Android secure apps. When entering the key <service_name>_CERT
or ES_DEFAULT_CERT in an app's AppConnect app configuration, the dropdown list for the possible values
should display only certificate enrollment settings. It erroneously also displays certificate settings.
Known iOS and macOS issues

This section describes known issues which are specific to the iOS and macOS platforms.
VSP-46264: Service Diagnostic for the Apple Activation Lock Bypass does not traverse through the HTTP
Outbound Proxy. This could provide an incorrect impression that the URL is not working.
VSP-46204: Wi-Fi profiles configured with a manual proxy are in perpetual pending state when sent to macOS
devices.
VSP-45952: Email notifications for macOS devices going out of compliance may use the default email
message specifying iOS rather than macOS.
VSP-45440: Configuration names and descriptions that refer to iOS apply to both iOS and macOS.

VSP-46521: In the DEP profile during upgrade, Skip primary account setup is selected by default and the
Save button is disabled. The Save button is enabled when administrator credentials are entered. If the DEP
profile is for iOS devices, the administrator can choose Prompt primary account setup to users > Admin
user to enable the Save button.
VSP-45966: After upgrading to Core 9.5.0.0, users when editing existing DEP enrollment profiles with the "Skip
primary account setup" selected, need to enter macOS administrator details to successfully edit and save the
DEP enrollment profile.
Known Windows issues

This section describes known issues which are specific to the Windows platform.
VSP-46275: AAD joined devices cannot use the following MobileIron Bridge features:
- Printer Settings
- Bloatware Removal Settings
- GPO Editor
- Desktop Settings
- Device Management Settings
Only MDM registered devices can use the MobileIron Bridge UI feature.
VSP-45485: Currently sentry supports only ActiveSync protocol, where as Outlook uses MAPI protocol.
Administrators cannot use Sentry as the server address in an Outlook profile.
VSP-46280: The Locate action works in Admin Portal on Windows devices, but, the same Locate action is
performed from the User Portal, generates the following error: "Location information is not available".
VSP-46975: Customers using Windows version RS3 (Build 1703 and higher) will need to use a PIN with a
minimum length of 6 digits as required by the OS for the BitLocker feature.
VSP-46573: In branded Core instances, the 'Registration Page Description' does not display company-specific
information inside the Registration Templates in all languages and the word "MobileIron" is visible in the text.
VSP-46714: Administrators cannot restrict users from accessing File Explorer or having write access to
removable storage drives in Core 9.5.0.0.
VSP-45681: Output from a MobileIron Bridge action in a new browser tab sometimes contains the result from a
different script.
VSP-46321: Users will not get search results in GPO editor if using purely the "admx" term. However, users
should be able to search using filenames for the admx files. For example users should be able to search for all
GPO settings listed under "Windowsbackup.admx" file by typing "windows" or "windowsbackup" in the search
box.
Known Sentry issues

This section describes known issues which are specific to Sentry.
VSP-44969: The SPN tool-tip in ActiveSyncServer settings in the Sentry Configuration page in Core blocks
other fields on re-enter edit mode.
Workaround: Navigate away from the settings page by canceling the edit operation and re-entering the edit
mode.
VSP-46619: If a Sentry certificate, generated by local CA (self-signed) or by an external SCEP CA using CSR,
fails to be renewed within 10 minutes, Core will not update the version and will not send out new profiles
containing a new Sentry Certificate.

Workaround: Administrators should get the Sentry certificate by clicking View Certificate on the Sentry UI in
Core, and then increment the versions manually by editing all Sentry configurations that use the certificate to
force a repush to all devices. Customers using CAs that take more than 10 minutes to respond can contact
MobileIron Customer Success for assistance in extending the wait interval to more.
Known Enterprise Connector issues

This section describes known Enterprise Connector issues found in this release.
VSP-46783: When configuring the Enterprise Connector with the Core connection details, testing the
connection without saving the connection information results in an error message.
Limitations
This section describes the following limitations (typically third-party limitations) which are found in the current
release of MobileIron Core.
General limitations
Android and Android enterprise limitations
iOS and macOS limitations
Windows limitations
Enterprise Connector limitations
Go to https://community.mobileiron.com/welcome to search release notes describing usage notes and limitations

documented in previous releases. MobileIron Support credentials are required to access this site.
General limitations
This section describes third-party limitations which are common to all platforms or are platform-independent.
VSP-44987: Certificates uploaded by V1 API will not be deleted.
VSP-45032: When sending a request to devices to update a public app in the App Catalog, Core is unable to
use the app install date on the device to determine whether updates are required, if the app was recently
converted from unmanaged to managed.
Workaround: When sending a request to update a recently converted managed app, select the following option
instead: "Ignore the app install date on device".
VSP-43935: The M2600 appliance is not configured with an internal DVDROM device. Administrators are
advised to configure the Remote Management Module (RMM) feature on the IPMI interface to mount an
external media source in order to support software ISO installation and boot.
Android and Android enterprise limitations

This section describes third-party Android and Android enterprise (Android for Work) limitations.
VSP-43627: Syncing multiple activesync mailboxes on most supported Android mail clients results with only
the first mailbox allowed to sync by Core. This is not a problem if mail client is set to sync a single mailbox.

Workaround: Manually allow the mistakenly blocked ActiveSync entries on Core.
iOS and macOS limitations

This section describes third-party iOS and macOS limitations.
VSP-45761: On devices running iOS 11, 32-bit apps will no longer be supported.
VSP-46445: Administrators must re-enroll MacOS devices using iReg for devices that were installed prior to
this release, in order for Application Management to work. The re-enrollment should repush the MDM profile
with the Application Management properly assuming that the original cookies from the first enrollment have not
been deleted. If the original cookies have been deleted, then the re-enrollment will fail. The only recourse in
that case is to retire the device and re-enroll fresh.
VSP-46025: When a macOS device enrolls in DEP with a PIN, the PIN is used as the standard user password.
VSP-44781: Devices running iOS 10.10 do not support device-based licenses. Both iOS 10.10 and Core
support user-based licenses. Apple, however, has a bug that causes user-based licenses not to work. As such,
apps with user-based licenses will not work on iOS 10.10.
VSP-47182: Existing registered macOS 10.12 devices on a Core that are upgraded to 9.5.0.0 might end up
with System - iOS Enterprise AppStore SCEP and System - macOS Enterprise AppStore Identity Preference
with the Status of "Not Present" after the first check-in following the upgrade. If that happens to a device,
administrators need to manually repush each of the profiles one at a time from the Device Details for that
device in the Admin Portal and reboot the system after each push. Alternatively the device could be re-
registered.
Windows limitations
This section describes third-party Windows limitations.
VSP-45650: For the first time, BSP apps sync to Core only after 5-6 hours. Then it follows manual sync or the
configured BSP Sync Interval. In addition, if a new app is purchased on BSP portal it is reported/synced on to
Core only after 24 hours.
VSP-44908: On Windows 10 RS2 devices, when a MobileIron Bridge USB restriction is applied to devices, the
restriction takes effect only after the Windows 10 device has signed out and signed in again.
Enterprise Connector limitations

There are no known third-party limitations for Enterprise Connector in this release.

MobileIron Core upgrade information
This section describes the following upgrade information for the current release of MobileIron Core.
Support community
MobileIron Core upgrade readiness checklists
MobileIron Core upgrade paths
MobileIron Core upgrade URL
Backup MobileIron Core
MobileIron end of sale and support policy
Support community
Use the information in this section for upgrade information specific to this release. For detailed instructions on how
to upgrade MobileIron Core using this upgrade information, refer to the MobileIron Core System Manager Guide,
available on the Support Community site:
https://community.mobileiron.com/welcome
MobileIron Core upgrade readiness checklists

This section provides checklists to help you successfully complete the upgrade process for Core and Sentry
software. The checklists include:
Pre-Upgrade checklist
Upgrade checklist
Post-Upgrade checklist
Important Note for Mobile@Work for Android: Versions of Mobile@Work for Android prior to Mobile@Work
9.2.0.0 have known compatibility issues with this release of MobileIron Core and are not supported. Upgrade
Mobile@Work on all impacted devices before upgrading Core.
Pre-Upgrade checklist
Before you upgrade, we encourage you to perform the following tasks:
Check Tasks References
Prepare and plan for Core (1 - 3 hours)

downtime Sentry (5 - 20 minutes)
Review relevant Core Documentation
documentation Sentry Documentation
Connector Documentation
Apps Documentation

Check certificates Enrollment, Portal, Client certificates

MDM Cert (check a month before expires)
Local CA
Knowledge Base article: Renewing an expired local CA
certificate
Check Boot partition Refer to the following document for Boot partition information: HA Sync
- Unknown Failure and other Core performance issues due to
full tmpfs (/dev/shm) partition
Ensure there is enough Old File System (2 GB /mi and 5 GB /mi/files)

disk space New File System (10 GB /mi)
Knowledge Base article: Resizing Disk Partition of a Core Virtual
Machine
Check for new system Minimum 80 GB hard drive
requirements If there is insufficient storage, increase the available disk space
using the procedure outlined in Resizing Disk Partition of a Core
Virtual Machine
Call MobileIron support if issues persist when physical appliances
and VMs have the minimum required disk space configured
Port 8443 for MICS
Review your backup and Physical backup: built in backup, showtech all
high availability options VMware backup: VDMK backup, snapshot
High Availability: confirm HA version 2.0
Knowledge Base article: How to tell if your Core has HA 2.0
If using HA 1.0, contact MobileIron Professional Services to upgrade to
2.0
Test your connectivity to Connection to support.mobileiron.com telnet support.mobileiron.com
MobileIron 443
Set up your proxy Manually set the upgrade URL and use http instead of https
configuration (if required)
Prepare test devices Client: Get clean test devices, open client and check-in, check iOS
log
Core: Note the watchlist and label numbers

Upgrade checklist
After the pre-upgrade planning, we recommend you review the following considerations:
Check Considerations References
DB Schema and Data Run pre-validation check after downloading the repository from System
Manager. If this task fails, contact MobileIron Support.
Understand the stages Download vs. Stage for install

Reboot when the system displays:
Reboot to install https://<serverFQDN>:8443/upgrade/status
Leverage CLI upgrade MobileIron Core Command Line Interface (CLI) Reference
commands (as
appropriate)
Understand scenario Single server

options High availability:
Option 1: little downtime: 1) upgrade secondary 2) upgrade primary
Option 2: zero downtime: 1) upgrade secondary 2) failover to
secondary 3) upgrade primary 4) re-establish sync
Download guide: MobileIron Core High Availability Management Guide
Review section: HA Core Software Upgrade Procedures
Monitor the upgrade Log into the Admin Portal
Select Logs > MDM Logs > States > Waiting xml generation
pending
Monitor upgrade status using:
https://<serverFQDN>:8443/upgrade/status
Post-Upgrade checklist
The following steps are recommended after completion of the upgrade:
Testing and Log into the System Manager

troubleshooting Select Maintenance > Software Updates > Software Version
Verify that the new version is listed
DO NOT re-boot the system once the upgrade process has begun
Call MobileIron Support for further investigation
Verify services Log into the Admin Portal
Select Services > Overview
Click Verify All
Verify devices Register a new device
Re-enroll/check-in existing devices
HA system cleanup Set secondary back to secondary
Confirm sync

Check disk space availability
Before you upgrade, check disk space availability. At least 35 MB of disk space must be available in the /boot
folder for an upgrade to be successful.
If at least 35 MB of disk space is not available in the /boot folder, contact MobileIron Technical Support before
proceeding with the upgrade.
Use one of the following methods to check disk space availability:
The CLI command show system disk
The following sample output shows the available disk space in the last line. It is 15M in this example.
CORE(8.5.0.1a-6)@host.company.com#show system disk
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 181G 20G 153G 12% /
tmpfs 16G 4.0K 16G 1% /dev/shm
/dev/sda1 95M 76M 15M 84% /boot
The System Manager

1. In the System Manager, go to Maintenance > System storage.
2. Click More Details next to the System Storage bar that shows percent used.
In this example, the available disk space is 190M.
MobileIron Core upgrade paths

MobileIron recommends the following upgrade paths. The listed upgrade paths are fully tested and supported. To
determine your upgrade path and to upgrade to MobileIron Core 9.5.0.0:
1. Find your current MobileIron Core version in the first column.
2. Apply each version listed in the next column.

For example, if you are currently on Core version 8.5.0.0, you should upgrade to 8.5.0.1 > 9.1.1.0 > 9.2.0.0 >
9.4.0.0 then to 9.5.0.0.
Your current
Core version Upgrade path to Core 9.5.0.0
9.4.0.0 9.5.0.0
9.3.0.1 9.5.0.0
9.3.0.0 9.5.0.0
9.2.1.0 9.4.0.0 --> 9.5.0.0
9.2.0.0 9.4.0.0 --> 9.5.0.0
9.1.1.0 9.3.0.0 --> 9.5.0.0
9.1.0.0 9.3.0.0 --> 9.5.0.0
9.0.1.1 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
9.0.1.0 9.0.1.1 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
9.0.0.0 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
8.5.0.2 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
8.5.0.1 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
8.5.0.0 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
8.0.1.0 9.0.0.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
8.0.0.2 8.5.0.0 --> 8.5.0.1 --> 9.1.10 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
8.0.0.2c 8.0.1.0 --> 9.0.0.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
8.0.0.0 8.0.0.2 --> 8.5.0.0 --> 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
7.5.4.0 8.0.1.0 --> 9.0.0.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
7.5.3.0 7.5.4.0 --> 8.0.1.0 --> 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
7.5.2.1 8.0.0.2 --> 8.5.0.0 --> 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
7.5.2.0 8.0.0.2 --> 8.5.0.0 --> 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
7.5.1.0 8.0.0.2 --> 8.5.0.0 --> 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
7.5 7.5.1.0 --> 8.0.0.2 --> 8.5.0.0 --> 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
7.1.1 7.5.2.0 --> 8.0.0.2 --> 8.5.0.0 --> 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
7.1 7.5.1.0 --> 8.0.0.2 --> 8.5.0.0 --> 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
7.0.x 7.5.1.0 --> 8.0.0.2 --> 8.5.0.0 --> 8.5.0.1 --> 9.1.1.0 --> 9.2.0.0 --> 9.4.0.0 --> 9.5.0.0

MobileIron Core upgrade URL
Use the following URL if you specify an alternate URL:
https://support.mobileiron.com/mi/vsp/9.5.0.0-77/mobileiron-9.5.0.0-77
Backup MobileIron Core

MobileIron recommends you make a local backup of MobileIron Core before starting an upgrade. For more
information, see: MobileIron Core System Manager Guide in the section Backing up and restoring MobileIron
Core
MobileIron Core end of sale and support policy

For details on the MobileIron Core end of sale and support policy, go to:
https://community.mobileiron.com/docs/DOC-1089.
Enterprise Connector upgrade information

This section describes the following upgrade information for the current release of Enterprise Connector.
Enterprise Connector upgrade overview
Supported Enterprise Connector upgrade paths
Enterprise Connector upgrade URL
Enterprise Connector upgrade notes
Enterprise Connector upgrade overview

Use the information in this section for upgrade information specific to this release. In most cases, Enterprise
Connector is upgraded automatically after a MobileIron Core upgrade. Core upgrades include any new service
package necessary for Enterprise Connector. If Connector needs to be updated, then Core prompts Connector to
access the new package and complete an in-place upgrade. In most cases, this process completes successfully,
and Connector restarts.
If there is a problem with the in-place upgrade, then Connector makes two additional attempts to complete the
upgrade. Connector reboots before attempting to upgrade again. If the upgrade is still not successful, then
Connector reverts to the previous version and begins running in compatibility mode. In this case, you must
complete the steps in Manual Upgrade Procedure detailed in the On-Premise Installation Guide, available on
the Support Community site:

Supported Enterprise Connector upgrade paths
Direct upgrade from only the following Enterprise Connector versions to version 9.5.0.0 is supported:
9.4.0.0 --> 9.5.0.0
9.3.0.1 --> 9.5.0.0
9.3.0.0 --> 9.5.0.0
9.2.2.0 --> 9.4.0.0 --> 9.5.0.0
9.2.1.0 --> 9.4.0.0 --> 9.5.0.0
9.2.0.0 --> 9.4.0.0 --> 9.5.0.0
If you are upgrading from a version not listed here, then you need to complete one or more previous upgrades first.
See the upgrade guide for that version.
Enterprise Connector upgrade URL

Use the following URL if you specify an alternate URL:
https://support.mobileiron.com/mi/connector/9.5.0.0-77/mobileiron-9.5.0.0-77
Enterprise Connector upgrade notes

There are no Enterprise Connector upgrade notes for this release.
Documentation resources
MobileIron product documentation is available at the following locations:
MobileIron Core and related product documentation in the Support Community:
MobileIron Core and related product documentation in the Software download site:
https://support.mobileiron.com/docs/current/

Copyright 2009 - 2017 MobileIron, Inc. All Rights Reserved.
Any reproduction or redistribution of part or all of these materials is strictly prohibited. Information in this
publication is subject to change without notice. MobileIron, Inc. does not warrant the use of this publication. For
some phone images, a third-party database and image library, Copyright 2007-2009 Aeleeta's Art and Design
Studio, is used. This database and image library cannot be distributed separate from the MobileIron product.
MobileIron, the MobileIron logos and other trade names, trademarks or service marks of MobileIron, Inc.
appearing in this documentation are the property of MobileIron, Inc. This documentation contains additional trade
names, trademarks and service marks of others, which are the property of their respective owners. We do not
intend our use or display of other companies trade names, trademarks or service marks to imply a relationship
with, or endorsement or sponsorship of us by, these other companies.

Mobileiron Core and Connector 9.5.0.0 Release and Upgrade Notes

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Mobileiron Core and Connector 9.5.0.0 Release and Upgrade Notes

Caricato da

Copyright:

Formati disponibili

MobileIron Core and Connector

9.5.0.0 Release and Upgrade Notes

This document contains the following information:

Proprietary and Confidential | Do Not Distribute

New features summary

Go to https://community.mobileiron.com/welcome to search release notes describing features added to previous

MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 2

Android and Android enterprise features

MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 3

MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 4

Delegated Administration features

MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 5

Enterprise Connector features

Standalone Sentry features

Support and compatibility

MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 6

MobileIron end of sale and support policy

MobileIron Core support and compatibility

Product Supported Compatible

Enterprise Connector 9.4.0.0, 9.5.0.0 9.3.0.0

Product Supported Compatible

Reporting Database 1.7.0.0, 1.8.0.0 1.6.0.0, 1.6.0.1

MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 7

Product Supported Compatible

Atlas 1.3 Not applicable. (v1.3 has been shipping for

Product Supported Compatible

Product Supported Compatible

Standalone 9.0.2, 9.1.0 8.5.0

Integrated 6.2.1 6.1.1, 6.2.0

Product Supported Compatible

iOS 9.0 to 10.3.3 8.0

Mobile@Work 8.6.0, 9.0.1, 9.1.0, 9.5.0 8.0.2

Docs@Work 2.2.0, 2.2.1, 2.2.2 2.0.0, 2.1.0, 2.1.1, 2.1.2

Web@Work 2.0.0 1.9.2, 1.9.3

PIV-D Entrust app for iOS 1.3 1.1, 1.2

Tunnel 1.0.6, 2.2.0 2.1.1

MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 8

Email+ 2.4.0, 2.4.1, 2.5.0 2.1.0 to 2.3.4

Help@Work 2.1.0, 2.1.1 2.0.2

Insight 5.1.1 Not applicable since all listed versions are

Product Supported Compatible

macOS/OS X macOS10.10 Not applicable since all listed versions are

Product Supported Compatible

Web@Work 2.0.0, 2.0.1 Not applicable. (The previous version,

Apps@Work Not applicable. (Apps@Work is Not applicable. (Apps@Work is part of

PIV-D Entrust app for 1.0 Not applicable.

MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 9

Tunnel 1.5.0, 2.0.0 1.4.0

Email+ 2.5.0.0 (AppConnect enabled) 2.0.0.0 to 2.4.0.0 (AppConnect enabled)

Help@Work 2.1.0, 2.1.1 2.0.2

Insight 5.1.1 Not applicable since only the listed version is

Product Supported Compatible

Apps@Work 9.5.0.5 Not applicable since only the listed version is

Tunnel 1.2.0 1.1.0

Browser Supported Compatible

Internet Explorer 11 8*, 9*, 10*

Edge Not supported Not compatible

Chrome >59 >59*

Firefox >=25 < 25*

MobileIron Core and Connector 9.5.0.0 Release and Upgrade Notes | 10

Safari Not supported 10.1*

Chrome - iPad Not supported Not compatible

Safari - iPad Not supported Not compatible

Internet Explorer 11 8, 9, 10*