I have been learning more about IIS this past month, and have discovered something interesting…
I recently found myself using a hard-to-find OfficeScan Database scanning tool that reports any issues it finds within the OfficeScan Server application directory. I thought it would be great if I could automate/schedule the tool, but the tool is only an executable that works only in interactive mode with a GUI. Thankfully, I found that these issues are all problems that can be discovered via PowerShell script! So I created a PowerShell version of the tool.
I’ve been pretty busy, lately. It’s taken a while for me to finally get around to looking at the Iron Scripter challenge, alongside the winning code, that went on at the PowerShell Summit this past April. How did the challenge work?
Participants were awarded 1-5 points in each of the following categories:
- Presentation (formatting)
- Use of the Theme Ingredient (being CIM)
- Taste (functionality)
The challenge was made up of three courses:
- Appetizer Course
- Dessert Course
- Main Course
I’ve created a script that applies best practices to TMCM 5.5 or 6.0 servers, and tested on PowerShell v2 through 4.
I created a resource document of links to articles, twitter feeds, blogs, youtube videos, and githubs based on the 2014 PowerShell Summit. I thought this would be the best way to provide resources to those that wanted to dig into what was covered this year.
If you know of anything I’ve missed, definitely leave a comment or hit me up on twitter with extra resources.
I’ve run into an issue where our Antivirus Vendor, Trend Micro, is unable to provide a service where we are emailed notifications of product service packs, patches, critical patches, repackaging of packages, etc. They also don’t have a notification process for when any of those are taken off their download site entirely due to bugs that are causing high impact across their customers. It looks like I’m going to use PowerShell to monitor the Download Center.