![eas em client 7 eas em client 7](https://www.emclient.com/sitecontrol/en/images/screenshots/emc_img_attachfolderaszip.png)
Let’s confirm that it is indeed set that way. MsExchOmaAdminWirelessEnable = 7 = 111 = All options disabled. MsExchOmaAdminWirelessEnable = 5 = 101 = Option 1 enabled and Option 2,3 disabled MsExchOmaAdminWirelessEnable = 4 = Option 1 and 3 enabled and Option 2 disabled MsExchOmaAdminWirelessEnable = 3 = 011 = Option 2 enabled. MsExchOmaAdminWirelessEnable = 2 = 010 = Option 2 and option 3 enabled (option 3 requires 2). MsExchOmaAdminWirelessEnable = 1 = 001 = Option 1 and option 2 enabled. If msexchOMAAdminWirelessEnable is set to a number, it will cause EAS issues. Ideally, if this all set to enable, the attribute “ msexchOMAAdminWirelessEnable“will be in ADSIEdit. Navigate to Active Directory Users and Computers à Search for the user à Exchange Feature tab à Issue with one single user only: First thing I would look for is to check the OMA AD property enabled or not. Let’s split this into 4 different scenario and the issue should be isolated to one of these: This is the primary focus area or we will be going in circles. Isolate the issue be for user, device, server or organization wide Confirm ADPermission for internet facing CAS servers on “ms-Exch-EPI-Token-Serialization”.
#Eas em client 7 series#
![eas em client 7 eas em client 7](https://www.emclient.com/sitecontrol/en/images/screenshots/emc_img_themeeditor_settingsapplycustom.png)
In this article I will try cover my way of troubleshooting Exchange ActiveSync issues from Server side and client side.