Saturday, May 31, 2008

Version 5 of the Mailbox Size Gui Script for Exchange 2007

***** If your running Exchange 2010 please see ********

Okay time for a new version of the mailbox size gui the last version had a number of large bugs and the quota code looked like it had been written by a drunk squirrel. So this version firstly fixes the bugs in the quota code and the bugs with Deleted items sizes and adds some new functionality.

The first addition is a drop down box that allows selection of which quota value you want to report on Eg exchange offers 3 quota levels Warning, Prohibit Send and Prohibit Send and Receive so the script will now allow reporting on which ever Quota usage you want to look at. This section still needs a little work to get better performance as it re-queries the server for mailbox sizes when you change the quota dropdown box instead of just reusing the current result.

The second and most exciting feature is the mailbox size growth feature this is the biggest change and requires some explanation.

Firstly when the script runs now it will create a folder on the c drive called mbsizehistory, it will then record the results of each mailbox size query you make to a csv file in this directory with a serial date as the file name along with the servername . It will only create one file per day and per server you run it against.

So basically every time you run this script it will create this file so if you run it once a week or one a day or every three days you will start collecting adhoc history data about your mailbox size growth. Convention wisdom and what I’ve done in the past is record this type of data to a database every day and then build table, view and graph report on this data. While this is possible with the script the amount of complexity of setup and other backend you need starts getting beyond the technology that might be generally available for a simple script like this. But this where the cool and exciting part comes in to cater for this and allow aggregation of random history files using a few simple date algorithms, hash table and loops I’ve come up with a serial date, random file aggregation datatable. This part is highly experimental as it was only written last week so I haven’t tested it with real data only mock data and haven’t tested it with multiple servers so going on past experience the squirrel may make another appearance. But with the limited testing I’ve done it does work and I think its pretty cool and useful. Basically it aggregates the previous result from the files and tries to show the mailbox growth over 1 day,7days,1 month and 1 year. Because the dates of the file may be intermediate the script handles getting the file that is as closest to the growth date's as possible.

I’ve put a downloadable of the new version here the growth section looks like

