I expect that most of you with enterprise wide antivirus installations probably have vendor tools for managing all of your clients. If so, don’t go away just yet. Even though I’m going to demonstrate how to get antivirus product status with PowerShell, the scripting techniques might still be useful. Or you might learn a bit more about WMI and the CIM cmdlets. Let me start with a simple command to get antivirus information from your local computer, assuming you are running PowerShell 3.0 or later.
I’ve written a few times about my PowerShell module that makes it easier to create remote tabs in the PowerShell ISE. The module, ISERemoteTab, is available in the PowerShell gallery. I’ve also created a short video that demonstrates how to use it, especially the WPF form.
I have a few more ideas for this project when I get some free time. In the mean time this should keep you busy. Enjoy!
For today’s fun I want to introduce you to a PowerShell project I’ve been working on. As with many of these Friday Fun projects this is something that is hardly groundbreaking but it could be fun to use and hopefully serves an educational purpose. What I have is a module called MyTimer that contains several commands designed to work with a very simple timer. In fact it is so simple you’ll probably think I’m joking.
I never take these things for granted and try very hard throughout the year to provide service to the community. So I’m very happy to share the news that I have been renewed for my 10th year as a Microsoft MVP. My official community is Cloud and Datacenter Management, but I think deep down I’ll always be a PowerShell MVP.
I honestly enjoy the work I do and hope that you find it worthwhile. I will be continuing to contribute to the community through this blog, my articles at Petri.com, my courses for Pluralsight as well as conferences and user group presentations. I look forward to the next year. With the upcoming release of Windows Server 2016 there will be many opportunities. I hope you’ll stick around.
Today’s Friday Fun isn’t exactly groundbreaking but you might find it useful in your PowerShell script development process. You might even learn a little something about the PowerShell ISE which is really the point of these articles anyway. How many times have you been working on a script or PowerShell tool and know that you’ll have to write some section of code but aren’t ready to tackle it now? Hopefully you are at least savvy enough to insert a comment reminding you what you need to do. So why not make this simple step as easy as possible in the PowerShell ISE?