As I write this, I have just finished the second round of Automation Bootcamps. This was an intense week, with courses spread over three time zones, for two different platforms, with each course happening over two days. We had a great turnout as usual—over 600 attendees between the morning, afternoon, and evening sessions.
This is our first time doing the Automation Bootcamp in the evening to cater to our Australian partners, and we had very positive feedback and great uptake. We are working on the next round of training for Q4, so I will give you all an update in one of my next blog posts once I have the confirmed dates. We’ll also soon be launching our Advanced Automation Bootcamp, so watch this space.
It is always interesting to see what questions pop up during the various courses. I have partners that are struggling to do the labs and require more help, which is expected, and then we have people who want more and ask questions about their own use cases, which is also great.
Since the training sessions ended, I have received well over 100 questions via email from partners asking for help with their own automation policies and scripts. I am taking the time to answer every partner, and every time I can, I build the automation policy for them and then publish it to the cookbook to help the rest of our automation community at the same time.
So keep checking in for our latest updates – www.solarwindsmsp.com/cookbook.
For this week, I wanted to use the example of a policy that was built recently for a partner after the bootcamp. This partner wanted to look in his client’s devices for large OST files. Rapidly expanding OST files is becoming a problem as Office 365 now comes with 100 GB free storage, causing mailboxes to grow rapidly since users don’t need to archive to PST files anymore.
This partner wanted to be able to look on his client’s machines for OST files over a certain size—his request was 30 GB or more—and then receive a notification if any were found. This would enable him to talk to the user and avoid issues with Outlook when files got too large.
Here is the link to the cookbook article if you want to get a copy of this policy:
As always, don’t forget to go look in the Automation Cookbook at if you are interested in other automation policies, script checks, and custom services.
Marc-Andre Tanguay is Head Automation Nerd. You can follow him on Twitter at @automation_nerd
Get the latest MSP tips, tricks, and ideas sent to your inbox each week.