function ShowGrowth(){

$datetime = get-date
$arArrayList = New-Object System.Collections.ArrayList
dir c:\mbsizehistory\*.csv | foreach-object{
$fname = $
$nmArray = $"-")
if ($nmArray[1].Replace(".csv","") -eq $snServerNameDrop.SelectedItem.ToString()) {
$spoint = $arArrayList[$arArrayList.Count-1]
$oneday = $spoint
$sevenday = $spoint
$onemonth = $spoint
$oneyear = $spoint
foreach ($file in $arArrayList){
if ($file -gt ($datetime.Adddays(-2).ToString("yyyyMMdd")) -band $file -lt $oneday) {$oneday = $file}
if ($file -gt ($datetime.Adddays(-7).ToString("yyyyMMdd")) -band $file -lt $sevenday) {$sevenday = $file}
if ($file -gt ($datetime.Adddays(-31).ToString("yyyyMMdd")) -band $file -lt $onemonth) {$onemonth = $file}
if ($file -gt ($datetime.Adddays(-256).ToString("yyyyMMdd")) -band $file -lt $oneyear) {$oneyear = $file}
write-host $oneday
write-host $sevenday
write-host $onemonth
write-host $oneyear

$onedaystats = @{ }
$sevendaystats = @{ }
$onemonthsdaystats = @{ }
$oneyearstats = @{ }

Import-Csv ("c:\mbsizehistory\" + $oneday + "-" + $snServerNameDrop.SelectedItem.ToString() + ".csv") | %{
Import-Csv ("c:\mbsizehistory\" + $sevenday + "-" + $snServerNameDrop.SelectedItem.ToString() + ".csv") | %{
Import-Csv ("c:\mbsizehistory\" + $onemonth + "-" + $snServerNameDrop.SelectedItem.ToString() + ".csv") | %{
Import-Csv ("c:\mbsizehistory\" + $oneyear + "-" + $snServerNameDrop.SelectedItem.ToString() + ".csv") | %{

foreach($row in $msTable.Rows){
if ($onedaystats.ContainsKey($row[0].ToString())){
$ondaysizegrowth = $row[2] - $onedaystats[$row[0].ToString()]
else{$ondaysizegrowth = 0}
if ($sevendaystats.ContainsKey($row[0].ToString())){
$sevendaysizegrowth = $row[2] - $sevendaystats[$row[0].ToString()]}
else{$sevendaysizegrowth = 0}
if ($onemonthsdaystats.ContainsKey($row[0].ToString())){
$onemonthsizegrowth = $row[2] - $onemonthsdaystats[$row[0].ToString()]}
else{$onemonthsizegrowth = 0}
if ($oneyearstats.ContainsKey($row[0].ToString())){
$oneyearsizegrowth = $row[2] - $oneyearstats[$row[0].ToString()]}
else{$oneyearsizegrowth = 0}

$dgDataGrid.DataSource = $gtTable


Tuesday, May 27, 2008

OT: Back from Holiday

I survived my hiking adventures and am back on deck to those people who sent me an email over the past couple of weeks sorry there are just too many and not enough time to answer then and the mark all read button kind of works really well so if it was important ping me again.


Wednesday, May 07, 2008

OT : Holidays

Im off from a couple of weeks holidays should be back around the end of may. I've enabled comment moderation to stop the spammers while im away. May all your coding and scripting be happy :)


Saturday, May 03, 2008

Creating a Contact with Exchange Web Services from Powershell

The following is a script that demonstrates how to create a contact using a SOAP string and a simple web request. While this is not a very elegant solution as long as you have your SSL certs sorted out it should work okay. I was planning something a little cooler but time is really short at moment but this is still okay though. When creating a contact there are a few properties that you should set to get a fully working contact object. So the first part of the script is divided into required props which if you are using this in a pipeline you should always make sure you set. If you don’t you may find things like your contacts don’t appear properly when you try to use the contact in the Outlook Address book. The rest of the properties are optional which you can set if you have the information. This is not a complete list of contact properties that can be set within EWS just the majority of the most common ones for a full list please refer to the Exchange SDK. The big advantage if you’re using scripting with EWS in Powershell compared to VBS. is if you combine this script with some simple Import-csv code you can basically create contacts with in a mailbox from any properly formatted CSV (no matter where it came from).

The changeable part of this script is the credential section which allows you to specify the credentials to use when connecting to EWS if you don’t want to specify the credentials you can comment out the following lines

$unUserName = "username"
$psPassword = "password"
$dnDomainName = "domain"
$cdUsrCredentials = new-object System.Net.NetworkCredential($unUserName , $psPassword , $dnDomainName)

To change the script to use the currently logged on user credentials you need to change the following lines

# $WDRequest.Credentials = $cdUsrCredentials
$WDRequest.UseDefaultCredentials = $True

The only other thing you may want to change is to make the script use impersonation if you want to create contacts in mailboxes other than the one associated with the security credentials you are using. The impersonation header should be something like

<t:ExchangeImpersonation> `
<t:ConnectingSID> `
<t:SID>" + $siSIDToSearch.SID + "</t:SID> `
</t:ConnectingSID>" `
</t:ExchangeImpersonation>" `

I’ve put a downloadable copy of the script here the script itself looks like

#Required Props
$subject = "Skippy(Skippys Email)"
$EmailDisplayAS = "Skippy Roo(Skippys Emaill)"
$EmailDisplayName = ""
$EmailAddress1 = ""
$FileAs = "Roo, Skippy"

#Optional Props

$givenName = "Skippy"
$middleName = "The"
$Surname = "Roo"
$nickName = "Skip"
$CompanyName = "Skips Helicopters"
$HomeStreet = "32 Walaby Street"
$HomeCity = "Maroobra"
$HomeState = "NSW"
$HomeCountry = "Australia"
$HomePostCode = "2000"
$BusinessStreet = "45 Emu Place"
$BusinessCity = "Woolloomooloo"
$BusinessState = "NSW"
$BusinessCountry = "Australia"
$BusinessPostCode = "2000"
$HomePhone = "9999-99999"
$HomeFax = "9999-99999"
$BusinessPhone = "9999-99999"
$BusinessFax = "9999-99999"
$MobilePhone = "999-9999-99999"
$AssistantName = "Wally"
$BusinessWebPage = ""
$Department = "Flying"
$OfficeLocation = "1st Floor"
$Profession = "Pilot"

$soapString = "<?xml version=`"1.0`" encoding=`"utf-8`" ?> `
<soap:Envelope xmlns:soap=`"`"
xmlns:xsi=`"`" `
<RequestServerVersion Version=`"Exchange2007_SP1`" xmlns=`"`"
/> `
<soap:Body> `
<CreateItem MessageDisposition=`"SaveOnly`" xmlns=`"`">`
<SavedItemFolderId> `
<DistinguishedFolderId Id=`"contacts`" xmlns=`"`"
<Contact xmlns=`"`"> `
<Subject>" + $subject + "</Subject> `
<ExtendedFieldURI PropertySetId=`"00062004-0000-0000-C000-000000000046`"
PropertyId=`"32898`" PropertyType=`"String`" /> `
<Value>SMTP</Value> `
<ExtendedFieldURI PropertySetId=`"00062004-0000-0000-C000-000000000046`"
PropertyId=`"32896`" PropertyType=`"String`" /> `
<Value>" + $EmailDisplayAS + "</Value> `
<ExtendedFieldURI PropertySetId=`"00062004-0000-0000-C000-000000000046`"
PropertyId=`"32900`" PropertyType=`"String`" /> `
<Value>" + $EmailDisplayName + "</Value> `
<FileAs>" + $fileas + "</FileAs> `
<GivenName>" + $givenName + "</GivenName> `
<MiddleName>" + $middleName + "</MiddleName> `
<Nickname>" + $nickName + "</Nickname> `
<CompanyName>" + $CompanyName + "</CompanyName> `
<Entry Key=`"EmailAddress1`">" + $EmailAddress1 + "</Entry> `
<Entry Key=`"Home`">`
<Street>" + $HomeStreet + "</Street> `
<City>" + $HomeCity + "</City> `
<State>" + $HomeState + "</State> `
<CountryOrRegion>" + $HomeCountry + "</CountryOrRegion> `
<PostalCode>" + $HomePostCode + "</PostalCode> `
<Entry Key=`"Business`">
<Street>" + $BusinessStreet + "</Street> `
<City>" + $BusinessCity + "</City> `
<State>" + $BusinessState + "</State> `
<CountryOrRegion>" + $BusinessCountry + "</CountryOrRegion> `
<PostalCode>" + $BusinessPostCode + "</PostalCode> `
<Entry Key=`"HomePhone`">" + $HomePhone + "</Entry> `
<Entry Key=`"HomeFax`">" + $HomeFax + "</Entry> `
<Entry Key=`"BusinessPhone`">" + $BusinessPhone + "</Entry> `
<Entry Key=`"BusinessFax`">" + $BusinessFax + "</Entry> `
<Entry Key=`"MobilePhone`">" + $MobilePhone + "</Entry> `
<AssistantName>" + $AssistantName + "</AssistantName> `
<BusinessHomePage>" + $BusinessWebPage + "</BusinessHomePage> `
<Department>" + $Department + "</Department> `
<OfficeLocation>" + $OfficeLocation + "</OfficeLocation> `
<Profession>" + $Profession + "</Profession> `
<Surname>" + $Surname + "</Surname> `

$unUserName = "username"
$psPassword = "password"
$dnDomainName = "domain"
$cdUsrCredentials = new-object System.Net.NetworkCredential($unUserName ,
$psPassword , $dnDomainName)

$mbURI = "https://servername/EWS/Exchange.asmx"

$WDRequest = [System.Net.WebRequest]::Create($mbURI)
$WDRequest.ContentType = "text/xml"
$WDRequest.Headers.Add("Translate", "F")
$WDRequest.Method = "POST"
$WDRequest.Credentials = $cdUsrCredentials
# $WDRequest.UseDefaultCredentials = $True
$bytes = [System.Text.Encoding]::UTF8.GetBytes($soapString)
$WDRequest.ContentLength = $bytes.Length
$RequestStream = $WDRequest.GetRequestStream()
$RequestStream.Write($bytes, 0, $bytes.Length)
$WDResponse = $WDRequest.GetResponse()
$ResponseStream = $WDResponse.GetResponseStream()
$readStream = new-object System.IO.StreamReader $ResponseStream
$textresult = $readStream.ReadToEnd()
if ($textresult.indexofany("ResponseClass=`"Success`"")){
"Contact Created Sucessfully"
else {