Skip to main content

Showing the Calendar Configuration of a Mailbox or Meeting Room using EWS

When you configure Calendar processing settings in Exchange either using the Exchange Administrator Centre via the Exchange Management Shell (Set-CalendarProcessing) many of these setting get held in a FAI (Folder Associated Item) in the Calendar Folder of the Mailbox in question. In EWS you can access these configuration objects using the UserConfiguration operation and classes.

The Calendar settings are stored in the Roaming Dictionary format to store each of the different Key and Value pairs. For some of the settings like the bookin policy (In-policy meeting requests) and (Out-of-policy meeting requests) these are stored as an array of ExchangeDn's.

I've put together a script cmdlet called Show-CalendarSettings that can dump out the Roaming dictionary setting for a Calendar Configuration object using EWS. And also for the BookIn and RequestIn policy it will loop through each of the ExchangeDn's in the array and try to resolve each of the entries via ResolveName . All the configuration information is written to file and the results of the ResolveName is written along with the result (eg valid if it resolves couldn't resolve if not). eg it produces an output like




  I've put the script on GitHub here https://github.com/gscales/Powershell-Scripts/blob/master/DumpCalSettings.ps1 and the script itself look like

function Show-CalendarSettings
{
    param( 
     [Parameter(Position=0, Mandatory=$true)] [string]$MailboxName,
  [Parameter(Position=1, Mandatory=$true)] [System.Management.Automation.PSCredential]$Credentials,
  [Parameter(Position=2, Mandatory=$false)] [switch]$useImpersonation,
  [Parameter(Position=3, Mandatory=$false)] [string]$url
    )  
  Begin
 {
  $service = Connect-Exchange -MailboxName $MailboxName -Credentials $Credentials
  if($useImpersonation.IsPresent){
   $service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
  }
  # Bind to the Calendar Folder
  $folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Calendar,$MailboxName)   
  $Calendar = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)
  $UsrConfig = [Microsoft.Exchange.WebServices.Data.UserConfiguration]::Bind($service, "Calendar", $Calendar.Id, [Microsoft.Exchange.WebServices.Data.UserConfigurationProperties]::All)  
  #$UsrConfig.Dictionary
  $rptCollection = @()
  foreach($cnfObj in $UsrConfig.Dictionary.Key){
   $rptObj = "" | Select Property,Value,Valid
   $rptObj.Property = $cnfObj
   $rptObj.Valid = "Ok"
   $rptObj.Value = $UsrConfig.Dictionary[$cnfObj]
   $rptCollection +=$rptObj
   if($cnfObj -eq "BookInPolicyLegDN")
   {
    foreach($LegDn in $UsrConfig.Dictionary["BookInPolicyLegDN"])
    {
        $ncCol = $service.ResolveName($LegDn, [Microsoft.Exchange.WebServices.Data.ResolveNameSearchLocation]::DirectoryOnly, $false);
           if($ncCol.Count -gt 0){
      #Write-output ("Found " + $ncCol[0].Mailbox.Address)
      $rptObj = "" | Select Property,Value,Valid
      $rptObj.Property = "BookInPolicyValue"
      $rptObj.Value = $ncCol[0].Mailbox.Address
      $rptObj.Valid = "Ok"
      $rptCollection +=$rptObj
           }
     else
     { 
      #Write-Output "Couldn't resolve " + $LegDn
      $rptObj = "" | Select Property,Value,Valid
      $rptObj.Property = "BookInPolicyValue"
      $rptObj.Value = $LegDn
      $rptObj.Valid = "Couldn't resolve"
      $rptCollection +=$rptObj
     }
     
    } 
   }
   if($cnfObj -eq "RequestInPolicyLegDN")
   {
    foreach($LegDn in $UsrConfig.Dictionary["RequestInPolicyLegDN"])
    {
        $ncCol = $service.ResolveName($LegDn, [Microsoft.Exchange.WebServices.Data.ResolveNameSearchLocation]::DirectoryOnly, $false);
           if($ncCol.Count -gt 0){
      #Write-output ("Found " + $ncCol[0].Mailbox.Address)
      $rptObj = "" | Select Property,Value,Valid
      $rptObj.Property = "RequestInPolicyValue"
      $rptObj.Value = $ncCol[0].Mailbox.Address
      $rptObj.Valid = "Ok"
      $rptCollection +=$rptObj
           }
     else
     { 
      #Write-Output "Couldn't resolve " + $LegDn
      $rptObj = "" | Select Property,Value,Valid
      $rptObj.Property = "RequestInPolicyValue"
      $rptObj.Value = $LegDn
      $rptObj.Valid = "Couldn't resolve"
      $rptCollection +=$rptObj
     }
     
    }   
   }
  }
  Write-Output $rptCollection
   
  $rptCollection | Export-Csv -Path ("$MailboxName-CalendarSetting.csv") -NoTypeInformation
 }
}

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 https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filename.txt 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 ' https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filena

A walk-though using the Graph API Mailbox reports in Powershell

Quite recently the Reporting side of the Graph API has moved in GA from beta, there are quite a number of reports that can be run across various Office365 surfaces but in this post I'm going to focus on the Mailbox related ones. Accessing Office365 Reports using Powershell is nothing new and has been available in the previous reporting endpoint  https://msdn.microsoft.com/en-us/library/office/jj984326.aspx however from the end of January many of these cmdlets are now being depreciated in favour of the Graph API  https://msdn.microsoft.com/en-us/library/office/dn387059.aspx . Prerequisites  In comparison to using the Remote PowerShell cmdlets where only the correct Office365 Admin permissions where needed, to use the new Graph API reports endpoint you need to use OAuth for authentication so this requires an Application Registration  https://developer.microsoft.com/en-us/graph/docs/concepts/auth_overview  that is then given the correct oAuth Grants to use the Reports EndPoin

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  https://en.wikipedia.org/wiki/Opportunistic_TLS .  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.