Intel Communities: Message List

Re: Intel AMT within SCCM 2012

webadmin@intel.com — Mon, 15 Apr 2013 20:25:37 GMT

Stéphane,

The AMT functionality in SCCM 2007 is the same in SCCM 2012, including automatic provisioning. Additionally, the add-on that we have produced that adds KVM Remote Control and Alarm Clock functionality works with SCCM 2012. It is available here: https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21835

If you are looking to migrate, I recommend reading through Microsoft's documentation on the subject:

http://technet.microsoft.com/en-us/library/gg712672.aspx#Plan_Migrate_AMT

-Dan

Re: Not shows me the page to enter https://FQDN:16993

webadmin@intel.com — Thu, 19 Apr 2012 20:58:38 GMT

Were you able to successfuly provision the client with SCCM? When you access the AMT WebUI on port 16992 does it ask you to log in, or does it give you any error messages?

Re: 2215-EIT failure. VA boot record read failure please help me

webadmin@intel.com — Mon, 09 Apr 2012 15:44:36 GMT

Have you tired the solution from HP in my message further up in this thread?

Re: Trigger_ros.iso won't launch

webadmin@intel.com — Fri, 09 Mar 2012 17:28:11 GMT

Lets's start with getting some additional info, what AMT version is running on your client and what management software are you using to launch the ISO session?

Re: AMT Provisioning Issue

webadmin@intel.com — Fri, 09 Mar 2012 17:34:24 GMT

I've got a couple of questions. First, what is the key size of your AMT provisioning certificate? Second, could we get additional log detail for the provisioning attempt? Ideally, we'd like to see all the log entries for that provisioning attempt to get a better idea of what's happening.

Re: AMT with TLS and Self Signed Certificates - challenge

webadmin@intel.com — Fri, 10 Feb 2012 23:29:28 GMT

Lets start with the question of having to touch each system. If you want to create your own provisioning certificate you will need to touch each one. This is needed to insert your own custom root CA thumbprint so that AMT will trust your provisioning cert. You don't ahve to do this if you can purchase a provisioning certifcate from a third party. If you want to order a provisioning certificate from a third party you will need to make sure that your current DNS domain is a publicly registered one. That's a requirement for the verification process that third party CA's use.

Have you looked at doing host-based configuration instead of remote configuration? No provisioning certificate is required for this provisioning mode. All you need it local admin rights to run it on your vPro clients. One thing to keep in mind with host-based configuration is that user consent for KVM Remote Control and boot redirection (IDER sessions, boot to PXE, etc) is manditory and cannot be disabled.

As for DHCP versus static IP addresses, you are in good shape with AMT 7. You have two options when you configure your clients. You can either go into the MEBx and specify the IP address, or, make sure you install the AMT driver stack, which will detect the OS network settings and apply them to the Management Engine for you.

For details on creating your own provisioning certificate for remote configuration, take a look at the SCS 7.1 user guide available in the Intel AMT Setup and Configuration Service here: http://software.intel.com/en-us/articles/download-the-latest-version-of-intel-amt-setup-and-configuration-service-scs/. The details are in apendix B. You can find a lot of other useful information in this guide as well.

Re: vPro remote KVM on Q67 boards with aditional NICs?

webadmin@intel.com — Wed, 11 Jan 2012 18:26:23 GMT

My setups will very depending on my needs at the time. I'll use anything from a laptop to a high end desktop system loaded with as much RAM as I can get. I typically use two NIC's so I can have my VM environment completely isolated from my other management network.

Re: vPro remote KVM on Q67 boards with aditional NICs?

webadmin@intel.com — Mon, 02 Jan 2012 18:14:42 GMT

The configuration you are describing should work fine I use similar setups myself for the same reason you are describing. Just remember that you only get AMT capabilities via the on-board NIC.

-Dan

Re: Deploying vPro for the first time

webadmin@intel.com — Mon, 28 Nov 2011 17:08:04 GMT

Yes, SCCM can handle that task just fine. Set it up like any other software package you want to distribute and you're set. You may want to look at using a task sequence (under OS distribution) as part of this process. It gives you the ability to specify the account that the ACUConfig software package will run as.

Re: Deploying vPro for the first time

webadmin@intel.com — Thu, 10 Nov 2011 18:26:25 GMT

Have you tried restarting the RCS service since you added the provisioning cert to th cert store?