Show the cities and Email has tranisted through using the Mail Header, EWS,Powershell and Geolocation (MEC Sample)

October 10, 2012, 4:39 am

≪ Previous: Geolocating a users last Send location (MEC sample)

This is Sample 2 from the where's wally section of my MEC talk, In this sample we will look at how you can get the Internet Headers of a Message via EWS. Then using RegEx parse the IPAddress's from the MailHeader and then using the Geolocation code I talk about in sample 1

The Internet Headers on a Message eg

tell you what happened to a message on the way to your inbox for example what SMTP mail-servers its transited through. In EWS this information can be accessed via the PR_TRANSPORT_MESSAGE_HEADERS extended property http://msdn.microsoft.com/en-us/library/office/cc815628.aspx

By using Regex in Powershell (and some other parsing code to clean the code up) you can parse all the IPAddress's you see in the Received headers then using GeoLocation look these up to determine the city that IPAddress is located in, then compile a list of cities that the email transited through. An example report of running this script on the Junk Email Folder of a Mailbox gives us something like

For more information on the Geolocation code I've used see the 1st example

I've put a download of this script here the code itself looks like

## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
$rptCollection = @()
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
# Bind to the Inbox Folder
$folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::JunkEmail,$MailboxName)
$Inbox = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)
#Define Property for the Message Header
$PR_TRANSPORT_MESSAGE_HEADERS = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(0x007D,[Microsoft.Exchange.WebServices.Data.MapiPropertyType]::String);
$psPropset= new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)
$psPropset.add($PR_TRANSPORT_MESSAGE_HEADERS)
#Setup GEOIP
$geoip = New-Object -ComObject "GeoIPCOMEx.GeoIPEx"
$geoip.set_db_path('c:\mec\')
#Define ItemView to retrive just 10 Items
$ivItemView = New-Object Microsoft.Exchange.WebServices.Data.ItemView(50)
$fiItems = $service.FindItems($Inbox.Id,$ivItemView)
[Void]$service.LoadPropertiesForItems($fiItems,$psPropset)
foreach($Item in $fiItems.Items){
$MailHeaderVal = $null
if($Item.TryGetProperty($PR_TRANSPORT_MESSAGE_HEADERS,[ref]$MailHeaderVal)){
$rptObj = "" | Select DateTimeReceived,From,Subject,Size,TransitCities
$rptObj.DateTimeReceived = $Item.DateTimeReceived
$rptObj.From = $Item.Sender.Address
if($Item.Subject.Length -gt 50){
$rptObj.Subject = $Item.Subject.SubString(0,50)
}
else{
$rptObj.Subject = $Item.Subject
}
$rptObj.Size = $Item.Size
$SMTPTrace = $MailHeaderVal.Substring(0,$MailHeaderVal.IndexOf("From:"))
# RegEx for IP address
$RegExIP = '\b(([01]?\d?\d|2[0-4]\d|25[0-5])\.){3}([01]?\d?\d|2[0-4]\d|25[0-5])\b'
$matchedItems = [regex]::matches($SMTPTrace, $RegExIP)
$lochash = @{}
foreach($Match in $matchedItems){
$preVal = $MailHeaderVal.SubString(($Match.Index-1),1)
if($preVal -eq "[" -bor $preVal -eq "("){
if($geoip.find_by_addr($Match.Value)){
if($geoip.country_name -ne "Localhost" -band $geoip.country_name -ne "Local Area Network"){
if($lochash.ContainsKey(($geoip.city + "-" + $geoip.country_name)) -eq $false){
$lochash.add(($geoip.city + "-" + $geoip.country_name),1)
$rptObj.TransitCities = $rptObj.TransitCities + $geoip.city + "-" + $geoip.country_name + ";"
}
}
}
}
}
$rptCollection += $rptObj
}
}
$tableStyle = @"
<style>
BODY{background-color:white;}
TABLE{border-width: 1px;
border-style: solid;
border-color: black;
border-collapse: collapse;
}
TH{border-width: 1px;
padding: 10px;
border-style: solid;
border-color: black;
background-color:#66CCCC
}
TD{border-width: 1px;
padding: 2px;
border-style: solid;
border-color: black;
background-color:white
}
</style>
"@
$body = @"
<p style="font-size:25px;family:calibri;color:#ff9100">
$TableHeader
</p>
"@
$rptCollection | ConvertTo-HTML -head $tableStyle –body $body | Out-File c:\temp\jnkmhReport.htm

↧

EWS Snippets for PowerGui

October 31, 2012, 4:02 am

≫ Next: Creating a sender domain auto reply rule for a mailbox with EWS and Powershell

≪ Previous: Show the cities and Email has tranisted through using the Mail Header, EWS,Powershell and Geolocation (MEC Sample)

Snippets are an idea that has been around in IDE environments for quite some time and can really be a time saver when it comes to writing EWS scripts. The following are the Snippets for PowerGUI that i presented in my MEC talk in September (Sorry I'm a little late in publishing these).

To use these snippits first you need to have powergui then you can download the Zip file that contains all the snippits from http://msgdev.mvps.org/exdevblog/ews-PowerGuiSnipits.zip .

Once you have unzipped the files to a directory run the ./installsnippits.ps1 script from this directory which will create a snippits folder under %UserName%\My Documents\WindowsPowerShell and copy the snippits into this directory.

Using the Snippits is pretty easy but you do need to understand a little bit about building EWS scripts. The majority of the EWS scripts you create will have 4 major phases

1st Phase - Is to connect and authenticate to the CAS server, in this day and age you should have a proper SSL certificate and Autodiscover should be configured. So in this first phase you need to acquire from somewhere the SMTPAddress of the mailbox you want to access and credentials for you to use to access the mailbox. Then perform a Autodiscover using the SMTPAddress and credentials you acquired which should then return the URL for EWS.

I've bundled this phase into the following snippit

The snippit will take the SMTPAddress as a cmdline parameter

$MailboxName = $args[0]

And also grab the credentials from the user (make sure you use the UPN as the username when it prompts)

$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds

2nd Phase - Now you have the URL for the CAS server to send your EWS request to, the next step is to bind to the folder you want to work with. For all the WellKnownFolders you can bind using the WellKnownFolder enum. I've bundled this phase together in another snippit for each folder for example to bind to the Inbox you use

If you wanted to instead bind to a Subfolder or user created folder I have another snippit for this phase which will bind to a folder using a path.

3rd Phase - Once you have the Folderid of the Folder you want to work with you can then either work with that folder or work with the Items in that folder so the snippit to use if you wish to Enumerate All Folder Items is (there are also several example of searches)

With this snippit you need to replace the $Folder.Id with the Folder.Id from the other Snippit eg if you used

$folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox,$MailboxName)
$Inbox = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)

You should then change

$fiItems = $service.FindItems($Folder.Id,$ivItemView)

to

$fiItems = $service.FindItems($Inbox.Id,$ivItemView)

4th Phase : There is no snippit for this but its basically where you put the code to process the Items eg you could output the Subject

    foreach($Item in $fiItems.Items){
                $Item.Subject
    }

or any of the other things I've listed in my other Howto http://gsexdev.blogspot.com.au/2012/02/ews-managed-api-and-powershell-how-to.html

That's it there are over 60 snippits altogether that I'll try to grow over time if you have any you want to include to help others out please send them to me and I'll include them.

↧

Creating a sender domain auto reply rule for a mailbox with EWS and Powershell

November 12, 2012, 2:57 am

≫ Next: Using eDiscovery to search mailboxes using EWS in Exchange 2013 (the new Exchange)

≪ Previous: EWS Snippets for PowerGui

This is a rewrite of an old CDO 1.2 rule.dll script back from 2006 http://gsexdev.blogspot.com.au/2006/10/creating-domain-based-auto-response.html .

Creating a Domain based auto response rule allows you to have a custom auto-responder for an email based on the sender's email domain of any newly received email messages. This is useful when you need to cater for a number of different scenarios and where you want to add a more personal touch to these auto responders.

EWS allows you to create Inbox rules via the CreateRule Operation if your after the full spiel have a read of http://msdn.microsoft.com/en-us/library/exchange/hh298418%28v=exchg.140%29.aspx

In this script it first uses a ContainsSenderStrings condition to filter on the domain you want the rule to apply to in my example yahoo.com

$nrNewInboxRule.Conditions.ContainsSenderStrings.Add("@yahoo.com")

Exceptions are created for any messages with subject prefixes of RE and FW to omit these messages from an Auto-Response.

$nrNewInboxRule.Exceptions.ContainsSubjectStrings.Add("RE:");

$nrNewInboxRule.Exceptions.ContainsSubjectStrings.Add("FW:")

The script also creates the auto response message which is a message that is saved in the Assoicated Items collection of the Inbox with a message class of "IPM.Note.Rules.ReplyTemplate.Microsoft". One important thing is to set the PidTagReplyTemplateId property on the Template messages as per http://msdn.microsoft.com/en-us/library/ff367988%28v=EXCHG.80%29.aspx

I've put a download of this script here the script itself looks like

## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
$tmTemplateEmail = New-Object Microsoft.Exchange.WebServices.Data.EmailMessage -ArgumentList $service
$tmTemplateEmail.ItemClass = "IPM.Note.Rules.ReplyTemplate.Microsoft";
$tmTemplateEmail.IsAssociated = $true;
$tmTemplateEmail.Subject = "Recipient of your Email action required";
$htmlBodyString = "Hello,<p>Thanks for your Email we only answer emails enqiures from coperates email domains";
$tmTemplateEmail.Body = New-Object Microsoft.Exchange.WebServices.Data.MessageBody($htmlBodyString);
$PidTagReplyTemplateId = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(0x65C2, [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Binary)
$tmTemplateEmail.SetExtendedProperty($PidTagReplyTemplateId, [System.Guid]::NewGuid().ToByteArray());
$tmTemplateEmail.Save([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox);
$nrNewInboxRule = New-Object Microsoft.Exchange.WebServices.Data.Rule
$nrNewInboxRule.DisplayName = "Auto Reply Rule";
$nrNewInboxRule.Conditions.ContainsSenderStrings.Add("@yahoo.com")
$nrNewInboxRule.Actions.ServerReplyWithMessage = $tmTemplateEmail.Id;
$nrNewInboxRule.Exceptions.ContainsSubjectStrings.Add("RE:");
$nrNewInboxRule.Exceptions.ContainsSubjectStrings.Add("FW:");
$cnCreateNewRule = New-Object Microsoft.Exchange.WebServices.Data.createRuleOperation[] 1
$cnCreateNewRule[0] = $nrNewInboxRule
$service.UpdateInboxRules($cnCreateNewRule,$true);

↧

Using eDiscovery to search mailboxes using EWS in Exchange 2013 (the new Exchange)

November 15, 2012, 12:19 am

≫ Next: Create an RSS feed of Exchange Items using any of the How To Series scripts

≪ Previous: Creating a sender domain auto reply rule for a mailbox with EWS and Powershell

eDiscovery is one of the new features in Exchange 2013 that has been built on the top of new operations added in Exchange Web Services in 2013. While its very useful for ITPro's for handling legal discoveries and compliance issues, it opens up a whole new world for application developers building Apps that search Exchange Mailboxes. Like the AQS querystring that was introduced in Exchange 2010 the eDiscovery operations make use of the Exchange Search service's content indexes.

There isn't much documentation around at the moment about how to use eDiscovery in EWS so this is just a dump of what I've learned so far.

All up there are four new EWS operations for eDiscovery however the two that you will use most of the time would be.

GetSearchableMailboxes

Gets a list of mailboxes that the client has permission to search or perform eDiscovery on.

SearchMailboxes

Searches for items in specific mailboxes that match query keywords.

from http://msdn.microsoft.com/en-us/library/exchange/jj190897.aspx

Permissions wise you need to be a member of the Discovery Management RBAC role

The eDiscovery operations make use of the Keyword Query Language (KQL) which there is some decent documentation for in the Protocol documents for KQL http://msdn.microsoft.com/en-us/library/hh644280%28v=office.12%29.aspx although this isn't very Exchange specific. KQL is pretty cool and gives greater control and functionality over the queries you make when compared against AQS. The syntax does bare similarities to AQS and in some cases your AQS queries should just be transferable.

Some KQL samples would be

Subject:"New Time Proposed: test" - This would do an exact match on the Subject

Subject:Football - This would do a SubString type query on the Subject

attachment:'.pdf' - The would search for attachment with a pdf attachment

To use the new eDisocvery operations in the EWS Managed API you need to have v2.0 which was released recently http://www.microsoft.com/en-au/download/details.aspx?id=35371 .

So now it comes to using the SearchMaiboxes operation, to do this you need to have a properly formated KQL query and you need to know the Mailbox Identifier to use. The Mailbox identifier was a bit of tricky one where in most other things in EWS this would be the PrimarySMTPAddress, for this operation its the X500 (or legacyExchangedn) of the mailbox. There are a few ways you could get this the eaiest and most reliable would be to use the GetSearchableMailboxes operation to build the MailboxSearchScope array for the mailboxes you want to search . eg

GetSearchableMailboxesResponse gsMBResponse = service.GetSearchableMailboxes("fsmith", false);
MailboxSearchScope[] msbScope = new MailboxSearchScope[gsMBResponse.SearchableMailboxes.Length];
Int32 mbCount = 0;
foreach (SearchableMailbox sbMailbox in gsMBResponse.SearchableMailboxes) {
msbScope[mbCount] = new MailboxSearchScope(sbMailbox.ReferenceId, MailboxSearchLocation.All);
mbCount++;
}

The Important point is the ReferenceId (which is the X500 address) is the Id that SearchMailbox seems to want.

Next you build the actually request

SearchMailboxesParameters smSearchMailbox = new SearchMailboxesParameters();
MailboxQuery mbq = new MailboxQuery("attachment:'.pdf'", msbScope);
MailboxQuery[] mbqa = new MailboxQuery[1] { mbq };
smSearchMailbox.SearchQueries = mbqa;
smSearchMailbox.PageSize = 1000;
smSearchMailbox.ResultType = Microsoft.Exchange.WebServices.Data.SearchResultType.PreviewOnly;
service.TraceEnabled = true;
ServiceResponseCollection<SearchMailboxesResponse> srCol = service.SearchMailboxes(smSearchMailbox);

There are a bunch of options for manipulating the results such as deduplication and the ability to page and sort the results in different ways and orders. You can also choose just to return the statistics of the query without the results, or return the resutls as PreviewItems where you can control what properties are returned in the PreviewItem.

So for me its a big thumbs up for eDiscovery, so far anyway I can see some frustrations in the way the PriviewItems are returned and there needs to be a lot better info for using KQL and the discovery options.

↧

Create an RSS feed of Exchange Items using any of the How To Series scripts

November 23, 2012, 10:14 pm

≫ Next: Multi Tabbed FreeBusy/OOF Board

≪ Previous: Using eDiscovery to search mailboxes using EWS in Exchange 2013 (the new Exchange)

If you've missed my HowTo Series this year I've been demonstrating many different way's of getting, filtering and searching for Exchange data using Powershell and the EWS Managed API see the full list here . One of the fun things to do with scripting is to link this together with the other plethora of script's out in the world to do different things. Here one example of linking the How-To series script with an RSS feed script from the PoshCode repository http://poshcode.org/?show=669

The following script grabs the last 50 Items in the Inbox and creates an RSS feed of theses Item including Links to OWA for the Item and the Item's Body as HTML in the Feed details.

I've put a download of this code here the script itself look like

###Code from http://poshcode.org/?show=669
# Creates an RSS feed
# Parameter input is for "site": Path, Title, Url, Description
# Pipeline input is for feed items: hashtable with Title, Link, Author, Description, and pubDate keys
Function New-RssFeed
{
param (
$Path = "$( throw 'Path is a mandatory parameter.' )",
$Title = "Site Title",
$Url = "http://$( $env:computername )",
$Description = "Description of site"
)
Begin {
# feed metadata
$encoding = [System.Text.Encoding]::UTF8
$writer = New-Object System.Xml.XmlTextWriter( $Path, $encoding )
$writer.WriteStartDocument()
$writer.WriteStartElement( "rss" )
$writer.WriteAttributeString( "version", "2.0" )
$writer.WriteStartElement( "channel" )
$writer.WriteElementString( "title", $Title )
$writer.WriteElementString( "link", $Url )
$writer.WriteElementString( "description", $Description )
}
Process {
# Construct feed items
$writer.WriteStartElement( "item" )
$writer.WriteElementString( "title", $_.title )
$writer.WriteElementString( "link", $_.link )
$writer.WriteElementString( "author", $_.author )
$writer.WriteStartElement( "description" )
$writer.WriteRaw( "<![CDATA[" ) # desc can contain HTML, so its escaped using SGML escape code
$writer.WriteRaw( $_.description )
$writer.WriteRaw( "]]>" )
$writer.WriteEndElement()
$writer.WriteElementString( "pubDate", $_.pubDate.toString( 'r' ) )
$writer.WriteElementString( "guid", $homePageUrl + "/" + [guid]::NewGuid() )
$writer.WriteEndElement()
}
End {
$writer.WriteEndElement()
$writer.WriteEndElement()
$writer.WriteEndDocument()
$writer.Close()
}
}
### end code from http://poshcode.org/?show=669
## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
# Bind to the Contacts Folder
$folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox,$MailboxName)
$Inbox = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)
$psPropset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)
#Define ItemView to retrive just 50 Items
$ivItemView = New-Object Microsoft.Exchange.WebServices.Data.ItemView(50)
$fiItems = $service.FindItems($Inbox.Id,$ivItemView)
[Void]$service.LoadPropertiesForItems($fiItems,$psPropset)
$feedItems = @()
foreach($Item in $fiItems.Items){
"processing Item " + $Item.Subject
$PostItem = @{}
$PostItem.Add("Title",$Item.Subject)
$PostItem.Add("Author",$Item.Sender.Address)
$PostItem.Add("pubDate",$Item.DateTimeReceived)
$PostItem.Add("link",("https://" + $service.Url.Host + "/owa/" + $Item.WebClientReadFormQueryString))
$PostItem.Add("description",$Item.Body.Text)
$feedItems += $PostItem
}
$feedItems | New-RssFeed -path "c:\temp\Inboxfeed.xml" -title ($MailboxName + " Inbox")

↧

Multi Tabbed FreeBusy/OOF Board

December 10, 2012, 2:52 am

≫ Next: Converting FolderId's from Get-MailboxFolderStatistics to use in EWS

≪ Previous: Create an RSS feed of Exchange Items using any of the How To Series scripts

In the past I've posted scripts for a Free-Busy Board and an OOF Board which uses the EWS Managed API and PowerShell. The following is a combination of the two that displays the OOFStatus of the user combined with their FreeBusy and Calendar Appointments in a Tabbed based output eg

To build the list of Mailboxes to create the Tabs the script uses a Distribution list and the ExpandDL operation which will retrieve a collection of SMTP address's for the members of the group. It then uses the GetUserAvailblity operation and MailTips operation to build the output.

To run the script you need to use the SMTPAddress of mailbox you want the script to run as and the SMTPAddress of the Distribution list to expand. eg

fbooftabs.ps1 user@domain.com dl@domain.com

I've put a download of this script here the code itself looks like

