A script to troubleshoot issues with Exchange ActiveSync

re: A script to troubleshoot issues with Exchange ActiveSync

Konstantin Papadakis - MSFT — Mon, 26 Mar 2012 18:12:23 GMT

@Frenchie: The best thing to do is to remove the partnership from the device thus stopping the device from attempting to sync at all. Now that is not the best thing for the end user. If possible identify what is wrong with the device (know build issue and upgrade, user workflow education, 3rd party installed on device that is causing the issue). Also in some organizations cannot afford to wait for a user to disable the device so there are ways with reverse proxy server/device (Ex. Threat Management Gateway) to block the User or User-Agent (if known bad device). This will allow the Exchange environment to be functional and give the admin time to work out the issues with the suspect device.

re: A script to troubleshoot issues with Exchange ActiveSync

Frenchie — Thu, 22 Mar 2012 23:48:18 GMT

I ran this in my organization, I have about 100 users that are well over 1k hits, some users had 40k, 50k, 100k, even 175 hits, all of these requests for 'Sync' commands. How do we block this? the 175k was an iPad on the latest iOS 5 software..Some of these devices are essentially sending a 'Sync' command every second if not 3 times every second. I don't think throttling helps as this basically stops 'concurrent' connections, however how do we stop devices so they only send 'Sync' command or we only 'accept' sync commands on particular intervals so they do not send 100k requests in 24 hours for example. This is killing CAS.

re: A script to troubleshoot issues with Exchange ActiveSync

Vikas Sukhija — Sat, 10 Mar 2012 22:59:18 GMT

This is fantastic, I have clubbed it with mine script to troubleshoot fast growing transactional logs

exchangedomino.wordpress.com/.../troubleshooting-fast-growing-transactional-logs-part-2

re: A script to troubleshoot issues with Exchange ActiveSync

House of brokers — Sat, 03 Mar 2012 07:49:15 GMT

If the hits (requests) are above 1500, there could be an issue on the device or environment. In that case, the device & its user’s activity should be further investigated." This information is very important and useful which gives the idea about a typical user behavior and the user profile.

<a href="markething.org/">House of brokers</a>

re: A script to troubleshoot issues with Exchange ActiveSync

saadrooking — Sun, 26 Feb 2012 19:11:41 GMT

Usually if a device is sending over 1000 requests per day, we consider this ‘high usage’. If the hits (requests) are above 1500, there could be an issue on the device or environment. In that case, the device & its user’s activity should be further investigated." This information is very important and useful which gives the idea about a typical user behavior and the user profile.

口臭

http://mouthfresher.com/

re: A script to troubleshoot issues with Exchange ActiveSync

burnham boilers — Thu, 23 Feb 2012 11:43:40 GMT

Turns out that he had a bad calendar entry that had generated over 11,000 meeting requests in 11 hours and his iPhone was attempting to sync over 18 times per minute to resolve this meeting request. We turned off his calendar sync and the traffic died off immediately.

<a href="bestburnhamboilers.net">burnham boilers</a>

re: A script to troubleshoot issues with Exchange ActiveSync

Benoit Boudeville — Fri, 10 Feb 2012 11:48:15 GMT

Also line 698:

Replace line:

Write-Host "Trying to find IIS logs from this date: $title"

With:

Write-Host "Trying to find IIS logs from this date: $filterdate"

re: A script to troubleshoot issues with Exchange ActiveSync

Benoit Boudeville — Fri, 10 Feb 2012 11:31:21 GMT

Several bugs in the script:

Line 721: replace with

if ($IISLogs.Count -gt 1) {

Also I suggest to delcare IISLogs with type [String[]] rather than [array] (line 48); this makes the script deal better with passed array of paths.

In Create-HTML, around line 593-602 - the function works but this is somehow by chance :) :

Replace

$html = ConvertTo-HTML -Head $HTMLHeader -Body $body

$body = "<h2><TT>Exchange ActiveSync Report on $title<TT></h2><TT>For additional <b>unfiltered</b> information on device hits please refer to the CSV $outfile</TT><BR /><BR />"

if ($table.count -le 0) {

$body += "No Devices have excited the Minimum Number of Hits (<b>$MinimumHits</b>)"

}

else { $body += ($table | Select $HTMLCSVHeaders.split(",") | ConvertTo-HTML -Fragment) }

$body += "</body></html>"

return ($HTMLHeader += $body)

with

$body = "<h2><TT>Exchange ActiveSync Report on $title<TT></h2><TT>For additional <b>unfiltered</b> information on device hits please refer to the CSV $outfile</TT><BR /><BR />"

if ($table.count -le 0) {

$body += "No Devices have excited the Minimum Number of Hits (<b>$MinimumHits</b>)"

}

else { $body += ($table | Select $HTMLCSVHeaders.split(",") | ConvertTo-HTML -Fragment) }

$body += "</body></html>"

ConvertTo-HTML -Head $HTMLHeader -Body $body

re: A script to troubleshoot issues with Exchange ActiveSync

Tunisian man — Thu, 09 Feb 2012 16:55:13 GMT

good job, Thank you

re: A script to troubleshoot issues with Exchange ActiveSync

dontcallmevic — Wed, 08 Feb 2012 15:12:37 GMT

@Brian: Thanks for the date parameters -- it works perfectly!

This script was a lifesaver for our Exchange server last week when I found the post. Log files were being generated like crazy, filling up the volume and threatening to crash the server. I could use ExMon to see which user was generating the logs but without your script I didn't know why. Turns out that he had a bad calendar entry that had generated over 11,000 meeting requests in 11 hours and his iPhone was attempting to sync over 18 times per minute to resolve this meeting request. We turned off his calendar sync and the traffic died off immediately.

Again, thanks for the info!