1 2 3 Previous Next

Intel vPro Expert Center Blog

1,214 posts

With ePO Deep Command v2.4 you can activate Intel AMT v7+ out of the box without using Intel RCS or the need of purchasing configuration certificate. You can even put the Systems into Admin Control Mode. Please refer to the blog post.


Coming soon, now I am in testing step....


Graphics Driver issue

Posted by jb2559 Aug 25, 2015

I recently upgraded from Windows 7 to Windows 10 and now when my grandson tries to play Minecraft he gets an error message that the graphics driver needs updated.  I determined that it currently has a Intel Driver and I ran the Intel Driver Utility and it came back and said no drivers were needed.  I thought I would try and manually download a driver but when I went to the list of Intel drivers there was not one for Windows 10.  Only Windows 7 and Vista.  I tried to download that one and received an error message that my computer did not meet the minimum requirements.  Has anyone else run into a similar issue and if so how did you resolve it?

I have a new Windows 10 HP Laptop.  A popup is suggesting I install this software to keep my system up to date and will I agree to the terms.  I find this intrusive and wish to ask if it's important. Why do I need this?


Multiple Alarms Feature

Posted by Tmowreader Jul 9, 2015

Hello, I am trying to remotely configure 150ish PC's with multiple AMT Alarms.  I can see from this webpage that AMT 8.0 and later supports the Multiple Alarm Feature, and all of our machines are 8.1 or newer.  I have successfully created individual alarms on multiple machines at once using the Intel vPro PowerShell GUI.  (Very hand tool BTW.)  I assume however that the tool was built before the ability to have multiple alarms as the option to set them does not exist in the GUI.  When I run a Get-Help command on Set-AMTAlarmclock I don't see a reference to the "ElementName" filed mentioned in the link above that appears to identify the individual alarms.


I'm fairly new to AMT and PowerShell and would appreciate any guidance you can provide.


I apologize if this is not the correct Forum, I couldn't find another that was more relevant.  I realize this is not related to Intel SCS.


Thank you for your time,






I am trying to setup an Intel SCS server to deploy AMT profiles to HP Intel vPro PCs.


In order to do this, I need to provision a Certificate, I got one from Comodo, but Intel SCS is asking for a CA Plugin couldn't find this anywhere

Is only giving me the option to use Domain Internal CA Certificates.


Any help

An enterprise customer wanted to enable Active Directory integration with Intel AMT on their large Intel vPro client estate. However their security team wanted the permissions for the Intel SCS service account against the Organisational Unit (OU) where Intel AMT computer objects are stored to support Kerberos, to be as restrictive as possible.


As defined in the Intel® Setup and Configuration Software User Guide, permissions for the SCS service account on the OU container are “Create Computer objects”, “Delete Computer objects” and “List content” (the latter seems to be default) and full control on descendant computer objects. The latter was not acceptable so ...



... to support AMT maintenance tasks such as updating the password of the AD object representing the Intel AMT device and ensuring the Kerberos clock remains synchronised, the following explicit permissions are required on all descendant computer objects within the OU.


The customers security team were happier with these permissions and they are now activating their Intel vPro systems to enable the powerful manageability and security capabilities that Active Management Technology, available on Intel vPro Technology platforms provides.

Take from an original (deleted) post by TerryCutler.


Intel AMT Remote Configuration enables the authentication of the firmware for an initial Intel AMT configuration event.  Remote configuration supports Admin Control Mode configuration of the Intel AMT firmware and is typically done using valid provisioning certificate for the customers environment.


This authentication process has to be completed without user interaction. If the requesting application i.e. Intel SCS is prompted every time access to the private key is required, the autonomy is lost.


When importing the certificate to your target server, if the strong key protection option is selected and grayed out, this indicates a conflicting group policy for cryptography has been applied to the server.


Changing the group policy setting of the server will remove this barrier, so set the System Cryptography policy to the "User input is not required when new keys are stored and used"

