In the previous article of this series we looked at using WMI in PowerShell to discover service information. The WMI service object offers a few properties missing from the .NET service object. And while we can use Set-Service to modify a service object, there may be situations where you want or need to use WMI.
The fifth installment in our series about managing Windows Services with PowerShell explains how to leverage WMI and CIM for configuring remote Services.
Let’s continue our exploration of using PowerShell to manage services. If you’ve missed the previous articles, take a few minutes to get caught up. In this article I want to explain how to configure services using the Set-Service cmdlet. This cmdlet uses the same service object that Get-Service works with.
Over the last few articles we’ve been exploring different ways to gather relevant service information from local and remote computers using PowerShell. In Part 3 of this series I will explain how to start, stop and restart Services with PowerShell.