Test-ActiveSyncConnectivity cmdlet can come handy here: Issue with a single server: It is important for us to understand if the issue is happening for all users or if it is isolated for users on a single mailbox server or even a mailbox database. Note: ExRCA doesn’t work all the time, so have a test mobile device handy and the website is solely owned by Microsoft. If this shows a pass, I would put the blame on the device and move forward. Once we ensure all is well with the user, navigate to and run a test for ActiveSync and give the user credentials and click Next. Have the user flip Wifi and 3G network to ensure the issue is not caused because of internet connection drop on the device or in other words, before proceeding have the user access a couple of websites on the mobile browser. Navigate to the user location in ADSIEdit and open his properties: 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”.
#EXPORT A LIST OF USERS FROM IIS LOG FILE SERIES#
Read event logs and filter MSExchange ActiveSync event in 10xx series.Look at CPU utilization for w3wp.exe on all CAS servers.
Confirm Authentication settings on IIS VDir’s for CAS and MBX roles.Read IIS logs and look at the error’s if any.Isolate the issue be for user, device, server or organization wide.My way of troubleshooting flows this way which I will explain in detail: Recently I had an issue where users on one of the Exchange 2007 servers “ONLY” weren’t able to sync their mobile device. In this article I will try cover my way of troubleshooting Exchange ActiveSync issues from Server side and client side.
0 kommentar(er)
