As well as Mailboxes and Archives, Public Folders are another place you may want to use EWS to enumerate Items to do some enhanced reporting. Building on the Enumerate script from the last two post, this post will cover how to modify this script to enable access Public Folder and Public Folder Items.
EWS Changes
To change the Mailbox code we have to access public folders requires one big change in the Mailbox script we have the line
in the FolderIdFromPath function. To access a Public folder we need to change this to
And that's pretty much it apart from renaming the function to PublicFolderIdFromPath this is all you have to do. One thing you can't do with Public Folders vs what you can do with Mailboxs and Archive folders is do a DeepTraversal of all the folders in a folder hierarchy. For the basic enumeration script this isn't a big deal because all the searches are done at a shallow level.
Exchange 2013 up
For Exchange 2013,2016 and Exchange Online there is one other change you should make to this script which is to add the X-AnchorHeader and X-PublicFolderMailbox headers to ensure routing happens correctly as per https://msdn.microsoft.com/en-us/library/office/dn818490(v=exchg.150).aspx and https://msdn.microsoft.com/en-us/library/office/dn818491(v=exchg.150).aspx. It gets a little complicated here but because the Hierarchy and content maybe located in a different Public Folder Mailboxes you have to use 2 different discovery mechanisms both the EWS Managed API discover like
and a POX Autodiscover (plain old XML) method like
I've put a full copy of this enumerate script up on git hub https://github.com/gscales/Powershell-Scripts/blob/master/EnumerateItemsInPublicFolder.ps1
For one example of what you can do with it if we take the sample from the last post on ItemAge we can create an ItemAge script for public folder items. eg
https://github.com/gscales/Powershell-Scripts/blob/master/PublicFolderItemAge.ps1
EWS Changes
To change the Mailbox code we have to access public folders requires one big change in the Mailbox script we have the line
$folderid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::MsgFolderRoot,$SmtpAddress)
in the FolderIdFromPath function. To access a Public folder we need to change this to
$folderid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::PublicFoldersRoot)
And that's pretty much it apart from renaming the function to PublicFolderIdFromPath this is all you have to do. One thing you can't do with Public Folders vs what you can do with Mailboxs and Archive folders is do a DeepTraversal of all the folders in a folder hierarchy. For the basic enumeration script this isn't a big deal because all the searches are done at a shallow level.
Exchange 2013 up
For Exchange 2013,2016 and Exchange Online there is one other change you should make to this script which is to add the X-AnchorHeader and X-PublicFolderMailbox headers to ensure routing happens correctly as per https://msdn.microsoft.com/en-us/library/office/dn818490(v=exchg.150).aspx and https://msdn.microsoft.com/en-us/library/office/dn818491(v=exchg.150).aspx. It gets a little complicated here but because the Hierarchy and content maybe located in a different Public Folder Mailboxes you have to use 2 different discovery mechanisms both the EWS Managed API discover like
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2013_SP1 $AutoDiscoverService = New-Object Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService($ExchangeVersion); $creds = New-Object System.Net.NetworkCredential($Credentials.UserName.ToString(),$Credentials.GetNetworkCredential().password.ToString()) $AutoDiscoverService.Credentials = $creds $AutoDiscoverService.EnableScpLookup = $false; $AutoDiscoverService.RedirectionUrlValidationCallback = {$true}; $AutoDiscoverService.PreAuthenticate = $true; $AutoDiscoverService.KeepAlive = $false; $gsp = $AutoDiscoverService.GetUserSettings($MailboxName,[Microsoft.Exchange.WebServices.Autodiscover.UserSettingName]::AutoDiscoverSMTPAddress);
and a POX Autodiscover (plain old XML) method like
$AutoDiscoverRequest = [System.Net.HttpWebRequest]::Create($AutoDiscoverService.url.ToString().replace(".svc",".xml")); $bytes = [System.Text.Encoding]::UTF8.GetBytes($auDisXML); $AutoDiscoverRequest.ContentLength = $bytes.Length; $AutoDiscoverRequest.ContentType = "text/xml"; $AutoDiscoverRequest.UserAgent = "Microsoft Office/16.0 (Windows NT 6.3; Microsoft Outlook 16.0.6001; Pro)"; $AutoDiscoverRequest.Headers.Add("Translate", "F"); $AutoDiscoverRequest.Method = "POST"; $AutoDiscoverRequest.Credentials = $creds; $RequestStream = $AutoDiscoverRequest.GetRequestStream(); $RequestStream.Write($bytes, 0, $bytes.Length); $RequestStream.Close(); $AutoDiscoverRequest.AllowAutoRedirect = $truee; $Response = $AutoDiscoverRequest.GetResponse().GetResponseStream() $sr = New-Object System.IO.StreamReader($Response) [XML]$xmlReposne = $sr.ReadToEnd() if($xmlReposne.Autodiscover.Response.User.AutoDiscoverSMTPAddress -ne $null) { write-host ("Public Folder Content Routing Information Header : " + $xmlReposne.Autodiscover.Response.User.AutoDiscoverSMTPAddress) $service.HttpHeaders["X-AnchorMailbox"] = $xmlReposne.Autodiscover.Response.User.AutoDiscoverSMTPAddress $service.HttpHeaders["X-PublicFolderMailbox"] = $xmlReposne.Autodiscover.Response.User.AutoDiscoverSMTPAddress }
I've put a full copy of this enumerate script up on git hub https://github.com/gscales/Powershell-Scripts/blob/master/EnumerateItemsInPublicFolder.ps1
For one example of what you can do with it if we take the sample from the last post on ItemAge we can create an ItemAge script for public folder items. eg
https://github.com/gscales/Powershell-Scripts/blob/master/PublicFolderItemAge.ps1