Thursday, April 28, 2016

EWS Bascis : Accessing Public Folders and Public Folder Content

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

$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




2 comments:

VVA said...

I'm using EWS API GetDelegate as shown below, but it is not returning all the delegates.

Mailbox mailbox = new Mailbox(User1@exdev2016.local);
DelegateInformation result = service.GetDelegates(mailbox, false);

I've given a delegate access to User1 from User3 and User4 user accounts. I expected GetDelegates to return User3 and User4 but output has no delegates. Response is below


NoError
DelegatesOnly


Can you please let me know if I'm missing anything?

Anthony said...

Glen! You're my only hope! I'm dying here!

first, let me say that your documentation of powershell EWS and exchange is absolutely incredible; i wish this level of information was available for all powershell functions. i applaud your work and dedication to this.

my problem: i run your EnumerateItemsInPublicFolder script, but I'm getting "Folder not found" every time, even when providing the base folder like "\\public folders - user@domain.com"

why!?

when i debug just before it errors out (at line 226: if($tfTargetFolder -ne $null){) i can see that $findFolderResults is empty, so i check the 3 arguments passed into $service.FindFolders(...) and they all have good values, but nothing is being found and it makes no sense.

could you shed some light on why that might be?

ps. also, is there another, more reliable way of getting in contact with you?