Periodically the question comes up “Can I use Intel vPro Technology to remotely unlock an encrypted hard drive ?”, either because unattended encrypted systems need to be booted outside of business hours and patched or because there is a significant cost associated with IT helpdesk calls when helpdesk technicians must remotely guide end users through a recovery process if they forgot their drive encryption passphrase or PIN.


Here are some available solutions for remotely unlocking encrypted drives using Intel vPro Technology…


Intel Hardware KVM Technology: Using Intel AMT and a hardware KVM viewer like VNC RealVNC Viewer Plus or McAfee KVMView (part of McAfee ePO Deep Command), it is possible for an IT helpdesk technician to remotely connect to an encrypted Intel vPro system and manually enter the recovery password at the pre-boot authentication screen to unlock the encrypted drive so Windows can boot. The remote connection to the Intel vPro system can be made over a wired or wireless LAN and the system can be connected directly to the internal enterprise network or through a Client Initiated Remote Access (CIRA) session. The recovery password needs to have been previously escrowed to a backup database (usually done automatically as part of standard IT policy) such as Microsoft Active Directory, McAfee Managed Native Encryption (MNE) or Microsoft BitLocker Administration and Monitoring (MBAM) and the helpdesk technician needs access to that database. This solution is compatible with Windows Vista, Windows 7 and Windows 8 and is suitable for on-demand 1:1 type scenarios but it is not suitable for automated 1:Many type scenarios.


Windows PowerShell: Using Intel AMT and Windows PowerShell it is possible to execute a PowerShell script on a central server or IT helpdesk workstation and have that script automatically retrieve previously escrowed BitLocker recovery passwords from a backup database, remotely connect to an encrypted Intel vPro system and use Serial-over-LAN (SOL) functionality to automatically input the recovery password to the pre-boot authentication screen to unlock the encrypted drive so that Windows can boot. This scripted approach automates the entire encrypted drive unlock process and can be invoked on-demand by a helpdesk operator or scheduled to run when systems need to be patched. This solution can be used with systems connected over a wired or wireless network and connected directly to the internal enterprise network or through a CIRA session. This solution is compatible with Windows Vista, Windows 7 and Windows 8 and is suitable for on-demand 1:1 type scenarios and automated 1:Many type scenarios. The video at http://www.youtube.com/watch?v=2ioN5BlD96Q shows an example of such a solution working. A consideration for using this with BitLocker is that when the recovery password is being automatically entered into the pre-boot authentication screen, the password is momentarily visible to the end user. If this is an issue then the recovery password could be programmatically changed as part of the IT procedure associated with unlocking systems.


McAfee Drive Encryption: Using Intel AMT, McAfee ePO Deep Command and McAfee Drive Encryption (MDE) 7.X it is possible to configure MDE policies so that the MDE pre-boot authentication code automatically retrieves a disk unlock password from the centralized McAfee EPO server using a Serial-over-LAN (SOL) connection and uses this password to unlock the encrypted drive so Windows can boot. The Serial-over-LAN connection between Intel vPro systems and the McAfee EPO server can be made over a wired or wireless LAN and systems can be connected directly to the internal enterprise network or through a Client Initiated Remote Access (CIRA) session. MDE supports a variety of unlock policies including the ability to limit the number of consecutive unlock operations, the ability to control the times and weekdays when unlock operations are valid and the ability to configure unlock operations to operate inside our outside the enterprise network. This solution is compatible with Windows Vista, Windows 7 and Windows 8 and is suitable for on-demand 1:1 type scenarios and automated 1:Many type scenarios. It is worth noting that this solution operates automatically with Intel vPro systems regardless of whether they require user consent or not.

There are some situations in which it would be nice to be able to export and import Intel Setup and Configuration Service (Intel SCS) provisioning profiles...


  • Environments with multiple Intel RCS servers to accomodate provisioning workload where profiles need to be duplicated across servers
  • Environments with multiple Intel RCS servers because of organization administration demands (i.e. politics, segregation...) where profiles need to be copied across servers
  • Situations in which it is required to simply backup and restore profiles



