The “Hey, Scripting Guys!” blog has been retired. There are many useful posts in this blog, so we keep the blog here for historical reference. However, some information might be very outdated and many of the links might not work anymore.
New PowerShell content is being posted to the PowerShell Community blog where members of the community can create posts by submitting content in the GitHub repository.
Summary: Learn how to use Windows PowerShell to determine if a laptop is running on battery.
(image) How can I use Windows PowerShell to determine if my laptop is running on battery?
(image) Use the Win32_Battery WMI class and look for a BatteryStatus of 1—this means the battery is discharging (in use). Here is an ...
Summary: Our trip now takes us from the Netherlands to Dortmund to Geneva and then on to Zurich.
Well, the Scripting Wife and I had a wonderful time at the first-ever Dutch PowerShell user group. I delivered two presentations and made dozens of new contacts and friends. The following day, Jeff Wouters took Teresa and me out and showed us ...
Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell to detect the power state on his laptop and to set the appropriate power plan.
Microsoft Scripting Guy, Ed Wilson, is here. This evening in Oslo, Norway, the Scripting Wife and I are attending the Microsoft Technology User Group meeting. The meeting runs from 18:...
Summary: Learn how to use Windows PowerShell to view contents of a VBScript file.
(image) How can I use Windows PowerShell to easily view the contents of a VBScript file, such as SLMGR.VBS? I do not know the path to the file.
(image) You do not need to know the path to the file. Use the Windows PowerShell Get-...
Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell and WMI or CIM cmdlets to view and to set power plans on his laptop.
Microsoft Scripting Guy, Ed Wilson, is here.
Tomorrow, the Scripting Wife and I are at the Microsoft Technology User Group in Oslo, Norway. I will be talking about using Windows PowerShell 3...