Skip to main content

Enumerating Public Folders using EWS and reporting on Rules and Folder Stats

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 can take a considerable amount of time.

The following Script does this enumeration for all the Public Folders (that the Mailbox that is running the script) has access to, it checks to see if there are any Rules that are Active or Disabled, and also produces a basic stats report of the Number of Items, FolderSize and also the PidTagLocalCommitTimeMax time which should give you the last time the items in the folder where last changed. eg it produces something like

With this base you can add-in whatever you want to do with each folder depending on your particular requirements.

I've put a copy of this script on GitHub here

To Run the script you need to pass in a Mailbox this is used to connect to CAS server and then connect eg

Enum-PublicFolders -MailboxName

Popular posts from this blog

Downloading a shared file from Onedrive for business using Powershell

I thought I'd quickly share this script I came up with to download a file that was shared using One Drive for Business (which is SharePoint under the covers) with Powershell. The following script takes a OneDrive for business URL which would look like This script is pretty simple it uses the SharePoint CSOM (Client side object Model) which it loads in the first line. It uses the URI object to separate the host and relative URL which the CSOM requires and also the SharePointOnlineCredentials object to handle the Office365 SharePoint online authentication. The following script is a function that take the OneDrive URL, Credentials for Office365 and path you want to download the file to and downloads the file. eg to run the script you would use something like ./spdownload.ps1 '

Export calendar Items to a CSV file using EWS and Powershell

Somebody asked about this last week and while I have a lot of EWS scripts that do access the Calendar I didn't have a simple example that just exported a list of the Calendar events with relevant information to a CSV file so here it is. I've talked on this one before in this howto  but when you query the calendar folder using EWS you need to use a CalendarView which will expand any recurring appointments in a calendar. There are some limits when you use a calendarview in that you can only return a maximum of 2 years of appointments at a time and paging will limit the max number of items to 1000 per call. So if you have a calendar with a very large number of appointments you need to break your query into small date time blocks. In this example script I'm just grabbing the next 7 days of appointments if you want to query a longer period you need to adjust the following lines (keeping in mind what I just mentioned) #Define Date to Query $StartDate = (Get-Date) $EndDate

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why I wrote th
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.