You know when you read documentation about a task or problem you need to solve and you think ‘Thats easy!’. But you find yourself scratching yourself in the head 6 hours later… Sounds like the average IT-task right?
I wanted to write a new guide to show you the thought process that I have when I’m exploring .net classes in Powershell. And something that most of you use is Exchange so I wrote a few lines on how to explore and use the EWS API.
I got a task to come up with a method to import resource calendars in public folders to resource resource mailboxes instead. A lot of the methods I found online involved a lot of manual hand cranking, and that’t not viable for 100s of calendars.
Happened to go down the rabbit hole and found out that you can search the data stored by Windows Search in powershell.
A while back I decided to create a powershell module for todoist.
A year ago i discovered Microsoft Flow.
A while back we had a couple of session with microsoft, one of those focused on DR of Active Directory and another one was on AD health. Here are some of my notes and things learned. Some of them are obvious but might need a reminder and other ones might not be well known:
About a year ago I stumbled upon what was for me some kind of holy grail. I struggled for a long time with managing multiple parallel projects and lots and lots of tasks was forgotten about. Everything was an emergency and most of my time was spent putting out fires only to see a new one arise.
I wanted something that would run powershell scripts as a service easily and I never was a fan of running it with taskscheduler. This windows service reads the path of the script and it’s arguments from the app.conf file so you can run any powershell script that you want (i think). It also redirects output and errors to eventlog and terminates itself if the script would stop running. I have tested it on Windows Server 2012 and Windows 10.