SUMMARY
The Exchange ActiveSync Protocol has the ability to enforce policies on devices. MailEnable provisions devices with a very simple policy by default, however, it is possible to configure additional policy settings for devices.
DETAIL
By default, MailEnable will issue a basic policy
document to clients that simply tells the device not to configure a device
password for the EAS account.
It is as
follows:
<EASProvisionDoc>
<DevicePasswordEnabled>0</DevicePasswordEnabled>
</EASProvisionDoc>
MailEnable will look for and create a file
ActiveSync.Policy.Xml that can be edited according to your requirements (by
default, the file will contain the basic policy outlined above).
The file
will be created in your MailEnable CONFIG directory, MailEnable BIN directory or
in the [System32]\inetsrv directory depending on whether you are using IIS or
the Synchronisation service to provide ActiveSync.
Microsoft provides
details on the settings that are available here:
http://msdn.microsoft.com/en-us/library/dd299443(v=exchg.80).aspx
An example of a more sophisticated policy
document
follows:
<EASProvisioningDoc>
<DevicePasswordEnabled>1</DevicePasswordEnabled>
<AlphanumericDevicePasswordRequired>1</AlphanumericDevicePasswordRequired>
<PasswordRecoveryEnabled>1</PasswordRecoveryEnabled>
<RequireStorageCardEncryption>1</RequireStorageCardEncryption>
<AttachmentsEnabled>1</AttachmentsEnabled>
<MinDevicePasswordLength/>
<MaxInactivityTimeDeviceLock>333</MaxInactivityTimeDeviceLock>
<MaxDevicePasswordFailedAttempts>8</MaxDevicePasswordFailedAttempts>
<MaxAttachmentSize/>
<AllowSimpleDevicePassword>0</AllowSimpleDevicePassword>
<DevicePasswordExpiration/>
<DevicePasswordHistory>0</DevicePasswordHistory>
</EASProvisioningDoc>
MORE
INFORMATION
Microsoft ActiveSync Device Provisioning: http://msdn.microsoft.com/en-us/library/dd299443(v=exchg.80).aspx
Product: | MailEnable (All Versions) |
Category: | Configuration |
Article: | ME020573 |
Module: | HTTPMail |
Keywords: | Exchange,ActiveSync,Policy |
Class: | HOWTO: Product Instructions |
Revised: | Wednesday, May 4, 2016 |
Author: | MailEnable |
Publisher: | MailEnable |