Exporting profiles from Intel RCS is simple enough; from the Intel SCS console you use the toolbar to export profiles to an encryted XML format file. But there is no import function on the Intel SCS console to import profiles from a backup file or another Intel RCS server.


So here's a simple solution; Intel RCS supports a WMI provider which is used to communicate with other software such as the SCS console and ACUConfig utility. Intel SCS provisioning profiles (amongst other things) can be read and written using this WMI provider. Windows PowerShell includes built-in cmdlets to provide easy access to WMI providers. With a little effort we can construct a couple of lines of PowerShell script to do everything we need to export, backup, restore and import profiles with Intel RCS servers.


The following code reads all Intel SCS profiles from an Intel RCS server and stores them in a PowerShell variable...


# Configure source RCS server
$SourceRCSServer = "SourceRCSServerHostname"

# Read profiles from source RCS server
$RCSProfiles = Get-WmiObject -Class "RCS_Profile" -Namespace "root/Intel_RCS_Editor" -Authentication PacketPrivacy -ComputerName $SourceRCSServer


Once we've read all the profiles, we may want to back them up. The following code copies our prevously read profiles to a backup file...


# Save profiles to backup file

$RCSProfiles | Export-Clixml .\ProfilesBackup.xml


Sometime later we may want to restore our profiles. The following code restores our profiles from the backup file to a PowerShell variable...


# Restore profiles from backup file

$RCSProfiles = Import-Clixml .\ProfilesBackup.xml


And finally, if we want to write our profiles to one or more Intel RCS servers, the following code writes our profiles from a PowerShell variable to Intel RCS...


# Configure one or more destination RCS servers
$DestinationRCSServers = "DestinationRCSServer1", "DestinationRCSServer2", "DestinationServerN"

# Write profiles to destination RCS servers
foreach ($DestinationRCSServer in $DestinationRCSServers)
   # Read and delete any existing profiles on the destination RCS server
   Get-WmiObject -Class "RCS_Profile" -Namespace "root/Intel_RCS_Editor" -Authentication PacketPrivacy -ComputerName $DestinationRCSServer | Remove-WmiObject


   # Write all profiles to the destination RCS server
   foreach ($RCSProfile in $RCSProfiles)
      Set-WmiInstance -Class "RCS_Profile" -Namespace "root/Intel_RCS_Editor" -Authentication PacketPrivacy -ComputerName $DestinationRCSServer -Arguments @{ElementName=$RCSProfile.ElementName;InstanceId=$RCSProfile.InstanceId;Text=$RCSProfile.Text;ProfileDescription=$RCSProfile.ProfileDescription;SolutionGUID=$RCSProfile.SolutionGUID;SolutionName=$RCSProfile.SolutionName} | Out-Null


All of the above code assumes the currently logged on Windows user has access to the Intel_RCS_Editor WMI namespace and appropriate DCOM permissions on the Intel RCS server (see the Intel SCS Users Guide for information on configuring these permissions during Intel RCS installation). The example code can easily be enhanced, for example scheduling it to run regularly to automatically synchronize profiles across multiple Intel RCS servers or by using PowerShell's filtering capabilities to save some profiles and delete others.


Two cautionary notes:


  1. The code shown above to backup profiles to a file does not encrypt those files, therefore any plaintext credentials in the profile (e.g. the MEBX password, a fixed AMT admin password, AMT digest credentials or KVM RFB password) will be visible in the backup file. The Intel SCS package includes a file encryption utility called SCSEncryption that can be used to encrypt/decrypt profile backup files or the files can be stored such that they are only accessible to authorized personnel.
  2. Profiles containing Microsoft Active Directory domain accounts, domain groups or certificate template information are tied to specific Active Directory installations because profiles store domain account, domain group and certificate template information by SID information rather than by name. SID's are specific to individual Active Directory installations therefore profiles cannot be transported between installations if they contain domain accounts, domain groups or certificate template information. So this means you can use the above scripts with Intel RCS servers if they are all part of the same Active Directory structure (which is typically the case with most organizations). But profiles containing domain accounts, domain groups or certificate templates cannot be copied between different customer environments or between customer test environments and production environments if they are based on different Active Directory installations.