$tbRptSourceHeader=@'
<!DOCTYPE html>
<html lang="en">
<head>
<style>
body
{
font-family: "Segoe UI", arial, helvetica, freesans, sans-serif;
font-size: 90%;
color: #333;
background-color: #e5eaff;
margin: 10px;
z-index: 0;
}
h1
{
font-size: 1.5em;
font-weight: normal;
margin: 0;
}
h2
{
font-size: 1.3em;
font-weight: normal;
margin: 2em 0 0 0;
}
p
{
margin: 0.6em 0;
}
p.tabnav
{
font-size: 1.1em;
text-transform: uppercase;
text-align: right;
}
p.tabnav a
{
text-decoration: none;
color: #999;
}
article.tabs
{
position: relative;
display: block;
width: 80em;
height: 30em;
margin: 2em auto;
}
article.tabs section
{
position: absolute;
display: block;
top: 1.8em;
left: 0;
height: 42em;
padding: 10px 20px;
background-color: #ddd;
border-radius: 5px;
box-shadow: 0 3px 3px rgba(0,0,0,0.1);
z-index: 0;
}
article.tabs section:first-child
{
z-index: 1;
}
article.tabs section h2
{
position: absolute;
font-size: 1em;
font-weight: normal;
width: 120px;
height: 1.8em;
top: -1.8em;
left: 10px;
padding: 0;
margin: 0;
color: #999;
background-color: #ddd;
border-radius: 5px 5px 0 0;
}
'@
$styleFooter=@'
article.tabs section h2 a
{
display: block;
width: 100%;
line-height: 1.8em;
text-align: center;
text-decoration: none;
color: inherit;
outline: 0 none;
}
article.tabs section,
article.tabs section h2
{
-webkit-transition: all 500ms ease;
-moz-transition: all 500ms ease;
-ms-transition: all 500ms ease;
-o-transition: all 500ms ease;
transition: all 500ms ease;
}
article.tabs section:target,
article.tabs section:target h2
{
color: #333;
background-color: #fff;
z-index: 2;
}
</Style>
<meta charset="UTF-8" />
<title>Tabbed FreeBusy-Out of Office Board</title>
<!--[if lt IE 9]>
<script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body>
<article class="tabs">
'@
## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\2.0\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
$fbGroup = $service.ExpandGroup($args[1]);
$StartTime = [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00"))
$EndTime = $StartTime.AddDays(1)
$displayStartTime = [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 08:30"))
$tmValHash = @{ }
$tidx = 0
for($vsStartTime=[DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00"));$vsStartTime -lt [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00")).AddDays(1);$vsStartTime = $vsStartTime.AddMinutes(30)){
$tmValHash.add($vsStartTime.ToString("HH:mm"),$tidx)
$tidx++
}
$drDuration = new-object Microsoft.Exchange.WebServices.Data.TimeWindow($StartTime,$EndTime)
$AvailabilityOptions = new-object Microsoft.Exchange.WebServices.Data.AvailabilityOptions
$AvailabilityOptions.RequestedFreeBusyView = [Microsoft.Exchange.WebServices.Data.FreeBusyViewType]::DetailedMerged
$type = ("System.Collections.Generic.List"+'`'+"1") -as "Type"
$type = $type.MakeGenericType("Microsoft.Exchange.WebServices.Data.AttendeeInfo" -as "Type")
$Attendeesbatch = [Activator]::CreateInstance($type)
$mbrRequest = ""
foreach ($mbr in $fbGroup.Members){
$Attendee = new-object Microsoft.Exchange.WebServices.Data.AttendeeInfo($mbr.Address)
$mbrRequest = $mbrRequest + "<Mailbox xmlns=`"http://schemas.microsoft.com/exchange/services/2006/types`"><EmailAddress>" + $mbr.Address + "</EmailAddress></Mailbox>"
$Attendeesbatch.add($Attendee)
}
$attendeeOOFHash = @{}
##Get OOF Status
$expHeader = @"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header><RequestServerVersion Version="Exchange2010_SP1" xmlns="http://schemas.microsoft.com/exchange/services/2006/types" />
</soap:Header>
<soap:Body>
<GetMailTips xmlns="http://schemas.microsoft.com/exchange/services/2006/messages">
<SendingAs>
<EmailAddress xmlns="http://schemas.microsoft.com/exchange/services/2006/types">$MailboxName</EmailAddress>
</SendingAs>
<Recipients>
"@
$expRequest = $expHeader + $mbrRequest + "</Recipients><MailTipsRequested>OutOfOfficeMessage</MailTipsRequested></GetMailTips></soap:Body></soap:Envelope>"
$mbMailboxFolderURI = New-Object System.Uri($service.url)
$wrWebRequest = [System.Net.WebRequest]::Create($mbMailboxFolderURI)
$wrWebRequest.CookieContainer = New-Object System.Net.CookieContainer
$wrWebRequest.KeepAlive = $false;
$wrWebRequest.Headers.Set("Pragma", "no-cache");
$wrWebRequest.Headers.Set("Translate", "f");
$wrWebRequest.Headers.Set("Depth", "0");
$wrWebRequest.ContentType = "text/xml";
$wrWebRequest.ContentLength = $expRequest.Length;
$wrWebRequest.Timeout = 60000;
$wrWebRequest.Method = "POST";
$wrWebRequest.Credentials = $creds
$bqByteQuery = [System.Text.Encoding]::ASCII.GetBytes($expRequest);
$wrWebRequest.ContentLength = $bqByteQuery.Length;
$rsRequestStream = $wrWebRequest.GetRequestStream();
$rsRequestStream.Write($bqByteQuery, 0, $bqByteQuery.Length);
$rsRequestStream.Close();
$wrWebResponse = $wrWebRequest.GetResponse();
$rsResponseStream = $wrWebResponse.GetResponseStream()
$sr = new-object System.IO.StreamReader($rsResponseStream);
$rdResponseDocument = New-Object System.Xml.XmlDocument
$rdResponseDocument.LoadXml($sr.ReadToEnd());
$RecipientNodes = @($rdResponseDocument.getElementsByTagName("t:RecipientAddress"))
$Datanodes = @($rdResponseDocument.getElementsByTagName("t:OutOfOffice"))
for($ic=0;$ic -lt $RecipientNodes.length;$ic++){
if($Datanodes[$ic].ReplyBody.Message -eq ""){
$attendeeOOFHash.add($Attendeesbatch[$ic].SmtpAddress,"In the Office")
}
else{
$attendeeOOFHash.add($Attendeesbatch[$ic].SmtpAddress,"Out of the Office")
}
}
### End OOF
$rptOutput = $tbRptSourceHeader
$tabNumber = 1
$taboffset = 10
$SectionReport = ""
$atndCnt = 0
$fbType = [Microsoft.Exchange.WebServices.Data.AvailabilityData]::FreeBusy
$availresponse = $service.GetUserAvailability($Attendeesbatch,$drDuration,$fbType,$AvailabilityOptions)
foreach($avail in $availresponse.AttendeesAvailability){
if($tabNumber -eq 1){
}
else{
$taboffset+=122
$rptOutput = $rptOutput + "article.tabs section:nth-child(" + $tabNumber + ") h2 { left: " + ($taboffset) + "px;}`r`n"
}
$SectionReport = $SectionReport + "<section id=`"tab" + $tabNumber + "`">`r`n"
$SectionReport = $SectionReport + "<h2><a href=`"#tab" + $tabNumber + "`">" + $Attendeesbatch[$atndCnt].SmtpAddress.SubString(0,10) + "</a></h2>`r`n"
$SectionReport = $SectionReport + "<p>User : " + $Attendeesbatch[$atndCnt].SmtpAddress + "_________________________________________________________________________________________</p>`r`n"
$SectionReport = $SectionReport + "<p>OOF Status : " + $attendeeOOFHash[$Attendeesbatch[$atndCnt].SmtpAddress] + "</p>`r`n"
$SectionReport = $SectionReport + "<p>Number of Calendar Events : " + $avail.CalendarEvents.Count + "</p>`r`n"
$SectionReport = $SectionReport + "<table><tr>" +"`r`n"
$SectionReport = $SectionReport + "<td align=`"center`" style=`"width=200;`" ><b>Time</b></td>" +"`r`n"
$SectionReport = $SectionReport + "<td align=`"center`" style=`"width=200;`" ><b>Status</b></td>" +"`r`n"
$SectionReport = $SectionReport + "<td align=`"center`" style=`"width=200;`" ><b>Meetings</b></td>" +"`r`n"
$SectionReport = $SectionReport + "</tr>"
$tabNumber++
""
"User : " + $Attendeesbatch[$atndCnt].SmtpAddress
"OOF Status : " + $attendeeOOFHash[$Attendeesbatch[$atndCnt].SmtpAddress]
"Number of Calender Events : " + $avail.CalendarEvents.Count
$fbcnt = 0;
for($stime = $displayStartTime;$stime -lt $displayStartTime.AddHours(10);$stime = $stime.AddMinutes(30)){
$title = ""
if ($avail.MergedFreeBusyStatus[$tmValHash[$stime.ToString("HH:mm")]] -eq "Busy" -bor $avail.MergedFreeBusyStatus[$tmValHash[$stime.ToString("HH:mm")]] -eq "OOF"){
if ($avail.CalendarEvents.Count -ne 0){
for($ci=0;$ci -lt $avail.CalendarEvents.Count;$ci++){
if ($avail.CalendarEvents[$ci].StartTime -ge $stime -band $stime -le $avail.CalendarEvents[$ci].EndTime ){
if($avail.CalendarEvents[$ci].Details.IsPrivate -eq $False){
$subject = ""
$location = ""
if ($avail.CalendarEvents[$ci].Details.Subject -ne $null){
$subject = $avail.CalendarEvents[$ci].Details.Subject.ToString()
}
if ($avail.CalendarEvents[$ci].Details.Location -ne $null){
$location = $avail.CalendarEvents[$ci].Details.Location.ToString()
}
$title = $title + "`"" + $subject + " " + $location + "`" "
}
}
}
}
}
$tbClr = "bgcolor=`"#41A317`""
if($avail.MergedFreeBusyStatus[$tmValHash[$stime.ToString("HH:mm")]] -eq "Busy"){
$tbClr = "bgcolor=`"#153E7E`""
}
$SectionReport = $SectionReport + "<tr>" +"`r`n"
$SectionReport = $SectionReport + "<td align=`"center`" style=`"width=200;`" ><b>" + $stime.ToString("HH:mm") + " </b></td>" +"`r`n"
$SectionReport = $SectionReport + "<td $tbClr align=`"center`" style=`"width=200;`" ><b>" + $avail.MergedFreeBusyStatus[$tmValHash[$stime.ToString("HH:mm")]] + "</b></td>" +"`r`n"
$SectionReport = $SectionReport + "<td align=`"center`" style=`"width=200;`" ><b>" + $title + "</b></td>" +"`r`n"
$SectionReport = $SectionReport + "</tr>"
$stime.ToString("HH:mm") + " : " + $avail.MergedFreeBusyStatus[$tmValHash[$stime.ToString("HH:mm")]] + " : " + $title
$fbcnt++
}
$SectionReport = $SectionReport + "</table>"
$SectionReport = $SectionReport + "</section>`r`n"
$atndCnt++
}
$rptOutput = $rptOutput + $styleFooter + $SectionReport + "</article></body></html>"
$rptOutput | Out-File c:\temp\taboutput.htm

↧

Converting FolderId's from Get-MailboxFolderStatistics to use in EWS

January 1, 2013, 3:00 am

≫ Next: Cleaning out the Skeletons in your mailbox by deleting all the Empty folders with EWS and Get-MailboxFolderStatistics

≪ Previous: Multi Tabbed FreeBusy/OOF Board

If you are using the Exchange Managed Shell Get-MailboxFolderStatistics cmdlet to track down issues or report on folders and you want to be able to get that same folder in EWS to do something else with it here's is script that you can use to do this. This script uses the ConvertId Operation in EWS to convert the OWAId you get from EMS to a EWSId which you can then use in EWS to bind to the folder.

## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
function ConvertId{
param (
$OwaId = "$( throw 'OWAId is a mandatory Parameter' )"
)
process{
$aiItem = New-Object Microsoft.Exchange.WebServices.Data.AlternateId
$aiItem.Mailbox = $MailboxName
$aiItem.UniqueId = $OwaId
$aiItem.Format = [Microsoft.Exchange.WebServices.Data.IdFormat]::OwaId
$convertedId = $service.ConvertId($aiItem, [Microsoft.Exchange.WebServices.Data.IdFormat]::EwsId)
return $convertedId.UniqueId
}
}
## Get Folder id from EMS and bind to the Folder in EWS
get-mailboxfolderstatistics $MailboxName | ForEach-Object{
# Bind to the Inbox Folder
$folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId((Convertid $_.FolderId))
$ewsFolder = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)
$ewsFolder
}

↧

Cleaning out the Skeletons in your mailbox by deleting all the Empty folders with EWS and Get-MailboxFolderStatistics

January 7, 2013, 2:27 am

≫ Next: Creating a new Calendar,Contacts,Tasks or Notes Sub Folder in EWS with Powershell

≪ Previous: Converting FolderId's from Get-MailboxFolderStatistics to use in EWS

One of the things you may find if your using Archive or Retention policies a lot is that you end up with skeleton folders in your mailbox. Which are basically the old folders trees that are all now empty because the items have been moved to the Archive or aged out of the Mailbox. To see your skeletons you can use the Get-MailboxFolderStatistics cmdlet and something like this to identify user created folders that are empty.

get-mailboxfolderstatistics $MailboxName | Where-Object{$_.FolderType -eq "User Created" -band $_.ItemsInFolderAndSubFolders -eq 0}

If you want to delete those folders there is no cmdlet to do this so you need to use EWS. Following on from my last post we can take the FolderId from Get-MailboxFolderStatistics convert this Id to a EWSId so we can then bind to the folder in EWS and then delete it using the Delete method.

I've put together a sample script to show how to do this by first using the Get-MailboxFolderStatistics and then in EWS ConvertId and Delete (a soft folder deletion).

The script itself isn't really intelligent in that it doesn't delete a Sub-folder before the Root folder if both are empty (it just depends they way they comes out). It just relies on the Try-Catch to ignore any errors and uses the EWS Folder TotalCount property as a secondary check.

As this script deletes things (some of which maybe be hard to recover if you don't want them deleted) you should do your own testing and use at your own risk.

I've put a download copy of this script here the code itself looks like

## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
function ConvertId{
param (
$OwaId = "$( throw 'OWAId is a mandatory Parameter' )"
)
process{
$aiItem = New-Object Microsoft.Exchange.WebServices.Data.AlternateId
$aiItem.Mailbox = $MailboxName
$aiItem.UniqueId = $OwaId
$aiItem.Format = [Microsoft.Exchange.WebServices.Data.IdFormat]::OwaId
$convertedId = $service.ConvertId($aiItem, [Microsoft.Exchange.WebServices.Data.IdFormat]::EwsId)
return $convertedId.UniqueId
}
}
## Get Empty Folders from EMS
get-mailboxfolderstatistics $MailboxName | Where-Object{$_.FolderType -eq "User Created" -band $_.ItemsInFolderAndSubFolders -eq 0} | ForEach-Object{
# Bind to the Inbox Folder
"Deleting Folder " + $_.FolderPath
try{
$folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId((Convertid $_.FolderId))
$ewsFolder = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)
if($ewsFolder.TotalCount -eq 0){
$ewsFolder.Delete([Microsoft.Exchange.WebServices.Data.DeleteMode]::SoftDelete)
"Folder Deleted"
}
}
catch{
}
}

↧

Creating a new Calendar,Contacts,Tasks or Notes Sub Folder in EWS with Powershell

January 18, 2013, 2:28 am

≫ Next: Using the PidTagAdditionalRenEntryIdsEx property in EWS to access localized folders such as the RSS Feeds folder in EWS and Powershell

≪ Previous: Cleaning out the Skeletons in your mailbox by deleting all the Empty folders with EWS and Get-MailboxFolderStatistics

I've had a few questions about this in the past week so I thought I would put together a quick sample to show how you can create a new Folder is EWS and set the FolderClass so it appears as a Calendar, Contacts, Tasks, Notes or whatever other folder you want. This is a function so you can just cut and paste it into your own script to use. The full script looks like the following which has samples of using the function at the bottom.

## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credhttp://www.blogger.com/blogger.g?blogID=7123450#editor/target=post;postID=2287688273890342518ential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
function Create-Folder{
param (
$ParentFolderID = "$( throw 'Enter Id of Parent Folder' )",
$FolderName = "$( throw 'Enter Folder Name' )",
$FolderClass = "$( throw 'Enter Folder Class IPF.Note,IPF.Appointment,IPF.Contact,IPF.Task' )"
)
process{
$NewFolder = new-object Microsoft.Exchange.WebServices.Data.Folder($service)
$NewFolder.DisplayName = $FolderName
$NewFolder.FolderClass = $FolderClass
try{
$NewFolder.Save($ParentFolderID)
Write-Host $FolderName + " Folder Created "
}
catch{
"Error : " + $Error[0]
}
}
}
#Example use creating a Calendar subFolder
$ParentId = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Calendar,$MailboxName)
Create-Folder -ParentFolderID $ParentId -FolderName "New Calendar Folder Name" -FolderClass "IPF.Appointment"
#Example use creating a Contacts subFolder
$ParentId = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Contacts,$MailboxName)
Create-Folder -ParentFolderID $ParentId -FolderName "New Contact Folder Name" -FolderClass "IPF.Contact"
#Example use creating a Tasks subFolder
$ParentId = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Tasks,$MailboxName)
Create-Folder -ParentFolderID $ParentId -FolderName "New Tasks Folder Name" -FolderClass "IPF.Task"
#Example use creating a Notes subFolder
$ParentId = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Notes,$MailboxName)
Create-Folder -ParentFolderID $ParentId -FolderName "New Notes Folder Name" -FolderClass "IPF.StickyNote"

↧

Using the PidTagAdditionalRenEntryIdsEx property in EWS to access localized folders such as the RSS Feeds folder in EWS and Powershell

January 22, 2013, 3:41 am

≫ Next: Creating a Report of the WhiteSpace in all the PST's and OST in the default Outlook profile

≪ Previous: Creating a new Calendar,Contacts,Tasks or Notes Sub Folder in EWS with Powershell

As I've covered before in this post when you want to access the WellKnowFolders in EWS in a language independent way (eg not having to worry about localization) you can use the WellKnowFoldersName Enumeration in EWS http://msdn.microsoft.com/en-us/library/exchange/microsoft.exchange.webservices.data.wellknownfoldername%28v=exchg.80%29.aspx. Although most of the folderID's are now included in the enumeration one that is missing is the RSS Feeds folder Id.. The Extended property that holds the PR_EntryID for the RSS Feeds Folder is the PidTagAdditionalRenEntryIdsEx extended property on the Non_IPM_Subtree of a mailbox. This Id is held within a PersistData Block which is a structured Binary property that if you want to read in EWS you need to decode (which is fun).

So how do you decode this property the first thing you want to do is convert it to Hex String while you could deal with it in the Binary array I find it easier to deal with as a Hex String.

$hexVal = [System.BitConverter]::ToString($binVal).Replace("-","");

The next thing you need to do is now start parsing the HexString because its a structure Blob you know what to expect so its just a matter of following the Map. So the first thing you need to do is read the first words (2 Bytes). Which tells you what type of Entry your dealing with from this PersistBlockType Values list this is in little-endian format so it needs to be swapped around to make sense.

After that you need to read the next word which contains the length of the Id property (or the payload). Once you have the length you can then parse the HexEntryId for the folder. As this property stores multiple ID's you need to do this for as many Ids as you can parse out. To then use this HexEntryID in EWS you need to use the ConvertID EWS operation which give you the EWSid of the folder from the HexEntryID which you can then Bind To the folder in EWS.

A full sample of doing this looks like

## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
$PidTagAdditionalRenEntryIdsEx = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(0x36D9, [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Binary)
$psPropset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)
$psPropset.Add($PidTagAdditionalRenEntryIdsEx)
# Bind to the NON_IPM_ROOT Root folder
$folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Root,$MailboxName)
$NON_IPM_ROOT = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid,$psPropset)
$binVal = $null;
$AdditionalRenEntryIdsExCol = @{}
if($NON_IPM_ROOT.TryGetProperty($PidTagAdditionalRenEntryIdsEx,[ref]$binVal)){
$hexVal = [System.BitConverter]::ToString($binVal).Replace("-","");
##Parse Binary Value first word is Value type Second word is the Length of the Entry
$Sval = 0;
while(($Sval+8) -lt $hexVal.Length){
$PtypeVal = $hexVal.SubString($Sval,4)
$PtypeVal = $PtypeVal.SubString(2,2) + $PtypeVal.SubString(0,2)
$Sval +=12;
$PropLengthVal = $hexVal.SubString($Sval,4)
$PropLengthVal = $PropLengthVal.SubString(2,2) + $PropLengthVal.SubString(0,2)
$PropLength = [Convert]::ToInt64($PropLengthVal, 16)
$Sval +=4;
$ProdIdEntry = $hexVal.SubString($Sval,($PropLength*2))
$Sval += ($PropLength*2)
$PtypeVal + " : " + $ProdIdEntry
$AdditionalRenEntryIdsExCol.Add($PtypeVal,$ProdIdEntry)
}
}
function ConvertFolderid($hexId){
$aiItem = New-Object Microsoft.Exchange.WebServices.Data.AlternateId
$aiItem.Mailbox = $MailboxName
$aiItem.UniqueId = $hexId
$aiItem.Format = [Microsoft.Exchange.WebServices.Data.IdFormat]::HexEntryId;
return $service.ConvertId($aiItem, [Microsoft.Exchange.WebServices.Data.IdFormat]::EWSId)
}
if($AdditionalRenEntryIdsExCol.ContainsKey("8001")){
$siId = ConvertFolderid($AdditionalRenEntryIdsExCol["8001"])
$RSSFolderID = new-object Microsoft.Exchange.WebServices.Data.FolderId($siId.UniqueId.ToString())
$RSSFolder = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$RSSFolderID)
$RSSFolder
}

