-->

Applies to: Exchange Server 2013

ActiveSync email supports 'push' where email is automatically transmitted to a mobile device as soon as it is received by MDaemon. When a device is configured for IMAP, email will arrive based on a scheduled collection (eg. Every 5 minutes) you define on the device. For example, Thunderbird cannot support Outlook.com using the EAS protocol and it can’t access a Microsoft Exchange account natively without an addin. Thunderbird could access an Exchange account via either the Imap or POP protocols but that is different then accessing the server using the native Exchange protocol. Exchange ActiveSync (MobileSync) vs Good Old IMAP + SMTP Many years ago, it used to be that if you had a cell phone that had an email program included, you could configure using IMAP and SMTP to allow you to check email and send email. Just like how a desktop email program worked.

Learn about the Exchange ActiveSync client protocol for Exchange Server 2013. You'll learn about the features of Exchange ActiveSync including security features, the things you can manage, how to make it secure, and how to avoid problems synching to Windows Phone 7.

Tip

Microsoft Exchange Activesync

This topic is for admins. Want to set up your Windows Phone, iOS, or Android device to access your Office 365 or Exchange Server mailbox? Check out the following topics.

Exchange ActiveSync is a client protocol that lets you synchronize a mobile device with your Exchange mailbox. Exchange ActiveSync is enabled by default when you install Microsoft Exchange 2013.

Overview of Exchange ActiveSync

Exchange ActiveSync is a Microsoft Exchange synchronization protocol that's optimized to work together with high-latency and low-bandwidth networks. The protocol, based on HTTP and XML, lets mobile phones access an organization's information on a server that's running Microsoft Exchange. Exchange ActiveSync enables mobile phone users to access their email, calendar, contacts, and tasks, and to continue to access this information while they're working offline.

Note

Exchange ActiveSync does not support shared mailboxes or delegate access.

Important

Windows Phone 7 mobile phones support only a subset of all Exchange ActiveSync mailbox policy settings. For a complete list, see Windows Phone 7 Synchronization.

Features in Exchange ActiveSync

Exchange ActiveSync provides the following:

• Support for HTML messages

• Support for follow-up flags

• Conversation grouping of email messages

• Ability to synchronize or not synchronize an entire conversation

• Synchronization of Short Message Service (SMS) messages with a user's Exchange mailbox

• Support for viewing message reply status

• Support for fast message retrieval

• Meeting attendee information

• Enhanced Exchange Search

• PIN reset

• Enhanced device security through password policies

• Autodiscover for over-the-air provisioning

• Support for setting automatic replies when users are away, on vacation, or out of the office

• Support for task synchronization

• Direct Push

• Support for availability information for contacts

Managing Exchange ActiveSync

By default, Exchange ActiveSync is enabled. All users who have an Exchange mailbox can synchronize their mobile device with the Microsoft Exchange server.

You can perform the following Exchange ActiveSync tasks:

• Enable and disable Exchange ActiveSync for users

• Set policies such as minimum password length, device locking, and maximum failed password attempts

• Initiate a remote wipe to clear all data from a lost or stolen mobile phone

• Run a variety of reports for viewing or exporting into a variety of formats

• Control which types of mobile devices can synchronize with your organization through device access rules

Imap Settings For Microsoft Exchange

Security in Exchange ActiveSync

You can configure Exchange ActiveSync to use Secure Sockets Layer (SSL) encryption for communications between the Exchange server and the mobile device.

Managing mobile device access in Exchange ActiveSync

You can control which mobile devices can synchronize. You do this by monitoring new mobile devices as they connect to your organization or by setting up rules that determine which types of mobile devices are allowed to connect. Regardless of the method you choose to specify which mobile devices can synchronize, you can approve or deny access for any specific mobile device for a specific user at any time

Device security features in Exchange ActiveSync

In addition to the ability to configure security options for communications between the Exchange server and your mobile devices, Exchange ActiveSync offers the following features to enhance the security of mobile devices:

• Remote wipe: If a mobile device is lost, stolen, or otherwise compromised, you can issue a remote wipe command from the Exchange Server computer or from any Web browser by using Outlook Web App. This command erases all data from the mobile device.

