Glen's Exchange and Office 365 Dev Blog

Tracking the bewildering array of clients and different Internet browsers that are being used to send email on Exchange can be an interesting challenge especially when your clients are in the cloud. One Mapi property that gets set on the SentItem in the senders Mailbox can help answer some of these questions where logs may not be available. The Named Mapi property clientinfo eg So if you write a script that accesses this property on messages in the SentItems folder you can build a report of the different sending methods that are being used and also different properties such as the browser version from the agent string being stored eg something like this I've put a script on GitHub here https://github.com/gscales/Powershell-Scripts/blob/master/GetMailUserAgentsv2.ps1  that can mine the data in the property correctly taking into account the ; used as a separator while also dealing with data enclosed in ( ) (it does this by just doing a character by character parse rather th

When people mention Public Folders in Exchange a quote from Mark Twain often comes to mind "the reports of my death are greatly exaggerated", one often thinks the same when people write such things about email.  While Groups in Office 365 offer a compelling alternative, Public Folders are still things Admins need to deal with and Migrate occasionally. While the Exchange Management Shell cmdlets for reporting on Public Folders have improved a lot in Exchange 2013 you may still have the need from time to time to want to do some more in-depth analysis of what's happening in your Public Folders which is where EWS can come in very useful. The one big difference to reporting on folders in a Public Folder Tree vs doing the same thing in a Mailbox is that in a Public Folder tree you can't do a Deep Traversal. This means to report on Public Folders you need to enumerate the child folders of each parent folder with a separate EWS call. For very large Public Folder trees this