↧

Creating a Report of the WhiteSpace in all the PST's and OST in the default Outlook profile

February 4, 2013, 2:35 am

≫ Next: Mailbox Info Mail app for Exchange 2013/Outlook 2013

≪ Previous: Using the PidTagAdditionalRenEntryIdsEx property in EWS to access localized folders such as the RSS Feeds folder in EWS and Powershell

One of my favorite development utilities is mfcMapi which along with OutlookSpy are invaluable utilities to use when doing any Exchange development. Along with mfcMapi Stephan also has a utility called mrMapi which provides console access to a number of useful MAPI functions . Last week he added a new feature to report on the files sizes and white-space inside a PST or OST based on the Header information in the file http://blogs.msdn.com/b/stephen_griffin/archive/2013/01/28/january-2013-release-of-mfcmapi-and-mrmapi.aspx.

I thought this was a really useful thing as it can be a little bit confounding sometimes looking at PST files that have been produced by exporting a Mailbox and comparing that against the actual mailbox size. So I decided to put a script together that would get all the PST and OST file paths for default Outlook profile. Run those filepaths through mrMapi and parse console Output and the put together a HTML report of the information that ended up looking something like this (all sizes are in MB)

To use this script you need the latest copy of mrMapi from http://mfcmapi.codeplex.com/ and you need to adjust the following varible in the script to the path where you downloaded it to

$mrMapiPath = "c:\mfcmapi\mrmapi.exe"

I've put a download of the script here the code itself looks like