• Device password policies: Exchange ActiveSync lets you configure several options for device passwords.

  Warning

  The iOS7 fingerprint reader technology cannot be used as a device password. https://omgtennessee.netlify.app/shiva-and-dionysus-pdf-to-jpg.html. If you choose to use the iOS7 fingerprint reader, you'll still need to create and enter a device password if the mobile device mailbox policy for your organization requires a device password.

  The device password options include the following:

  • Minimum password length (characters): This option specifies the length of the password for the mobile device. The default length is 4 characters, but as many as 18 can be included.

  • Minimum number of character sets: Use this text box to specify the complexity of the alphanumeric password and force users to use a number of different sets of characters from among the following: lowercase letters, uppercase letters, symbols, and numbers.

  • Require alphanumeric password: This option determines password strength. You can enforce the usage of a character or symbol in the password in addition to numbers.

  • Inactivity time (seconds): This option determines how long the mobile device must be inactive before the user is prompted for a password to unlock the mobile device.

  • Enforce password history: Select this check box to force the mobile phone to prevent the user from reusing their previous passwords. The number that you set determines the number of past passwords that the user won't be allowed to reuse.

  • Enable password recovery: Select this check box to enable password recovery for the mobile device. Administrators can use the Get-ActiveSyncDeviceStatistics cmdlet to look up the user's recovery password.

  • Wipe device after failed (attempts): This option lets you specify whether you want the phone's memory to be wiped after multiple failed password attempts.

• Device encryption policies: There are a number of mobile device encryption policies that you can enforce for a group of users. These policies include the following:

  • Require encryption on device: Select this check box to require encryption on the mobile device. This increases security by encrypting all information on the mobile device.

  • Require encryption on storage cards: Select this check box to require encryption on the mobile device's removable storage card. This increases security by encrypting all information on the storage cards for the mobile device.

Windows Phone 7 synchronization

If you have Windows Phone 7 mobile devices in your organization, these devices will experience synchronization problems if certain Mobile Device mailbox policy properties are configured. To allow Windows Phone 7 mobile phones to synchronize with an Exchange mailbox, either set the AllowNonProvisionableDevices property to true or configure only the following Mobile Device mailbox policy properties:

• PasswordRequired

• MinPasswordLength

• IdleTimeoutFrequencyValue

• DeviceWipeThreshold

  It was changed to ‘Sorcerer’s’ for the US printing by the US publishers, but I use ‘Philosopher’s’ because it’s the title the author intended. Harry potter and the philosophers stone pdf indonesia. Cache said this on • Cache, the books are originally British, and ‘Philosopher’s Stone’ is the original title.

• AllowSimplePassword

• PasswordExpiration

• PasswordHistory

• DisableRemovableStorage

• DisableIrDA

• DisableDesktopSync

• BlockRemoteDesktop

• BlockInternetSharing

#1 .....Apparently, there are many functions in Outlook 2013 that are not supported by EAS, such as categories, and importing of contacts, etc. This is causing me a lot of frustration in regards to importing my contacts from Gmail and the like, so I'm wondering what the are to using an EAS account as opposed to IMAP. Is there some reason she set it up as an EAS account?

#2 Also, the reason she had trouble in the first place was because the default system for setting up accounts wouldn't work, so it had to be done manually. Why is that?

#1a - Simple solution to importing contacts to your Outlook.com EAS account - import them using the Outlook.com web-interface. There are also ways to do it within Outlook but none at the moment as quick as doing it directly to the Outlook.com account. However, that does require that you know the exact contact field names to use in the data file holding your contacts

List of Import Contact Field Names for Outlook.com Using CSV
http://www.contactgenie.info/outlook-com-import-field-names

#1b - Each protocol used to access an email account has different capabilities (i.e. POP and IMAP do not sync contact/calendar info)

Understanding Email Protocols (POP, Imap, MAPI, EAS)
http://www.contactgenie.info/understanding-email-protocols-pop-imap-mapi-eas-exchange

#1c - Outlook.com accounts are being migrated to the Office 365 backend Exchange server platform where virtually all the 'aggravations' will be resolved. This is 'in progress' now being completed in stages (there are several hundred million Outlook.com accounts involved). The target is year-end but could spill over into 2016 depending on what, if any, problems are encountered,

#2 - No one can answer your 'why' question without knowing at least the most minimal of details of your particular circumstance in terms of what problems were encountered to start with.