Below find 2 scripts (Big Thanks to Lance A) using PowerShell* to:
- Test the Reason for the last boot
- Set the AMT Alarm Clock.(legacy interface)
Before running a PowerShell script, you may need to set the PowerShell environment to allow scripts to run . Also make sure the vPro Scripting Library is installed on the client.
If you are disappointed that neither Command Prompt nor PowerShell on Windows have the ability to maintain a persistent command history the same way the Linux Terminal does by default, then this blog post is for you.
If you would like to add this capability to the Command Prompt, then the easiest way is to install either of the following applications:
One feature of Windows PowerShell is that it gives you the ability treat various data stores as if they were file systems. An advantage of this approach is that you can use a relatively small set of built-in commands to manage your data stores. This is because only thing that changes from data store to data store is the path to individual items, while the commands to operate on the data remain the essentially the same. Another advantage is that you can start at root of the data store and navigate or explore the contents just like you would a file system.
Starting with the Intel® AMT SDK version 7.0 and higher, it’s becoming much easier to access Intel® AMT Technology using Windows PowerShell. PowerShell, as you have probably heard, is Microsoft’s task automation framework for Windows and provides a scripting language built on top of the .NET framework. Intel now provides a PowerShell Module for Intel® AMT. A PowerShell Module is a package of reusable commands and features that expose their functionality as if they were directly built into PowerShell.