Limitations

This release does not introduce any new limitation. The following are some existing limitations:

Manual ActiveSync operations with Office 365

VS-8338, VS-8340: Use the MobileIron Core Admin Portal to do the manual ActiveSync operations block, allow, wipe, and remove. Do not do these operations using Microsoft Exchange or Office 365 directly.

Mixing Microsoft Exchange Servers

VS-8217: Consider the case when you have a mixed Exchange environment where, for example, some Exchange servers are Exchange 2013 (On premise) and some are Exchange 2010. Some PowerShell commands that Integrated Sentry uses do not work across Exchange versions. To workaround this PowerShell limitation, do the following:

1. Group all Exchange 2010 users into one LDAP group.
2. Place an Integrated Sentry in the Exchange 2010 environment.
3. When you configure this Integrated Sentry on the MobileIron Core, specify this LDAP group in the Selected list for Apply To LDAP Groups.
4. Group all Exchange 2013 (On premise) users into another LDAP group.
5. Place an Integrated Sentry in the Exchange 2013 (On premise) environment.
6. When you configure this Integrated Sentry on the MobileIron Core, specify this LDAP group in the Selected list for Apply To LDAP Groups.

PowerShell session limits

VS-8254: Office 365 normally has a limit of three PowerShell sessions. Integrated Sentry requires one PowerShell session to communicate with Office 365. More than two other concurrent remote PowerShell sessions with Office 365 can cause problems for Integrated Sentry.

If the problem occurs, MobileIron Core displays an error for the Integrated Sentry entry at Settings > Sentry. The error includes the following text:

“The user is allowed a maximum number of three concurrent shells, which has been exceeded. Close existing shells or raise the quota for this user.”

Use the following workarounds:

  • Dedicate a PowerShell session to each Integrated Sentry.
  • If you use a secondary Integrated Sentry as a backup, also dedicate a PowerShell session to it.
  • If you open another remote PowerShell session with Office 365, be sure to cleanly shut down the session when you are done with it.
  • If necessary, contact Microsoft to increase your PowerShell quota.