Intel® vPro™ Platform
Intel Manageability Forum (Intel® EMA, AMT, SCS & Manageability Commander)
Intel® Endpoint Management Assistant (Intel® EMA) Cloud Start Tool for Azure* 2.0 is now available for download here.

The Intel® Manageability Commander 2.2 has been released! Learn more here.

The Intel® Endpoint Management Assistant, version 1.6.0 is now available for download here.

The Intel® Setup and Configuration Software tool will End of Life (EOL) on 12/31/2022. The Intel® Setup and Configuration Software Download will be available until March 31, 2021. For details, Please click here.
2565 Discussions

Stand-alone SCS or integration with SCCM? Both?


In our environment WOL is inconsistent and unreliable for a number of reasons, mostly uncontrollable networking issues. We need the ability to reliably wake machines up on demand and on a schedule. This is all we need from AMT, nothing more.

  • We are willing to touch every machine to set up AMT.
  • We'd like to avoid certificates (lack of experience + Network team manages certificates).
  • We'd like to be able to wake up machines for both SCCM and Altiris, using integrated commands, or some external mechanism.

1) With that in mind, what is the least complex (not quickest) method to configure AMT?

2) Can vPro work independently while integrated with SCCM?


3) Will AMT simply not work at all in SCCM if certificates aren't used?


0 Kudos
5 Replies


  1. For your situation, running ACUConfig to apply your SCS profile on each computer would be the least complex way to configure AMT.
  2. vPro will work independently.
  3. SCCM requires TLS communication with AMT. SCS integration will also require the use of Kerberos.

Once configured you can power them up on demand, or on a schedule using the AMT Alarm Clock feature.


Thanks for the input Alan. If I decided to try to tackle TLS so I can use AMT with SCCM, is it possible to set up SCS as an independent installation and then just "plug" it into SCCM later? (As opposed to doing everything via the Add-on 2.0; or would the Add-on be the better route?)


What is tripping me up the most is the TLS issue. It seems most of the documentation assumes a solid familiarity with certificates, but our team has never used them. I understand the importance for security, but the complexity is certainly an obstacle. Is it possible to have full AMT functionality without the use of certificates? (only using PSK?)

There seems to be so many versions, variations, and variables with vPro/AMT/SCS that it's hard to know you're starting on the right path. Maybe I'm an idiot but I could certainly benefit from some decision flowcharts :-O



Yes you are able to setup an SCS server separately. Then at a later time use the SCS Add-on to integrate it into SCCM.

It's absolutely possible to have full AMT functionality without using certificates. You can achieve full AMT functionality with a basic SCS profile. That profile only needs to contain the mandatory system settings. Later, if you want, you can go back and reconfigure your vPro computers with a new SCS profile that includes any of the increased security options.


I need to develop a process that covers the spectrum, AMT 2.2 and up.

  1. The only way to do this, without PKI/certificates/CA, is to use the One-Touch (TLS-PSK) provisioning method, correct?
  2. After TLS-PSK provisioning, TLS communication isn't required. But if I decide to enable TLS-PKI later won't I need to manually install a new root hash, meaning all machines would have to be touched again?
  3. If TLS is only for encrypting the communication with a client, what protects the device itself? Digest passwords?

Later, if I want to integrate AMT with SCCM it will require a certificate. Either a Microsoft CA, or 3rd party certificate. Our network team says we have an internal CA, and we have a "wildcard cert from Entrust I may be able to use".


  1. From experience, which would be the least problematic, using an internal CA or the Entrust certificate? (Disregarding the need to the need to import it into the root of each device since Entrust is only for versions 7.0+)

Thanks so much for your help.

  1. Correct.
  2. This depends on if you use your own internal CA provisioning certificate or get a 3rd party certificate. Using an internally created provisioning certificate will require you to manually input the certificate hash into the MEBx of every AMT computer. However, certain 3rd party certificate hashes have been present in the MEBx beginning with AMT 2.2.
  3. Digest passwords and if you choose, Kerberos.
  4. Using a 3rd party provisioning certificate would be easier in the long run. All future vPro computers would already contain the certificate hash, which would mean less work for you.

As far as your current Entrust certificate, in order for it to work as a provisioning certificate it will need to have been created as outlined in this document.