Details of the Intel SCS WMI provider classes and methods are available in the downloadable Intel SCS SDK at https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=20921


Hi All,


First time posting, so hopefully I give enough information.  The environment is a SCCM 2012 R2 / HP EliteDesk 800 and HP Folio 1040 G1.  I am wanting to get Out Of Band Management working so that clients can KVM at a BIOS level and initiate PXE boots remotely.


I have roughly followed this guide (with input from this community and technet) ;



I have created internal certificates as per the guide.  I have deployed the configuration profile as per the guide.

I have not used a third party certificate as i'm not sure where to load it into (I do have a GoDaddy Certificate if required).

I have installed SCS / Vpro integration with SCCM and have the collections / task sequences and packages. 

The problems I am facing are;

1) In SCCM, machines are not changing status from "Detected" or "Not Supported", I only have about three that say "externally provisioned"

2) The ones that do show as externally provisioned - I am unable to Vpro to, they have done a few different behaviors (probably depending on the tweaking i've been doing) and will either a) Connect and prompt for user permssion  (only had this on one machine and can't replicate it.  Also would like to not use user consent).

                    b) either connect and then disconnect straight away

                     c) not connect - host not found

                    d) not connect - machine actively refused connection.

3) SCCM seems to be adding the wrong computer object, example machine name PC1234, SCCM is adding PC1234ime.  I have excluded the AD container that houses the IME objects, from SCCM discovery so it shouldn't be seeing them.  The problem with IME objects being in SCCM, is that it stops it's native remote control from working as it should be looking for it's real hostname.

I have been at this for about 4 weeks on and off for a client and it is driving me crazy.  Please help and let me know if any log files are required etc.

Thanks in advance,


With the release of Intel 4th generation core vPro processors comes new AMT versions, 9.0 and 9.5. This means that some of our favorite Use Case Reference Designs (UCRD) need driver updates. Well, fret no longer; 2 stage boot (iFast) and Remote Drive Mount (RDM) have been updated.


For those not in the know, RDM is a remote repair use case. Basically a technician can access the hard drive(s) of a remote system at the block level, even if Windows will no longer start.


iFast is a "building block" use case that makes remote booting faster, making it feasible to use larger ISOs, like WinPE, for remote repair and/or OS imaging. Check them out below


Remote Drive Mount

2 stage boot


Jake Fritz, vPro Expert

Read other posts from Jake


Intel Control Center software

Posted by WA07 Feb 17, 2014

I need to download Intel Control Center software to replace what I inadvertently uninstalled.  What version of Intel Control Center software is compatible with a notebook, Windows 7, 64 bit.?

Things are changing around here! Do you want to receive support direct from an Intel engineer? Intel® Business Support is a new portal designed to provide faster, more personalized assistance. Users submit tickets, track their tickets’ progress, and get their environment up and running faster within the Intel® Business Support website. Users are eligible to submit tickets by filling out a quick enrollment form.


If you choose not to enroll, you can access community-based support at the Intel® vPro™ Expert Center. The community, however, will no longer be supported by Intel experts. The only way to get assistance direct from Intel will be by enrolling. Enroll now and get your environment back on the fast track to success!


Intel® Business Support

Getting your business back to what’s important, faster.


This simple Infographic illustrates the benefits of utilizing Intel Setup and Configure Software (Intel SCS) in your enterprise IT environment. Discover, configure & manage many Intel capabilities in your environment. For more in depth details, visit> http://intel.ly/1gq07yA




Filter Blog

By date:
By tag:
Get Ahead of Innovation
Continue to stay connected to the technologies, trends, and ideas that are shaping the future of the workplace with the Intel IT Center