$mrMapiPath = "c:\mfcmapi\mrmapi.exe"
$rptCollection = @()
function ParseBitValue($String){
$numItempattern = '(?=\().*(?=bytes)'
$matchedItemsNumber = [regex]::matches($String, $numItempattern)
$bytes = [INT64]$matchedItemsNumber[0].Value.Replace("(","").Replace(",","") /1MB
return [System.Math]::Round($bytes,2)
}
$Encode = new-object System.Text.UnicodeEncoding
##Check for Office 2013
$RootKey = "Software\Microsoft\Office\15.0\Outlook\Profiles\"
$pkProfileskey = [Microsoft.Win32.Registry]::CurrentUser.OpenSubKey($RootKey, $true)
if($pkProfileskey -eq $null){
$RootKey = "Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles"
$pkProfileskey = [Microsoft.Win32.Registry]::CurrentUser.OpenSubKey($RootKey, $true)
$defProf = $pkProfileskey.GetValue("DefaultProfile")
}
else{
$OutDefault = "Software\Microsoft\Office\15.0\Outlook\"
$pkProfileskey = [Microsoft.Win32.Registry]::CurrentUser.OpenSubKey($OutDefault, $true)
$defProf = $pkProfileskey.GetValue("DefaultProfile")
}
$defProf
$pkSubProfilekey = [Microsoft.Win32.Registry]::CurrentUser.OpenSubKey(($RootKey + "\\" + $defProf), $true)
foreach($Valuekey in $pkSubProfilekey.getSubKeyNames()){
$pkSubValueKey = [Microsoft.Win32.Registry]::CurrentUser.OpenSubKey(($RootKey + "\\" + $defProf + "\\" + $Valuekey ), $true)
$pstVal = $pkSubValueKey.GetValue("001f6700")
if($pstVal -ne $null)
{
$pstPath = $Encode.GetString($pstVal)
$fnFileName = $pstPath.Replace([System.Convert]::ToChar(0x0).ToString().Trim(), "")
if(Test-Path $fnFileName){
$rptObj = "" | Select Name,Type,FilePath,FileSize,FreeSpace,PrecentFree
$fiInfo = ([System.IO.FileInfo]$fnFileName)
$rptObj.Name = $fiInfo.Name
$rptObj.FilePath = $fiInfo.DirectoryName
$rptObj.Type = "PST"
iex ($mrMapiPath + " -pst -i '$pstPath'") | foreach-object{
if($_.Contains("=")){
$splitArray = $_.Split("=")
switch ($splitArray[0].Trim()){
"File Size" {
$rptObj.FileSize = ParseBitValue($splitArray[1].Trim())
}
"Free Space" {
$rptObj.FreeSpace = ParseBitValue($splitArray[1].Trim())
}
"Percent free" {
$rptObj.PrecentFree = $splitArray[1].Trim()
}
}
}
}
$rptCollection += $rptObj
}
}
## Check OSTs
$ostVal = $pkSubValueKey.GetValue("001f6610")
if($ostVal -ne $null)
{
$ostPath = $Encode.GetString($ostVal)
$fnFileName = $ostPath.Replace([System.Convert]::ToChar(0x0).ToString().Trim(), "")
if(Test-Path $fnFileName){
$rptObj = "" | Select Name,Type,FilePath,FileSize,FreeSpace,PrecentFree
$fiInfo = ([System.IO.FileInfo]$fnFileName)
$rptObj.Name = $fiInfo.Name
$rptObj.FilePath = $fiInfo.DirectoryName
$rptObj.Type = "OST"
iex ($mrMapiPath + " -pst -i `"$fnFileName`"") | foreach-object{
if($_.Contains("=")){
$splitArray = $_.Split("=")
switch ($splitArray[0].Trim()){
"File Size" {
$rptObj.FileSize = ParseBitValue($splitArray[1].Trim())
}
"Free Space" {
$rptObj.FreeSpace = ParseBitValue($splitArray[1].Trim())
}
"Percent free" {
$rptObj.PrecentFree = $splitArray[1].Trim()
}
}
}
}
$rptCollection += $rptObj
}
}
}
$tableStyle = @"
<style>
BODY{background-color:white;}
TABLE{border-width: 1px;
border-style: solid;
border-color: black;
border-collapse: collapse;
}
TH{border-width: 1px;
padding: 10px;
border-style: solid;
border-color: black;
background-color:thistle
}
TD{border-width: 1px;
padding: 2px;
border-style: solid;
border-color: black;
background-color:white
}
</style>
"@
$body = @"
<p style="font-size:25px;family:calibri;color:#ff9100">
$TableHeader
</p>
"@
$rptCollection | ConvertTo-HTML -head $tableStyle –body $body |Out-File c:\temp\ProfileReport-$defProf.htm

↧

Mailbox Info Mail app for Exchange 2013/Outlook 2013

February 13, 2013, 3:07 am

≫ Next: Removing attachments of a specific type with EWS and Powershell

≪ Previous: Creating a Report of the WhiteSpace in all the PST's and OST in the default Outlook profile

Mail Apps for Outlook (and OWA) is one of the really cool new features of Exchange 2013.Anybody who has every had to do any OWA customization using forms from Exchange 2003 to 2010 would be glad to see they have finally gone past their used by date and Mail Apps provides the promise of a unified custom app framework across mail clients. At RTM the feature set gap compared to currently what you can do in Outlook Plugins and full access to all EWS operations is substantial (and frustrating) and a show stopper for a lot of good application ideas, but hopefully this will narrow somewhat like a lot of Exchange features when we see new bits and pieces come through in the new cumulative updates.

Mail Apps have three main ingredients

A manifest file which is what is used to install a Mail App and contains all the configuration and activation rules for the Mail App
A html file that is rendered by the Mail client and controls the display elements.
JavaScript files that are bascially the heart soul of your application and contain all the Application and Business logic.

If your going to write a Mail App you need to have a good grip on JavaScript and get acquainted with the JavaScript Api for Office. From a technical point of view you should also understand how the Runtime works which there is a good explanation of here .

Browser Hell - Writing a mail app that you want to run in any browser will take a lot of testing and tweaking, although some of the vendors have improved browser standards are still pretty lacking. For example to get this small Info Apps to work across Chrome, FireFox and ie9 required dealing with Google's different implementation of parseFromString which at the moment can't deal with prefixes while IE and firefox can. This is just one example, if you going to write mail apps make sure you put on your boots and get set to wade in.

Hosting is one other requirement for Mail Apps as the HTML,Manifest and JavaScript files that go along with your application need to be hosted somewhere (they are not stored in Exchange). Basically you just need a Web Server the most obvious source would be your CAS server but any IIS instance will do. If your Mail Apps are mission critical then availability has to factor into the argument or if your in the cloud you'll need to find a Cloud source for your apps. For this sample I've used Azure http://www.windowsazure.com/en-us/home/scenarios/web-sites/ which is a cheap and easy especially if you have a MSDN subscription.

For this Post I've put together an Info App that uses various methods in the Office JavaScript API and EWS to get the following information.

DisplayName from the Item properties
EmailAddress from the Item properties
TimeZone from the Item properties.
Language from the Mailbox Context.
HostVersion from the Diag Object
UserAgent from the Hosting Browsers window.navigator
Total Mailbox Folder Count from EWS (FindFolder)
MailboxServer from the EWS PR_REPLICA_SERVER Extended property
Inbox Total Item Count EWS (GetFolder)
Inbox Unread Item Count EWS (GetFolder)

This is what it looks like the App Box

Manifest file

Every Mail App starts with a Manifest file which contains the configuration information about the MailApp. All Mail Apps need a unique GUID which you can generate easily in Powershell using

[System.GUID]::NewGuid()

Permissions - Mail Apps have a three tired permission model if you want to use EWS you need to specify ReadWriteMailbox. A Mail Aps that is going to use EWS needs to be installed and enabled by an administrator. Eg for this apps the following is configured in the Manifest file

<permissions>ReadWriteMailbox</permissions>

Activation Rules - All Mail apps need an activation rule which basically controls in what items they will appear. Activation rules are also affected by the Permissions that a Mail app requests but for this simple app I have an activation rule that says my Mail App will appear on every Mail Item

<Rule xsi:type="ItemIs" ItemType="Message" />

DisplaySetting - With the Display Setting in a manifest file you can control the size of the Application box and how that application box will appear on different form factors like tablets and mobiles.

HTML and JavaScript files, for your Mail apps you need to reference the Office JavaScript file either that you host along with the application or you can use Microsoft's CDN for this sample I'm using the CDN eg.

<script src="https://appsforoffice.microsoft.com/lib/1.0/hosted/office.js" type="text/javascript"></script>

In this App I've also made use of JQuery which is great utility script to help Glue your Mail App together, like the JavaScript API I've used the CDN version of JQuery.

Installation - There are a couple of way to install a Mail App by far the easiest is just to use EAC eg for this sample Apps if you want to use my hosted version the URL would be

https://gsmailapp.azurewebsites.net/InfoApp/manifest.xml

You should however download and host it yourself I've put a download of the files here

↧

Removing attachments of a specific type with EWS and Powershell

March 5, 2013, 1:37 am

≫ Next: Clearing the RSS Feeds folder in Exchange using EWS and Powershell

≪ Previous: Mailbox Info Mail app for Exchange 2013/Outlook 2013

Sometimes particular attachments can create different issues for a number of different reasons so you might find you want to get rid of all those attachments without removing the messages they are attached to. If you find yourself in this situation then this is the sample for you.

Firstly to find the attachments of a specific type we use the following AQS query

System.Message.AttachmentContents:.pdf

This acts as a first level filter but it will give a few false positives so a second client level check of the actual Attachment file name is needed.

foreach ($Attachment in $Item.Attachments)
{
if($Attachment -is [Microsoft.Exchange.WebServices.Data.FileAttachment]){
if($Attachment.Name.Contains(".pdf")){
}
}
}

The following script can be run in one of two modes , Report will just report on attachments that are found in a particular folder and Delete will delete attachments from messages within that folder. I've put a download of this script here the code itself looks like.

$RunMode = Read-Host "Enter Mode for Script (Report or Delete)"
switch($RunMode){
"Report" {$runokay = $true
"Report Mode Detected"
}
"Delete" {$runokay = $true
"Delete Mode Detected"
}
default {$runOkay = $false
"Invalid Reponse you need to type Report or Delete"
}
}
if($runokay){
## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = (Read-Host "Enter mailbox to run it against(email address)" )
$rptcollection = @()
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"
[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
[System.Reflection.Assembly]::LoadWithPartialName("System.windows.forms")
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
$PR_FOLDER_TYPE = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(13825,[Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Integer);
$folderidcnt = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::MsgFolderRoot,$MailboxName)
# Bind to the Contacts Folder
$rfRootFolder = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderidcnt)
#Define the FolderView used for Export should not be any larger then 1000 folders due to throttling
$fvFolderView = New-Object Microsoft.Exchange.WebServices.Data.FolderView(1000)
#Deep Transval will ensure all folders in the search path are returned
$fvFolderView.Traversal = [Microsoft.Exchange.WebServices.Data.FolderTraversal]::Deep;
$psPropertySet = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)
$PR_Folder_Path = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(26293, [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::String);
#Add Properties to the Property Set
$psPropertySet.Add($PR_Folder_Path);
$fvFolderView.PropertySet = $psPropertySet;
#The Search filter will exclude any Search Folders
$sfSearchFilter = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsEqualTo($PR_FOLDER_TYPE,"1")
$fiResult = $null
#
$Treeinfo = @{}
$TNRoot = new-object System.Windows.Forms.TreeNode("Root")
$TNRoot.Name = "Mailbox"
$TNRoot.Text = "Mailbox - " + $MailboxName
#The Do loop will handle any paging that is required if there are more the 1000 folders in a mailbox
do {
$fiResult = $Service.FindFolders($folderidcnt,$sfSearchFilter,$fvFolderView)
foreach($ffFolder in $fiResult.Folders){
#Process folder here
$TNChild = new-object System.Windows.Forms.TreeNode($ffFolder.DisplayName.ToString())
$TNChild.Name = $ffFolder.DisplayName.ToString()
$TNChild.Text = $ffFolder.DisplayName.ToString()
$TNChild.tag = $ffFolder.Id.UniqueId.ToString()
if ($ffFolder.ParentFolderId.UniqueId -eq $rfRootFolder.Id.UniqueId ){
$ffFolder.DisplayName
[void]$TNRoot.Nodes.Add($TNChild)
$Treeinfo.Add($ffFolder.Id.UniqueId.ToString(),$TNChild)
}
else{
$pfFolder = $Treeinfo[$ffFolder.ParentFolderId.UniqueId.ToString()]
[void]$pfFolder.Nodes.Add($TNChild)
if ($Treeinfo.ContainsKey($ffFolder.Id.UniqueId.ToString()) -eq $false){
$Treeinfo.Add($ffFolder.Id.UniqueId.ToString(),$TNChild)
}
}
}
$fvFolderView.Offset += $fiResult.Folders.Count
}while($fiResult.MoreAvailable -eq $true)
$Script:clickedFolder = $null
$objForm = New-Object System.Windows.Forms.Form
$objForm.Text = "Folder Select Form"
$objForm.Size = New-Object System.Drawing.Size(600,600)
$objForm.StartPosition = "CenterScreen"
$tvTreView1 = new-object System.Windows.Forms.TreeView
$tvTreView1.Location = new-object System.Drawing.Size(1,1)
$tvTreView1.add_DoubleClick({
$Script:clickedFolder = $this.SelectedNode.tag
$objForm.Close()
})
$tvTreView1.size = new-object System.Drawing.Size(580,580)
$tvTreView1.Anchor = "Top,left,Bottom"
[void]$tvTreView1.Nodes.Add($TNRoot)
$objForm.controls.add($tvTreView1)
$objForm.ShowDialog()
$clickedfolderid = new-object Microsoft.Exchange.WebServices.Data.FolderId($Script:clickedFolder)
#Define Attachment Contet To Search for
$AttachmentContent = ".pdf"
$AQSString = "System.Message.AttachmentContents:$AttachmentContent"
#Define ItemView to retrive just 1000 Items
$ivItemView = New-Object Microsoft.Exchange.WebServices.Data.ItemView(1000)
$fiItems = $null
do{
$fiItems = $service.FindItems($clickedfolderid,$AQSString,$ivItemView)
#[Void]$service.LoadPropertiesForItems($fiItems,$psPropset)
foreach($Item in $fiItems.Items){
$Item.Load()
$attachtoDelete = @()
foreach ($Attachment in $Item.Attachments)
{
if($Attachment -is [Microsoft.Exchange.WebServices.Data.FileAttachment]){
if($Attachment.Name.Contains(".pdf")){
if($RunMode -eq "Report"){
$rptObj = "" | Select DateTimeReceived,Subject,AttachmentName,Size
$rptObj.DateTimeReceived = $Item.DateTimeReceived
$rptObj.Subject = $Item.Subject
$rptObj.AttachmentName = $Attachment.Name
$rptObj.Size = $Attachment.Size
$rptcollection += $rptObj
}
$Attachment.Name
if($RunMode -eq "Delete"){
$attachtoDelete += $Attachment
}
}
}
}
$updateItem = $false
foreach($AttachmentToDelete in $attachtoDelete){
if($RunMode -eq "Delete"){
$Item.Attachments.Remove($AttachmentToDelete)
$updateItem = $true
}
}
if($updateItem){$Item.Update([Microsoft.Exchange.WebServices.Data.ConflictResolutionMode]::AlwaysOverWrite)};
}
$ivItemView.Offset += $fiItems.Items.Count
}while($fiItems.MoreAvailable -eq $true)
if($RunMode -eq "Report"){
$rptcollection | Export-Csv -Path c:\temp\$MailboxName-AttachmentReport.csv -NoTypeInformation
}
}

↧

Clearing the RSS Feeds folder in Exchange using EWS and Powershell

May 1, 2013, 5:18 am

≫ Next: Using the EWS FindPeople operation in Exchange 2013 and Exchange Online (2013)

≪ Previous: Removing attachments of a specific type with EWS and Powershell

RSS feeds in Outlook is a nice feature that was added in Outlook, but for some organizations it may not be a desirable feature. While you can't delete the RSS Feeds folder itself as its on of Outlooks default folders you can easily remove each of the feeds and items from these folders using EWS's Empty folder operation http://msdn.microsoft.com/en-us/library/exchange/ff797574(v=exchg.80).aspx. A couple of months back I posted a Language independent way of getting the RSS feeds folder using the PidTagAdditionalRenEntryIdsEx property http://gsexdev.blogspot.com.au/2013/01/using-pidtagadditionalrenentryidsex.html . This script can be easily modified to Empty the RSSFeeds folder eg the following script binds to the RSS Feeds folder and use the Empty Operation with the parameter to also delete all sub folders under the RSS Feeds Folder. - I've put a download of this script here.

## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
$PidTagAdditionalRenEntryIdsEx = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(0x36D9, [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Binary)
$psPropset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)
$psPropset.Add($PidTagAdditionalRenEntryIdsEx)
# Bind to the NON_IPM_ROOT Root folder
$folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Root,$MailboxName)
$NON_IPM_ROOT = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid,$psPropset)
$binVal = $null;
$AdditionalRenEntryIdsExCol = @{}
if($NON_IPM_ROOT.TryGetProperty($PidTagAdditionalRenEntryIdsEx,[ref]$binVal)){
$hexVal = [System.BitConverter]::ToString($binVal).Replace("-","");
##Parse Binary Value first word is Value type Second word is the Length of the Entry
$Sval = 0;
while(($Sval+8) -lt $hexVal.Length){
$PtypeVal = $hexVal.SubString($Sval,4)
$PtypeVal = $PtypeVal.SubString(2,2) + $PtypeVal.SubString(0,2)
$Sval +=12;
$PropLengthVal = $hexVal.SubString($Sval,4)
$PropLengthVal = $PropLengthVal.SubString(2,2) + $PropLengthVal.SubString(0,2)
$PropLength = [Convert]::ToInt64($PropLengthVal, 16)
$Sval +=4;
$ProdIdEntry = $hexVal.SubString($Sval,($PropLength*2))
$Sval += ($PropLength*2)
#$PtypeVal + " : " + $ProdIdEntry
$AdditionalRenEntryIdsExCol.Add($PtypeVal,$ProdIdEntry)
}
}
function ConvertFolderid($hexId){
$aiItem = New-Object Microsoft.Exchange.WebServices.Data.AlternateId
$aiItem.Mailbox = $MailboxName
$aiItem.UniqueId = $hexId
$aiItem.Format = [Microsoft.Exchange.WebServices.Data.IdFormat]::HexEntryId;
return $service.ConvertId($aiItem, [Microsoft.Exchange.WebServices.Data.IdFormat]::EWSId)
}
#Define Function to convert String to FolderPath
function ConvertToString($ipInputString){
$Val1Text = ""
for ($clInt=0;$clInt -lt $ipInputString.length;$clInt++){
$Val1Text = $Val1Text + [Convert]::ToString([Convert]::ToChar([Convert]::ToInt32($ipInputString.Substring($clInt,2),16)))
$clInt++
}
return $Val1Text
}
if($AdditionalRenEntryIdsExCol.ContainsKey("8001")){
$siId = ConvertFolderid($AdditionalRenEntryIdsExCol["8001"])
$RSSFolderID = new-object Microsoft.Exchange.WebServices.Data.FolderId($siId.UniqueId.ToString())
$RSSFolder = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$RSSFolderID)
if($RSSFolder -ne $null){
"Deleteing : " + $RSSFolder.ChildFolderCount.ToString() + " Feeds"
$RSSFolder.Empty([Microsoft.Exchange.WebServices.Data.DeleteMode]::SoftDelete, $true);
}
}

↧

Using the EWS FindPeople operation in Exchange 2013 and Exchange Online (2013)

May 20, 2013, 4:55 am

≫ Next: EWS/Powershell Recoverable Items age report for Exchange 2010/13

≪ Previous: Clearing the RSS Feeds folder in Exchange using EWS and Powershell

In previous versions of Exchange accessing the Directory (or Global Address List) with EWS was limited to just resolving a specific entry or expanding a Distribution list. In Exchange 2013 the concept of the persona's has been introduced http://msdn.microsoft.com/en-us/library/exchange/jj190898%28v=exchg.150%29.aspx. To distill this down a little a persona allows you to have a Contact that can pull its related information from multiple sources while previously everything was just stored in one object in the Exchange Store.

There are a number of new EWS operations to go along with personas and the Unified Contact Store the most interesting of these is the FindPeople operation which allows you to do something you couldn't do previously which is enumerate the entire GAL (or any other address list). At this point I should make the point that the GAL is just one of the data sources that FindPeople can search you can also include searching the local contact folders.

To able to search an Address List (including the GAL but it will work with any of the Address Lists like ("All Room", "All Contacts") you need to know the AddressList Id. However this is one part of these new operations that really needs improvement because at the moment there is no way in EWS to get a list of AddressList Id's. While the FindPeople operation is used in OWA in 2013 they have a custom command in OWA called "GetPeopleFilters". So if you want to use the FindPeople operation you need to either Get the AddressList id from using OWA and capturing it with fiddler eg

(If your using Office365 this is the only way you can get this information that i know of as the Get-AddressList cmdlet or LDAP/AD access isn't available in the cloud)

In a OnPrem environment you can just use the Get-AddressList cmdlet eg

(or you could also use LDAP to get this information)

Once you have the address list Id your ready to code, there are no methods in the EWS Managed API for this operation so you need to use WSDL ProxyCode or RAW Soap to use this operation. For example the following is a C# sample for using the FindPeople operation to enumerate through the address list 100 entries at the a time

FindPeopleType fpType = new FindPeopleType();
IndexedPageViewType indexPageView = new IndexedPageViewType();
indexPageView.BasePoint = IndexBasePointType.Beginning;
indexPageView.Offset = 0;
indexPageView.MaxEntriesReturned = 100;
indexPageView.MaxEntriesReturnedSpecified = true;
fpType.IndexedPageItemView = indexPageView;
fpType.ParentFolderId = new TargetFolderIdType();
DistinguishedFolderIdType contactsFolder = new DistinguishedFolderIdType();
AddressListIdType adList = new AddressListIdType();
adList.Id = "2117949e-abe8-4915-91eb-6b9f867fd8de";
fpType.ParentFolderId.Item = adList;
FindPeopleResponseMessageType fpm = null;
do
{
fpm = esb.FindPeople(fpType);
if (fpm.ResponseClass == ResponseClassType.Success)
{
foreach (PersonaType PsCnt in fpm.People) {
Console.WriteLine(PsCnt.EmailAddress.EmailAddress);
}
indexPageView.Offset += fpm.People.Length;
}
else {
throw new Exception("Error");
}
} while (fpm.TotalNumberOfPeopleInView > indexPageView.Offset);

↧

EWS/Powershell Recoverable Items age report for Exchange 2010/13

June 12, 2013, 3:53 am

≫ Next: EWS Findpeople workaround for reading the Offline Address Book in Office365 / Exchange Online

≪ Previous: Using the EWS FindPeople operation in Exchange 2013 and Exchange Online (2013)

With Single Item Recovery in Exchange 2010 and Exchange 2013, the Recoverable Items Folder in an Exchange Mailbox becomes one of the things you may want to pay some more special attention to in the course of managing the disk resource that are being consumed within your Exchange Org. The following is a script that does another take on ItemAge reporting by basically crawling every item in a folder and then grouping the DateTimeRecieved (to get the age of the Item) and the ModifiedTime(which is when its deleted). The script produces a report like the following for the Mailbox you run it against

To use the script you just need to enter the SMTPAddress of the Mailbox you want to run it against and as long as you have rights to the mailbox you should get a report.

I've put a download of the script here the code looks like

## Get the Mailbox to Access from the 1st commandline argument
$MailboxName = $args[0]
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\2.0\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
$service.AutodiscoverUrl($MailboxName,{$true})
"Using CAS Server : " + $Service.url
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
$PR_MESSAGE_SIZE_EXTENDED = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(3592,[Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Long);
$psPropset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)
$psPropset.Add($PR_MESSAGE_SIZE_EXTENDED)
# Bind to the MsgFolderRoot folder
$folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::RecoverableItemsDeletions,$MailboxName)
$RecoverableItemsDeletions = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid,$psPropset)
$rptObject = "" | Select MailboxName,TotalNumberOfItems,TotalSize,AgeLessThan7days,AgeLessThan7daysSize,Age7To30Days,Age7To30DaysSize,Age1to6Months,Age1to6MonthsSize,Age6To12Months,Age6To12MonthsSize,AgeGreator12Months,AgeGreator12MonthsSize,DeletedLessThan7days,DeletedLessThan7daysSize,Deleted7To30Days,Deleted7To30DaysSize,Deleted1to6Months,Deleted1to6MonthsSize,Deleted6To12Months,Deleted6To12MonthsSize,DeletedGreator12Months,DeletedGreator12MonthsSize
$rptObject.AgeLessThan7daysSize = [INT64]0
$rptObject.Age7To30DaysSize = [INT64]0
$rptObject.Age1to6MonthsSize = [INT64]0
$rptObject.Age6To12MonthsSize = [INT64]0
$rptObject.AgeGreator12MonthsSize = [INT64]0
$rptObject.AgeLessThan7days = [INT64]0
$rptObject.Age7To30Days = [INT64]0
$rptObject.Age1to6Months = [INT64]0
$rptObject.Age6To12Months = [INT64]0
$rptObject.AgeGreator12Months = [INT64]0
$rptObject.DeletedLessThan7daysSize = [INT64]0
$rptObject.Deleted7To30DaysSize = [INT64]0
$rptObject.Deleted1to6MonthsSize = [INT64]0
$rptObject.Deleted6To12MonthsSize = [INT64]0
$rptObject.DeletedGreator12MonthsSize = [INT64]0
$rptObject.DeletedLessThan7days = [INT64]0
$rptObject.Deleted7To30Days = [INT64]0
$rptObject.Deleted1to6Months = [INT64]0
$rptObject.Deleted6To12Months = [INT64]0
$rptObject.DeletedGreator12Months = [INT64]0
$rptObject.MailboxName = $MailboxName
$rptObject.TotalNumberOfItems = $RecoverableItemsDeletions.TotalCount
$folderSizeVal = $null;
if($RecoverableItemsDeletions.TryGetProperty($PR_MESSAGE_SIZE_EXTENDED,[ref]$folderSizeVal)){
$rptObject.TotalSize = [Math]::Round([Int64]$folderSizeVal / 1mb,2)
}
#Define ItemView to retrive just 1000 Items
$ivItemView = New-Object Microsoft.Exchange.WebServices.Data.ItemView(1000)
$itemPropset= new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::IdOnly)
$itemPropset.Add([Microsoft.Exchange.WebServices.Data.ItemSchema]::DateTimeReceived)
$itemPropset.Add([Microsoft.Exchange.WebServices.Data.ItemSchema]::DateTimeCreated)
$itemPropset.Add([Microsoft.Exchange.WebServices.Data.ItemSchema]::LastModifiedTime)
$itemPropset.Add([Microsoft.Exchange.WebServices.Data.ItemSchema]::Size)
$fiItems = $null
$itemCnt = 0
do{
$fiItems = $service.FindItems($RecoverableItemsDeletions.Id,$ivItemView)
#[Void]$service.LoadPropertiesForItems($fiItems,$psPropset)
foreach($Item in $fiItems.Items){
$Notadded = $true
$dateVal = $null
if($Item.TryGetProperty([Microsoft.Exchange.WebServices.Data.ItemSchema]::DateTimeReceived,[ref]$dateVal )-eq $false){
$dateVal = $Item.DateTimeCreated
}
$modDateVal = $null
if($Item.TryGetProperty([Microsoft.Exchange.WebServices.Data.ItemSchema]::LastModifiedTime,[ref]$modDateVal)){
if($modDateVal -gt (Get-Date).AddDays(-7))
{
$rptObject.DeletedLessThan7days++
$rptObject.DeletedLessThan7daysSize += $Item.Size
$Notadded = $false
}
if($modDateVal -le (Get-Date).AddDays(-7) -band $modDateVal -gt (Get-Date).AddDays(-30))
{
$rptObject.Deleted7To30Days++
$rptObject.Deleted7To30DaysSize += $Item.Size
$Notadded = $false
}
if($modDateVal -le (Get-Date).AddDays(-30) -band $modDateVal -gt (Get-Date).AddMonths(-6))
{
$rptObject.Deleted1to6Months++
$rptObject.Deleted1to6MonthsSize += $Item.Size
$Notadded = $false
}
if($modDateVal -le (Get-Date).AddMonths(-6) -band $modDateVal -gt (Get-Date).AddMonths(-12))
{
$rptObject.Deleted6To12Months++
$rptObject.Deleted6To12MonthsSize += $Item.Size
$Notadded = $false
}
if($modDateVal -le (Get-Date).AddYears(-1))
{
$rptObject.DeletedGreator12Months++
$rptObject.DeletedGreator12MonthsSize += $Item.Size
$Notadded = $false
}
}
if($dateVal -gt (Get-Date).AddDays(-7))
{
$rptObject.AgeLessThan7days++
$rptObject.AgeLessThan7daysSize += $Item.Size
$Notadded = $false
}
if($dateVal -le (Get-Date).AddDays(-7) -band $dateVal -gt (Get-Date).AddDays(-30))
{
$rptObject.Age7To30Days++
$rptObject.Age7To30DaysSize += $Item.Size
$Notadded = $false
}
if($dateVal -le (Get-Date).AddDays(-30) -band $dateVal -gt (Get-Date).AddMonths(-6))
{
$rptObject.Age1to6Months++
$rptObject.Age1to6MonthsSize += $Item.Size
$Notadded = $false
}
if($dateVal -le (Get-Date).AddMonths(-6) -band $dateVal -gt (Get-Date).AddMonths(-12))
{
$rptObject.Age6To12Months++
$rptObject.Age6To12MonthsSize += $Item.Size
$Notadded = $false
}
if($dateVal -le (Get-Date).AddYears(-1))
{
$rptObject.AgeGreator12Months++
$rptObject.AgeGreator12MonthsSize += $Item.Size
$Notadded = $false
}
}
$ivItemView.Offset += $fiItems.Items.Count
}while($fiItems.MoreAvailable -eq $true)
if($rptObject.AgeLessThan7daysSize -gt 0){
$rptObject.AgeLessThan7daysSize = [Math]::Round($rptObject.AgeLessThan7daysSize/ 1mb,2)
}
if($rptObject.Age7To30DaysSize -gt 0){
$rptObject.Age7To30DaysSize = [Math]::Round($rptObject.Age7To30DaysSize/ 1mb,2)
}
if($rptObject.Age1to6MonthsSize -gt 0){
$rptObject.Age1to6MonthsSize = [Math]::Round($rptObject.Age1to6MonthsSize/ 1mb,2)
}
if($rptObject.Age6To12MonthsSize -gt 0){
$rptObject.Age6To12MonthsSize = [Math]::Round($rptObject.Age6To12MonthsSize/ 1mb,2)
}
if($rptObject.AgeGreator12MonthsSize -gt 0){
$rptObject.AgeGreator12MonthsSize = [Math]::Round($rptObject.AgeGreator12MonthsSize/ 1mb,2)
}
if($rptObject.DeletedLessThan7daysSize -gt 0){
$rptObject.DeletedLessThan7daysSize = [Math]::Round($rptObject.DeletedLessThan7daysSize/ 1mb,2)
}
if($rptObject.Deleted7To30DaysSize -gt 0){
$rptObject.Deleted7To30DaysSize = [Math]::Round($rptObject.Deleted7To30DaysSize/ 1mb,2)
}
if($rptObject.Deleted1to6MonthsSize -gt 0){
$rptObject.Deleted1to6MonthsSize = [Math]::Round($rptObject.Deleted1to6MonthsSize/ 1mb,2)
}
if($rptObject.Deleted6To12MonthsSize -gt 0){
$rptObject.Deleted6To12MonthsSize = [Math]::Round($rptObject.Deleted6To12MonthsSize/ 1mb,2)
}
if($rptObject.DeletedGreator12MonthsSize -gt 0){
$rptObject.DeletedGreator12MonthsSize = [Math]::Round($rptObject.DeletedGreator12MonthsSize/ 1mb,2)
}
$a = "<style>"
$a = $a + "TABLE{border-width: 1px;border-style: solid;border-color: black;border-collapse: collapse;}"
$a = $a + "TH{border-width: 1px;padding: 0px;border-style: solid;border-color: black;}"
$a = $a + "TD{border-width: 1px;padding: 0px;border-style: solid;border-color: black;}"
$a = $a + "</style>"
$rptObject | ConvertTo-Html -As LIST -Head $a | Out-File c:\temp\RetainedItemReport.htm

↧

EWS Findpeople workaround for reading the Offline Address Book in Office365 / Exchange Online

June 14, 2013, 4:08 am

≫ Next: EWS Powershell default Mailbox Folder ACE audit script

≪ Previous: EWS/Powershell Recoverable Items age report for Exchange 2010/13

A couple of weeks ago I posted this about using the new FindPeople operation in EWS with Exchange 2013 to enumerate through the Global Address List. As I mentioned one pain point around using this new operation on Office365 is that you need to know the AddressList Id which there is no way of dynamically getting via EWS. This has been bugging me for a while so I started thinking about some ways of working around this and one method I found that did work is you can obtain the Id for the Offline Address Book and then query this (which is mostly as good as querying the Online GAL).

To Get the Id of the Offline Address book what you first need to do is use AutoDiscover to get the External OAB url, Then use a normal Get request on this url for the oab.xml file. Then you can parse from the OAB.xml file the Guid value of the OAB which you can transform into an AddressList id that you can then use with EWS to query the OAB. The following C# sample use the EWS Managed API for Autodiscover and then use some WSDL Proxy code to execute the FindPeople Operation

NetworkCredential ncCred = new NetworkCredential("user@domain.onmicrosoft.com", "psword");
String mbMailbox = "user@domain.onmicrosoft.com";
AutodiscoverService adService = new AutodiscoverService(ExchangeVersion.Exchange2013);
adService.Credentials = ncCred;
adService.RedirectionUrlValidationCallback = adAutoDiscoCallBack;
GetUserSettingsResponse adResponse = adService.GetUserSettings(mbMailbox, (new UserSettingName[2] { UserSettingName.ExternalOABUrl,UserSettingName.ExternalEwsUrl }));
String exOABURL = (String)adResponse.Settings[UserSettingName.ExternalOABUrl];
String ewsURL = (String)adResponse.Settings[UserSettingName.ExternalEwsUrl];
String auDisXML = "";
System.Net.HttpWebRequest oabRequest = (System.Net.HttpWebRequest)System.Net.HttpWebRequest.Create((exOABURL + "oab.xml"));
byte[] bytes = Encoding.UTF8.GetBytes(auDisXML);
oabRequest.ContentLength = bytes.Length;
oabRequest.ContentType = "text/xml";
oabRequest.Headers.Add("Translate", "F");
oabRequest.Method = "GET";
oabRequest.Credentials = ncCred;
oabRequest.AllowAutoRedirect = false;
WebResponse oabResponse = oabRequest.GetResponse();
Stream rsResponseStream = oabResponse.GetResponseStream();
XmlDocument reResponseDoc = new XmlDocument();
reResponseDoc.Load(rsResponseStream);
XmlNodeList oabDetails = reResponseDoc.GetElementsByTagName("OAL");
String OabGuid = oabDetails[0].Attributes["dn"].Value.Substring(6);
OabGuid = OabGuid.Substring(6, 2) + OabGuid.Substring(4, 2) + OabGuid.Substring(2, 2) + OabGuid.Substring(0, 2) + "-" + OabGuid.Substring(10, 2) + OabGuid.Substring(8, 2) + "-" + OabGuid.Substring(14, 2) + OabGuid.Substring(12, 2) + "-" + OabGuid.Substring(16, 4) + "-" + OabGuid.Substring(20, 12);
ExchangeServiceBinding esb = new ExchangeServiceBinding();
esb.Url = ewsURL;
esb.Credentials = ncCred;
esb.RequestServerVersionValue = new EWSProxy.RequestServerVersion();
esb.RequestServerVersionValue.Version = ExchangeVersionType.Exchange2013;
FindPeopleType fpType = new FindPeopleType();
IndexedPageViewType indexPageView = new IndexedPageViewType();
indexPageView.BasePoint = IndexBasePointType.Beginning;
indexPageView.Offset = 0;
indexPageView.MaxEntriesReturned = 100;
indexPageView.MaxEntriesReturnedSpecified = true;
fpType.IndexedPageItemView = indexPageView;
fpType.ParentFolderId = new TargetFolderIdType();
DistinguishedFolderIdType contactsFolder = new DistinguishedFolderIdType();
AddressListIdType adList = new AddressListIdType();
adList.Id = OabGuid;
fpType.ParentFolderId.Item = adList;
FindPeopleResponseMessageType fpm = null;
do
{
fpm = esb.FindPeople(fpType);
if (fpm.ResponseClass == ResponseClassType.Success)
{
foreach (PersonaType PsCnt in fpm.People)
{
if (PsCnt.EmailAddress.MailboxTypeSpecified) {
Console.WriteLine(PsCnt.EmailAddress.MailboxType);
}
Console.WriteLine( PsCnt.EmailAddress.EmailAddress);
}
indexPageView.Offset += fpm.People.Length;
}
else
{
throw new Exception("Error");
}
} while (fpm.TotalNumberOfPeopleInView > indexPageView.Offset);
}
internal static bool adAutoDiscoCallBack(string url)
{
return true;
}

↧

EWS Powershell default Mailbox Folder ACE audit script

June 25, 2013, 5:29 am

≫ Next: Creating Item Attachments with the EWS Managed API with Powershell

≪ Previous: EWS Findpeople workaround for reading the Offline Address Book in Office365 / Exchange Online

The default Access Control Entry ACE in an Exchange Mailbox Folder DACL controls the rights that all authenticated users have to a particularity mailbox folder. Generally from a security perspective its something you don't want users to use as they may not understand when then set this ACE they are giving all people access to certain information. Eg Giving the default user reviewer rights to your Inbox means everyone in the Exchange org can now read mailbox in you Inbox which may not provide much privacy to your email. The following script will enumerate the permissions on every folder in a Mailbox and then produce a report of the folders where the default ACE isn't set to none. For most users the only folder that should show up in the report in the calendar folder. This script uses EWS but you could also use the Exchange Management Shell Get-MailboxFolderPermission cmdlet.

To run this script you need to feed is with a CSV file that contains the SMTPAddress of the Mailboxes you want it to run against. I've put a download of this script here the script itself looks like

## Get the Mailbox to Access from the 1st commandline argument
$Script:rptCollection = @()
## Load Managed API dll
Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\2.0\Microsoft.Exchange.WebServices.dll"
## Set Exchange Version
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2
## Create Exchange Service Object
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials
#Credentials Option 1 using UPN for the windows Account
$psCred = Get-Credential
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())
$service.Credentials = $creds
#Credentials Option 2
#service.UseDefaultCredentials = $true
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null
$TASource=@'
namespace Local.ToolkitExtensions.Net.CertificatePolicy{
public class TrustAll : System.Net.ICertificatePolicy {
public TrustAll() {
}
public bool CheckValidationResult(System.Net.ServicePoint sp,
System.Security.Cryptography.X509Certificates.X509Certificate cert,
System.Net.WebRequest req, int problem) {
return true;
}
}
}
'@
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly
## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll
## end code from http://poshcode.org/624
## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use
#CAS URL Option 1 Autodiscover
#CAS URL Option 2 Hardcoded
#$uri=[system.URI] "https://casservername/ews/exchange.asmx"
#$service.Url = $uri
## Optional section for Exchange Impersonation
#$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)
# Bind to the Inbox Folder
#Define Function to convert String to FolderPath
function ConvertToString($ipInputString){
$Val1Text = ""
for ($clInt=0;$clInt -lt $ipInputString.length;$clInt++){
$Val1Text = $Val1Text + [Convert]::ToString([Convert]::ToChar([Convert]::ToInt32($ipInputString.Substring($clInt,2),16)))
$clInt++
}
return $Val1Text
}
function Process-Mailbox{
param (
$SmtpAddress = "$( throw 'SMTPAddress is a mandatory Parameter' )"
)
process{
#Define Extended properties
$PR_FOLDER_TYPE = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(13825,[Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Integer);
$folderidcnt = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::MsgFolderRoot,$SmtpAddress)
#Define the FolderView used for Export should not be any larger then 1000 folders due to throttling
$fvFolderView = New-Object Microsoft.Exchange.WebServices.Data.FolderView(1000)
#Deep Transval will ensure all folders in the search path are returned
$fvFolderView.Traversal = [Microsoft.Exchange.WebServices.Data.FolderTraversal]::Deep;
$psPropertySet = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)
$PR_Folder_Path = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(26293, [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::String);
#Add Properties to the Property Set
$psPropertySet.Add($PR_Folder_Path);
$fvFolderView.PropertySet = $psPropertySet;
#The Search filter will exclude any Search Folders
$sfSearchFilter = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsEqualTo($PR_FOLDER_TYPE,"1")
$fiResult = $null
#Process the Mailbox Root Folder
$psPropset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)
$psPropset.Add([Microsoft.Exchange.WebServices.Data.FolderSchema]::Permissions);
#The Do loop will handle any paging that is required if there are more the 1000 folders in a mailbox
do {
$fiResult = $Service.FindFolders($folderidcnt,$sfSearchFilter,$fvFolderView)
foreach($ffFolder in $fiResult.Folders){
$foldpathval = $null
#Try to get the FolderPath Value and then covert it to a usable String
if ($ffFolder.TryGetProperty($PR_Folder_Path,[ref] $foldpathval))
{
$binarry = [Text.Encoding]::UTF8.GetBytes($foldpathval)
$hexArr = $binarry | ForEach-Object { $_.ToString("X2") }
$hexString = $hexArr -join ''
$hexString = $hexString.Replace("FEFF", "5C00")
$fpath = ConvertToString($hexString)
}
"Processing FolderPath : " + $fpath
$ffFolder.Load($psPropset)
foreach($Permission in $ffFolder.Permissions){
if($Permission.UserId.StandardUser -eq [Microsoft.Exchange.WebServices.Data.StandardUser]::Default){
if($Permission.DisplayPermissionLevel -ne "None"){
$rptObj = "" | Select Mailbox,FolderPath,FolderType,PermissionLevel
$rptObj.Mailbox = $SmtpAddress
$rptObj.FolderPath = $fpath
$rptObj.FolderType = $ffFolder.FolderClass
$rptObj.PermissionLevel = $Permission.DisplayPermissionLevel
$Script:rptCollection += $rptObj
}
}
}
}
$fvFolderView.Offset += $fiResult.Folders.Count
}while($fiResult.MoreAvailable -eq $true)
}
}
Import-Csv -Path $args[0] | ForEach-Object{
if($service.url -eq $null){
$service.AutodiscoverUrl($_.SmtpAddress,{$true})
"Using CAS Server : " + $Service.url
}
Process-Mailbox -SmtpAddress $_.SmtpAddress
}
$Script:rptCollection

↧

Creating Item Attachments with the EWS Managed API with Powershell

July 22, 2013, 3:25 am

≫ Next: Forwarding a Message as an Attachment using the EWS Managed API and Powershell

≪ Previous: EWS Powershell default Mailbox Folder ACE audit script

Item Attachments in EWS allow you to create an Attachment that is of a Rich Exchange type such as an EmailMessage, Task, Post, Contact etc or even your own custom form if your using these. Although one thing you can't do with an Item attachment is attach an existing Exchange Item.

To use ItemAttachments in Powershell you need to use reflection in .NET as it involves invoking a Generic Method which is not that straight forward in Powershell.

The following is an example of creating a Task as an Item Attachment in Powershell using reflection

$mail = New-Object Microsoft.Exchange.WebServices.Data.EmailMessage($service);
$AtColtype = ("Microsoft.Exchange.WebServices.Data.AttachmentCollection") -as "Type"
$Tasktype = ("Microsoft.Exchange.WebServices.Data.Task") -as "Type"
$methodInf = $AtColtype.GetMethod("AddItemAttachment");
$AddItmAttachMethod = $methodInf.MakeGenericMethod($Tasktype);
$TaskAttachment = $AddItmAttachMethod.Invoke($mail.Attachments,$null);
$TaskAttachment.Item.Subject = "Mondays Task"
$TaskAttachment.Item.StartDate = (Get-Date)
$TaskAttachment.Item.DueDate = (Get-Date).AddDays(7)
$TaskAttachment.Name = "Mondays Task"
$mail.Subject = "See the Attached Task"
$mail.ToRecipients.Add("user@domain.com")
$mail.SendAndSaveCopy()

↧

Forwarding a Message as an Attachment using the EWS Managed API and Powershell

July 22, 2013, 4:27 am

≫ Next: Sending a VoiceMail using EWS and Powershell

≪ Previous: Creating Item Attachments with the EWS Managed API with Powershell

While you can easily create an Inbox rule to forward a Message as an Attachment, doing this programmatically in EWS isn't that straight forward. As there is no direct method in EWS to attach an existing Store item a work around is needed.

With this workaround we use the MimeContent of an existing email message which will allow you to create an ItemAttachment of this existing message (using the method from this post) in the Inbox and maintain all the Mime Properties and attachments on the message your forwarding. Note this method doesn't maintain full fidelity of a Message as it won't include any MAPI properties or Exchange rich datatypes which may or may not be important.

The following sample demonstrates how to forward the more recently received email in the Inbox as an Item Attachment using the MimeContent (and also setting the MessageFlags property to make sure the message appears sent).

$folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox,$MailboxName)
$Inbox = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)
#Define ItemView to retrive just 1 Item
$ivItemView = New-Object Microsoft.Exchange.WebServices.Data.ItemView(1)
$fiItems = $service.FindItems($Inbox.Id,$ivItemView)
if($fiItems.Items.Count -eq 1){
$mail = New-Object Microsoft.Exchange.WebServices.Data.EmailMessage($service)
$OriginalEmail = $fiItems.Items[0]
$psPropset= new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::IdOnly)
$psPropset.Add([Microsoft.Exchange.WebServices.Data.ItemSchema]::MimeContent)
$psPropset.Add([Microsoft.Exchange.WebServices.Data.ItemSchema]::Subject)
$OriginalEmail.Load($psPropset)
$AtColtype = ("Microsoft.Exchange.WebServices.Data.AttachmentCollection") -as "Type"
$Emailtype = ("Microsoft.Exchange.WebServices.Data.EmailMessage") -as "Type"
$methodInf = $AtColtype.GetMethod("AddItemAttachment");
$AddItmAttachMethod = $methodInf.MakeGenericMethod($Emailtype);
$EmailAttachment = $AddItmAttachMethod.Invoke($mail.Attachments,$null);
$EmailAttachment.Item.MimeContent = $OriginalEmail.MimeContent
$PR_Flags = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(3591, [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Integer);
$EmailAttachment.Item.SetExtendedProperty($PR_Flags,"1")
$EmailAttachment.Name = $OriginalEmail.Subject
$mail.Subject = "See the Attached Email"
$mail.ToRecipients.Add("glen.scales@messageops.com")
$mail.SendAndSaveCopy()
}

↧