TT(O)M

Windows started life as a text-based OS that had graphical elements bundled on top. Today most of the interaction with the OS is done through the graphical interface although the underlying text-based interface still exists and is important to reach certain nooks and crannies that are not exposed graphically. The command prompt or cmd was the first and (still) default character-based scripting language to interact with the components making up the operating system.  In 2006 an alternative called PowerShell (PS) became available for Windows. PS is an environment that manipulates configuration files and runs scripts. PS constructs make it easier to develop more complex solutions than with cmd. The latest version of PS is 7.  Version 7 is available for other platforms other than Windows. Joining cmd commands into a script was done in a text file with the extension bat or (later) cmd extensions while PS scripts are identified using the ps1 extension.     PowerShell under Windows has a sa

   PowerShell has a mechanism called ExecutionPolicy that restricts running of  unsigned scripts.  This is intended to protect users from running malicious scripts. There are situations in which such scripts need to be run.  This HOWTO explains the various options that are available focusing on staying secure. More information on the ExecutionPolicy is available at: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.1      

This HOWTO explains the Watch-Win32_UPS PowerShell Uninterrupted Power Supply (UPS) utility. Watch-Win32_UPS allows you to monitor and take and shut down your computer if there is a power failure. It explains how to set it up, delves into the code and invites you to join the development effort behind this tool. GitHub URL for Watch-Win32_UPS: https://github.com/chribonn/UPSMonitor ​