Skip to content
Menu
The Lonely Administrator
  • PowerShell Tips & Tricks
  • Books & Training
  • Essential PowerShell Learning Resources
  • Privacy Policy
  • About Me
The Lonely Administrator

Download your Ignite schedule with PowerShell

Posted on September 19, 2016September 19, 2016

So I'm starting to get ready for Ignite next week. This year my attendance is down to a single day so I wanted to make sure I got the most out of it. I used the Scheduled Builder to pick some sessions to see on Tuesday.  Once that was done I thought I'd export the events to my calendar. However, I don't use Microsoft Outlook or a Windows Phone. I couldn't get the link to save an .ICS file or otherwise export my schedule. Then I remembered I know how to use PowerShell.

Manage and Report Active Directory, Exchange and Microsoft 365 with
ManageEngine ADManager Plus - Download Free Trial

Exclusive offer on ADManager Plus for US and UK regions. Claim now!

The first step was to visit my schedule page. You can visit yours at https://myignite.microsoft.com/schedule.

image

Personally, I don't have any installed applications that know how to handle the webcal link you get when clicking Export Calendar. So I right-clicked and copied the link. In PowerShell I created a variable for this value.  It will look something like this:

$myLink = "webcal://https://microsoftignitecontent.hubb.me/Sessions/CalendarFeed/uGJN3V..."

Before you can use it, delete everything in the URI up to https. Next, download the content using Invoke-WebRequest. I saved it to another variable.

$dl = Invoke-WebRequest $myLink -DisableKeepAlive

Finally, save the content to a file.

$d.content | set-content c:\work\myignite.ics

And that's it! From here you can open your mail or calendar program of choice and import the ICS file. Mission Accomplished!

If you prefer a one-line approach using your modified URI variable you can use something like this:

(Invoke-WebRequest $myLink -DisableKeepAlive).Content | Set-Content -Path c:\work\myignite.ics

I hope to catch up with a lot of people during my short visit. I'll be tweeting my wanderings around the event.  If you see me, I'll hope you say "Hi" and let me know what you're working on.

UPDATE: I thought I remembered an even easier way to do this. I even re-read the help but apparently missed it. I went to alot of extra work when all I needed to do was this:

invoke-webrequest $mylink -OutFile c:\work\myignite.ics

I suppose another take-away is to read cmdlet help. Maybe even twice!


Behind the PowerShell Pipeline

Share this:

  • Click to share on X (Opens in new window) X
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on Mastodon (Opens in new window) Mastodon
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Pocket (Opens in new window) Pocket
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to print (Opens in new window) Print
  • Click to email a link to a friend (Opens in new window) Email

Like this:

Like Loading...

Related

reports

Powered by Buttondown.

Join me on Mastodon

The PowerShell Practice Primer
Learn PowerShell in a Month of Lunches Fourth edition


Get More PowerShell Books

Other Online Content

github



PluralSightAuthor

Active Directory ADSI Automation Backup Books CIM CLI conferences console Friday Fun FridayFun Function functions Get-WMIObject GitHub hashtable HTML Hyper-V Iron Scripter ISE Measure-Object module modules MrRoboto new-object objects Out-Gridview Pipeline PowerShell PowerShell ISE Profile prompt Registry Regular Expressions remoting SAPIEN ScriptBlock Scripting Techmentor Training VBScript WMI WPF Write-Host xml

©2025 The Lonely Administrator | Powered by SuperbThemes!
%d