The default W3C fields enabled for logging do vary between IIS 6.0 and 7.0/7.5 ( IIS 7.0 has the same fields as 7.5). Note: The script works with IIS logs on Exchange 2010, Exchange 2007 and Exchange 2003 servers.Īll communication between mobile devices using EAS protocol and Microsoft Exchange is logged in IIS Logs on CAS/ FE servers in W3C format. It also provides an auto-monitoring feature which you can use to receive e-mail notifications. You can use it as a tool to establish a baseline during periods of normal EAS activity and then use that for comparison and reporting when things sway in other directions. The script makes it easier to identify users with multiple EAS devices. Using this script you can easily & quickly drill into your users' EAS activity, which can be a major task when faced with IIS logs that can get up to several gigabytes in size. The purpose of this post is to introduce everyone in Exchange community to a new PowerShell script that can be utilized to identify devices causing resource depletion issue, help in spotting performance trends and automatically generate reports for continuous monitoring. As referenced in the article above, you can use Log Parser to extract useful statistics from IIS logs (see note below), but most administrators do not have the time & expertise to draft queries to extract such information from lengthy logs. Trying to track down which devices are causing resource depletion issues on Exchange 2010/2007 Client Access server (CAS) or Exchange 2003 Front-end (FE) server is not an easy task. Managing mobile devices & balancing available server resources among different types of clients can be a daunting challenge for IT administrators. This can cause such devices to attempt to connect & sync with the mailbox more than 60 times in a minute, killing battery life on the device and causing performance issues on server. #MICROSOFT ACTIVESYNC 3.7 TROUBLESHOOTING GUIDE HOW TO#Another example could be some devices that do not understand how to handle a ‘mailbox full’ response from the Exchange server, resulting in several tries to reconnect. #MICROSOFT ACTIVESYNC 3.7 TROUBLESHOOTING GUIDE FULL#We have documented this issue with possible mitigations in the following KnowledgeBase article:Ģ469722 Unable to connect using Exchange ActiveSync due to Exchange resource consumptionĪ recent example of this issue was Apple iOS 4.0 devices retrying a full sync every 30 seconds (see TS3398). The worst outcome of such a situation is that the server also becomes unavailable to other users who may not be using EAS protocol to connect. The Exchange support team relatively frequently receives cases where mobile devices using Exchange ActiveSync (EAS) protocol send too many requests to Exchange server resulting in a situation where server runs out of resources, effectively causing a ‘denial of service’ (DOS) attack. #MICROSOFT ACTIVESYNC 3.7 TROUBLESHOOTING GUIDE DOWNLOAD#You can download the script, which has been attached to this blog post.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |