Skip to main content

Geolocating a users last Send location (MEC sample)

This is sample one from the where's wally section of my MEC talk and demonstrates how you can locate the geographical place where a user last sent a Message from using EWS, Extended properties and GeoIp.

This script makes use of the x-ms-exchange-organization-originalclientipaddress extended property which is a extended property that gets set on the copy of the message that is saved into the SentItems folder of a mailbox when you send a message from OWA or Outlook (Note this isn't transmitted with the actually messages itself) . eg

The value of this property reflects the IP Address of the sending client eg so if your using OWA from a Kiosk PC it will show the IP from the Kiosk, or if your using Outlook from home via Outlook-Anywhere it will contain your ISP's Address. Or if your traveling around the world using different hotspots then the address you will get would be from each of the hotspot's you used. Here's a sample report from a mailbox I used from different hotspot's I was using on my recent trip to MEC which included a short holiday in New York.

To resolve the IP Address to geographical location involves using GeoLocation which has an increasing number of users in IT from WebStats to GeoDNS. In this script I've used Maxmind's GeoLiteCity database and Com object. The only thing with the COM object while it only take a few lines of Powershell to use because its a 32 bit library you need to make sure you run it from 32 bit session of Powershell.

 Before running this code you need the GEOIP database and Com object and the database must be in the following location and named GeoIPCity.dat.

$geoip = New-Object -ComObject "GeoIPCOMEx.GeoIPEx"

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

  1. ## Get the Mailbox to Access from the 1st commandline argument  
  3. $MailboxName = $args[0]  
  5. ## Load Managed API dll    
  6. Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"    
  8. ## Set Exchange Version    
  9. $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2    
  11. ## Create Exchange Service Object    
  12. $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)    
  14. ## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials    
  16. #Credentials Option 1 using UPN for the windows Account    
  17. $psCred = Get-Credential    
  18. $creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())    
  19. $service.Credentials = $creds        
  21. #Credentials Option 2    
  22. #service.UseDefaultCredentials = $true    
  24. ## Choose to ignore any SSL Warning issues caused by Self Signed Certificates    
  26. ## Code From  
  27. ## Create a compilation environment  
  28. $Provider=New-Object Microsoft.CSharp.CSharpCodeProvider  
  29. $Compiler=$Provider.CreateCompiler()  
  30. $Params=New-Object System.CodeDom.Compiler.CompilerParameters  
  31. $Params.GenerateExecutable=$False  
  32. $Params.GenerateInMemory=$True  
  33. $Params.IncludeDebugInformation=$False  
  34. $Params.ReferencedAssemblies.Add("System.DLL") | Out-Null  
  36. $TASource=@' 
  37.   namespace Local.ToolkitExtensions.Net.CertificatePolicy{ 
  38.     public class TrustAll : System.Net.ICertificatePolicy { 
  39.       public TrustAll() {  
  40.       } 
  41.       public bool CheckValidationResult(System.Net.ServicePoint sp, 
  42.         System.Security.Cryptography.X509Certificates.X509Certificate cert,  
  43.         System.Net.WebRequest req, int problem) { 
  44.         return true; 
  45.       } 
  46.     } 
  47.   } 
  48. '@   
  49. $TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)  
  50. $TAAssembly=$TAResults.CompiledAssembly  
  52. ## We now create an instance of the TrustAll and attach it to the ServicePointManager  
  53. $TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")  
  54. [System.Net.ServicePointManager]::CertificatePolicy=$TrustAll  
  56. ## end code from  
  58. ## 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    
  60. #CAS URL Option 1 Autodiscover    
  61. $service.AutodiscoverUrl($MailboxName,{$true})    
  62. "Using CAS Server : " + $Service.url     
  64. #CAS URL Option 2 Hardcoded    
  66. #$uri=[system.URI] "https://casservername/ews/exchange.asmx"    
  67. #$service.Url = $uri      
  69. ## Optional section for Exchange Impersonation    
  71. #$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)   
  73. # Bind to the SentItems Folder  
  74. $folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::SentItems,$MailboxName)     
  75. $SentItems = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  76. #Define ExtendedProps  
  77. $OriginalServerIP = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(  
  78. [Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::InternetHeaders,"x-ms-exchange-organization-originalserveripaddress",  
  79. [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::String)  
  81. $OriginalClientIP = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(  
  82. [Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::InternetHeaders,"x-ms-exchange-organization-originalclientipaddress",  
  83. [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::String)  
  85. $psPropset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)    
  86. $psPropset.add($OriginalServerIP)  
  87. $psPropset.add($OriginalClientIP)  
  89. #Setup GEOIP  
  90. $geoip = New-Object -ComObject "GeoIPCOMEx.GeoIPEx"  
  91. $geoip.set_db_path('c:\mec\')  
  94. #Define ItemView to retrive just 1000 Items      
  95. $ivItemView =  New-Object Microsoft.Exchange.WebServices.Data.ItemView(1000)   
  96. $ivItemView.PropertySet = $psPropset  
  97. $fiItems = $null  
  98. $rptCollection = @()  
  99. do{      
  100.     $fiItems = $service.FindItems($SentItems.Id,$ivItemView)      
  101.     #[Void]$service.LoadPropertiesForItems($fiItems,$psPropset)    
  102.     foreach($Item in $fiItems.Items){   
  103.         $rptobj = "" | select DateSent,Subject,ClientIP,LocationCity,LocationCountry,Latitute,Longitute  
  104.         "Subject : " + $Item.Subject  
  105.         $rptobj.Subject = $Item.Subject  
  106.         $rptobj.DateSent = $Item.DateTimeSent  
  107.         $clientIpvalue = $null  
  108.         if($Item.TryGetProperty($OriginalClientIP,[ref]$clientIpvalue)){  
  109.             $rptobj.ClientIP = $clientIpvalue  
  110.             "ClientIP : " + $clientIpvalue  
  111.             if($geoip.find_by_addr($clientIpvalue)){  
  112.                 "Location City : " + $  
  113.                 $rptobj.LocationCity = $  
  114.                 "Location Country : " + $geoip.country_name  
  115.                 $rptobj.LocationCountry = $geoip.country_name  
  116.                 "Location Latitute : " + $geoip.latitude  
  117.                 $rptobj.Latitute = $geoip.latitude  
  118.                 "Location Longitute : " + $geoip.longitude  
  119.                 $rptobj.Longitute = $geoip.longitude  
  120.             }  
  121.         }  
  122.         $serverIpValue = $null  
  123.         if($Item.TryGetProperty($OriginalServerIP,[ref]$serverIpValue)){  
  124.             "ServerIP : " + $serverIpValue  
  125.         }   
  126.         $rptCollection += $rptobj  
  128.     }      
  129.     $ivItemView.Offset += $fiItems.Items.Count      
  130. }while($fiItems.MoreAvailable -eq $true)   
  132. $tableStyle = @" 
  133. <style> 
  134. BODY{background-color:white;} 
  135. TABLE{border-width: 1px; 
  136.   border-style: solid; 
  137.   border-color: black; 
  138.   border-collapse: collapse; 
  139. } 
  140. TH{border-width: 1px; 
  141.   padding: 10px; 
  142.   border-style: solid; 
  143.   border-color: black; 
  144.   background-color:#66CCCC 
  145. } 
  146. TD{border-width: 1px; 
  147.   padding: 2px; 
  148.   border-style: solid; 
  149.   border-color: black; 
  150.   background-color:white 
  151. } 
  152. </style> 
  153. "@  
  155. $body = @" 
  156. <p style="font-size:25px;family:calibri;color:#ff9100">  
  157. $TableHeader  
  158. </p>  
  159. "@  
  161. $rptCollection | ConvertTo-HTML -head $tableStyle –body $body | Out-File c:\temp\GeoIpUserSentReport.html

Popular posts from this blog

Export calendar Items to a CSV file using EWS and Powershell

Somebody asked about this last week and while I have a lot of EWS scripts that do access the Calendar I didn't have a simple example that just exported a list of the Calendar events with relevant information to a CSV file so here it is. I've talked on this one before in this howto  but when you query the calendar folder using EWS you need to use a CalendarView which will expand any recurring appointments in a calendar. There are some limits when you use a calendarview in that you can only return a maximum of 2 years of appointments at a time and paging will limit the max number of items to 1000 per call. So if you have a calendar with a very large number of appointments you need to break your query into small date time blocks. In this example script I'm just grabbing the next 7 days of appointments if you want to query a longer period you need to adjust the following lines (keeping in mind what I just mentioned) #Define Date to Query $StartDate = (Get-Date) $EndDate

Writing a simple scripted process to download attachmentts in Exchange 2007/ 2010 using the EWS Managed API

Every complicated thing in life is made up of smaller simpler building blocks, when it comes to writing a script (or any code really) the more of these little building blocks you have to figure out the more the process of solving a problem can become bewildering. The Internet generally provides you with lots of half eaten sandwiches of information something someone else has taken a bite out but a lot of the time half done, and as with any code its usefulness declines over time as new and better API's and methods are derived. In this post I'm going to go through a simple scripted process that hopefully covers a few more of these smaller building blocks that you might face when asked to come up with a simple costless solution to perform an automated business function with a script. So the process im going to look at is one that comes up a lot and that is you have an Email that comes into to certain mailbox every day with a certain subject in my case "Daily Export" this

EWS Managed API and Powershell How-To series Part 1

I thought I'd start the year with a series of posts that goes back over the basics of using the EWS Managed API from Powershell and provides a modular remarked example that you can easily cut and paste to build your own scripts. Along the way in this series I'll show a whole bunch of examples around specific things. As a starting point for versions this will be Powershell Version 2.0  and the EWS Managed API 1.1 (which will soon change to 1.2 once released) The starting point for any EWS script your going to write is connecting to Exchange for which there are three important pieces of information you will need. Firstly you need to know the version of Exchange your running in this script its going to be held in the following variable $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1 Other valid values for Exchange 2007 would be $ExchangeVersion = [Microsoft.Exchange.Web
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.