{"id":131,"date":"2015-03-19T08:38:36","date_gmt":"2015-03-19T12:38:36","guid":{"rendered":"https:\/\/www.ccrossan.com\/?p=131"},"modified":"2016-07-07T08:03:59","modified_gmt":"2016-07-07T12:03:59","slug":"pushing-calendar-events-with-the-ews-api","status":"publish","type":"post","link":"https:\/\/crossan007.dev\/blog\/microsoft-exchange\/pushing-calendar-events-with-the-ews-api\/","title":{"rendered":"Pushing Calendar Events with the EWS API"},"content":{"rendered":"\n
Tweet<\/a><\/div>\n

We’ve had\u00a0a need to populate users’ calendars with data from\u00a0an internal FileMaker Database, so I dug around in the EWS API, and came up with a script that uses the FileMaker ODBC Connection, and the EWS API to accomplish the task:<\/p>\n

First things first, we need to install the EWS Managed API<\/a> on the machine that will run the script.<\/p>\n

After the EWS Managed API is installed, we need to reference it in our PowerShell script:<\/p>\n

Add-Type -Path “C:\\Program Files\\Microsoft\\Exchange\\Web Services\\2.2\\Microsoft.Exchange.WebServices.dll”<\/p><\/blockquote>\n

Next, we need to set up a System.Net.NetworkCredential object for the account we’ll use to push these events. \u00a0This account must have at least modify permission on the target users’ calendar.<\/p>\n

$Credentials = new-object system.net.NetworkCredential(“CalendarAccessAccount”,”SuperStrongPa$$w0Rd!”,”litware”)<\/p><\/blockquote>\n

Next, we need to Create anMicrosoft.Exchange.WebServices.Data.ExchangeService object:<\/p>\n

$version = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2013_SP1
\n$service = new-object Microsoft.Exchange.WebServices.Data.ExchangeService($version)<\/p><\/blockquote>\n

We don’t want to use the default credentials, Instead we want to authenticate using the service account specified earlier:<\/p>\n

$service.UseDefaultCredentials = $false
\n$service.Credentials=$Credentials<\/p><\/blockquote>\n

And, presuming AutoDiscover is set up correctly in our domain, we want to let EWS figure out the server address, port, etc:<\/p>\n

$service.AutodiscoverUrl(“TargetMailbox@litware.com”)<\/p><\/blockquote>\n

Next, we need to reference the user’s calendar (it’s really just a folder as far as the API is concerned):<\/p>\n

$folderid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Calendar, “TargetMailbox@litware.com”)<\/p><\/blockquote>\n

And finally, we build the appointment object:<\/p>\n

$Appointment = New-Object Microsoft.Exchange.WebServices.Data.Appointment -ArgumentList $Service
\n$appointment.Subject = “Test111”
\n$appointment.Body = “Test111”
\n$appointment.Start = $(Get-Date).AddHours(6)
\n$appointment.End =$(Get-Date).AddHours(9)<\/p><\/blockquote>\n

Don’t forget to save it:<\/p>\n

$appointment.Save($folderid)<\/p>\n

 <\/p><\/blockquote>\n

All in all, we can wrap this up as a function:<\/p>\n

Function CreateAppointment($User,$Credentials)
\n{
\n$mailboxName=$User
\n$version = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2013_SP1
\n$service = new-object Microsoft.Exchange.WebServices.Data.ExchangeService($version)
\n$service.UseDefaultCredentials = $false
\n$service.Credentials=$Credentials
\n$service.AutodiscoverUrl($mailboxName)<\/p>\n

$folderid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Calendar, $mailboxName)<\/p>\n

$Appointment = New-Object Microsoft.Exchange.WebServices.Data.Appointment -ArgumentList $Service
\n$appointment.Subject = “Test\u00a0Subject”
\n$appointment.Body = “Test Body”
\n$appointment.Start = $(Get-Date).AddHours(6)
\n$appointment.End =$(Get-Date).AddHours(9)<\/p>\n

$appointment.Save($folderid)<\/p>\n

}<\/p><\/blockquote>\n

Now we can call the function from, say, with a loop so as to iterate through each user in a CSV:<\/p>\n

$users = Import-CSV “Users.csv”<\/p>\n

$Credentials = new-object system.net.NetworkCredential(“CalendarAccessAccount”,”SuperStrongPa$$w0Rd!”,”litware”)<\/p>\n

Foreach ($User in $Users)<\/p>\n

{<\/p>\n

CreateAppointment $User $Credentials<\/p>\n

}<\/p>\n

 <\/p><\/blockquote>\n

More to come later on the FileMaker ODBC Connection…<\/p>\n","protected":false},"excerpt":{"rendered":"

We’ve had\u00a0a need to populate users’ calendars with data from\u00a0an internal FileMaker Database, so I dug around in the EWS API, and came up with a script that uses the FileMaker ODBC Connection, and the EWS API to accomplish the task: First things first, we need to install the EWS Managed API on the machine … Continue reading Pushing Calendar Events with the EWS API<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[28],"tags":[176,30,47,29],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n