Skip to main content

Using Google Charts in Exchange Powershell Scripts

I've been looking at rewriting some message tracking scripts and one the things that's helpfull when you are doing message tracking is having some nice flashy visuals to help you out. Now there are some nice 3rd party packages out there like powergadgets who will separate you from your money and also the WPF framework stuff that give you some charting functionality. But if you want something that's free and will work from any workstation/server that has powershell and a Internet connection then its hard to go past Google Charts. Once you work you way around the different URL options its pretty much just a matter of creating some code to build the URL.

So to put this into something that is actually useful here's a couple of samples that first generate Rate information from the message tracking log files on Exchange 2003 using the wonder of WMI and on Exchange 2007 using the Exchange Management Shell get-messagetrackinglog cmdlet. The script itself is pretty simple it uses a hashtable to build this rate information then loops back though the hashtable to build a Google chart Url then it creates a Winform and adds a picture control setting the location property of the picture control to the URL that was built for Google charts. The cool thing is that's all you have to do because the picture control will handle all the http request stuff and download the png image and then display it to you how cool is that ! . Well I was pretty impressed anyway and you may see this technique popping up here a little more in the future.

I've put a sample of two scripts one for 2003 one for 2007 that shows a graph of the sent and received email for the last 6 hours. To use this script you need to set the hardcoded servername variable

$servername = "servername"

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

[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
[System.Reflection.Assembly]::LoadWithPartialName("System.windows.forms")

$servername = "servername"


$hcHourCount = @{ }
$dtQueryDT = [DateTime]::UtcNow.AddHours(-6)
$dtQueryDTf = [DateTime]::UtcNow
Get-MessageTrackingLog -Server $servername -ResultSize Unlimited -Start $dtQueryDT -End $dtQueryDTf -EventId "Send" | ForEach-Object{
$mdate = $_.TimeStamp
if ($hcHourCount.ContainsKey($mdate.hour)){
$hcHourCount[$mdate.hour] = [int]$hcHourCount[$mdate.hour] + 1
}
else{
$hcHourCount.Add($mdate.hour,1)
}
}
Get-MessageTrackingLog -Server $servername -ResultSize Unlimited -Start $dtQueryDT -End $dtQueryDTf -EventId "Receive" | ForEach-Object{
$mdate = $_.TimeStamp
if ($hcHourCount.ContainsKey($mdate.hour)){
$hcHourCount[$mdate.hour] = [int]$hcHourCount[$mdate.hour] + 1
}
else{
$hcHourCount.Add($mdate.hour,1)
}
}


$valueBlock = ""
$TitleBlock = ""
$lval = 0

$hcHourCount.GetEnumerator() | sort name -descending | foreach-object {
if ($lval -lt $_.value){$lval = $_.value}
if ($valueBlock -eq "") {$valueBlock = $_.value.ToString()}
else {$valueBlock = $valueBlock + "," + $_.value.ToString()}
if ($TitleBlock -eq ""){$TitleBlock = $_.key.ToString() + ":00"}
else {$TitleBlock = $_.key.ToString() + ":00" + "|" + $TitleBlock}

}

$hcHourCount
$csString = "http://chart.apis.google.com/chart?cht=bhg&chs=400x250&chd=t:" + $valueBlock + "&chds=0," + ($lval+20) + "&chxt=x,y&chxr=" + "&chxr=0,0," + ($lval+20) + "&chxl=1:|" + $TitleBlock + "&chco=00ff00&chtt=Message+Volume++Last+6+Hours"
$form = new-object System.Windows.Forms.form
$form.Text = "Last 6 Hours Graph"

#add Picture box

$pbox = new-object System.Windows.Forms.PictureBox
$pbox.Location = new-object System.Drawing.Size(10,10)
$pbox.Size = new-object System.Drawing.Size(400,250)
$pbox.ImageLocation = $csString
$form.Controls.Add($pbox)
$form.Size = new-object System.Drawing.Size(500,350)

$form.topmost = $true
$form.Add_Shown({$form.Activate()})
$form.ShowDialog()
Labels:

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...
Read more

Sending a MimeMessage via the Microsoft Graph using the Graph SDK, MimeKit and MSAL

One of the new features added to the Microsoft Graph recently was the ability to create and send Mime Messages (you have been able to get Message as Mime for a while). This is useful in a number of different scenarios especially when trying to create a Message with inline Images which has historically been hard to do with both the Graph and EWS (if you don't use MIME). It also opens up using SMIME for encryption and a more easy migration path for sending using SMTP in some apps. MimeKit is a great open source library for parsing and creating MIME messages so it offers a really easy solution for tackling this issue. The current documentation on Send message via MIME lacks any real sample so I've put together a quick console app that use MSAL, MIME kit and the Graph SDK to send a Message via MIME. As the current Graph SDK also doesn't support sending via MIME either there is a workaround for this in the future my guess is this will be supported.
Read more

Export calendar Items to a CSV file using Microsoft Graph and Powershell

For the last couple of years the most constantly popular post by number of views on this blog has been  Export calendar Items to a CSV file using EWS and Powershell closely followed by the contact exports scripts. It goes to show this is just a perennial issue that exists around Mail servers, I think the first VBS script I wrote to do this type of thing was late 90's against Exchange 5.5 using cdo 1.2. Now it's 2020 and if your running Office365 you should really be using the Microsoft Graph API to do this. So what I've done is create a PowerShell Module (and I made it a one file script for those that are more comfortable with that format) that's a port of the EWS script above that is so popular. This script uses the ADAL library for Modern Authentication (which if you grab the library from the PowerShell gallery will come down with the module). Most EWS properties map one to one with the Graph and the Graph actually provides better information on recurrences then...
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.