Note: The contents in this post are on topics that are not fully released or implemented.  Content is subject to change at any time.


As previously noted in an earlier blog, we just released Version 2 of the PowerShell Module for Intel vPro Technology.  However, what was not mentioned is that version 2 of the PowerShell Module for Intel vPro Technology has undocumented beta features that can expose AMT as a PowerShell Drive.  Much of the vPro / AMT PowerShell Drive functionality works today; however, we do expect minor changes and additions between now and the final implementation.  Never the less, we wanted to get it out there to allow the PowerShell Community access to it so that you start playing with it and provide feedback.


PowerShell Drives provides the ability to "map” logical data stores the same as a physical data stores, such as a network drive or a directory on the local computer.  You can change locations into the drive (using "set-location", "cd", or "chdir") and access the contents of the drive (using "Get-Item", "Get-Content", or "dir").”  A prime example of this capability is the native support of Windows Registry and Certificate Store as a PowerShell Drive.



We have taken this same concept and exposed AMT (Remotely, Locally, and via HECI) as a PowerShell Drive.



To get started with AMT PowerShell Drives, the first thing we need to do is import the IntelvPro Module:


Import-Module IntelvPro


Second, create a New-PSDrive associated to the remote vPro / AMT system.  To do so, run the following command from the PowerShell console:


New-PSDrive -Name AMT -PSProvider amtsystem -Root "/" -ComputerName -Credential $myPScredential


Note: If your AMT client is configured in TLS mode (TLS encrypted traffic over AMT Port 16993), add the –TLS switch to the command.


If you run a Get-PSDrive, you should see a the newly created PS Drive label as the name you gave it.PSDrive2.jpg


Now that you have the New AMT PowerShell Drive created, you can browse and navigate the remote AMT System in a similar fashion as a normal file system drive:

Set-Location AMT:\


Note: cd AMT:\ and dir work as well




So you may be asking… “That is great, but what can I do with it?”  Well for one, you can perform a Get-Content and pull the AMT Event.

Get-Content AMT:\logs\EventLog




… or perhaps, the AMT Access Monitor (Audit Log)


Get-Content AMT:\logs\AccessMonitor



…or even enumerate the AMT Hardware Inventory and dump the data to a file for auditing purposes


Get-ChildItem -Recurse AMT:\HardwareAssets | Out-File C:\PS\HWInv.txt


…or perhaps just pull the BIOS manufacturing information remotely

Get-ChildItem -Recurse AMT:\HardwareAssets\BIOS





This just scratches the surface on the many things you can do with accessing AMT within PowerShell as a PowerShell Drive.  Keep a look out on the vPro Expert Center for more usages and information on this topic.


Related Content:



--Matt Royer