Intel Communities: Message List

Re: Teleport Extender Error: Error connecting to server

webadmin@intel.com — Tue, 26 Feb 2013 18:37:49 GMT

I have a desktop and laptop connected to home network - one via wired other via wireless. Android phone connected to home network via wireless. Able to connect Teleport Extender to desktop but not to laptop.

At first I thought it might be due to VPN client on laptop. The laptop is "seen" by the Android phone... but unable to connect.

Connection worked the first time with the phone to desktop... but ultimately I'd like to see phone to laptop since that is the unit most often used in my case.

Aside from multicast DNS, what other ports\security settings might be affecting?

Re: TV screen is black after connecting to ntv300sl

webadmin@intel.com — Thu, 03 Jan 2013 19:43:28 GMT

experiencing same issue.

Had access to other WiDi devices via local contacts\resources - Belkin, NetGear Push2TV, etc. All of those worked perfectly. Sadly - the NeoTV (NTV300SL) connects without video... sometimes a mouse cursor is shown, sometimes not.

At first I suspected my laptop setup\drivers was the issue. Tried a second laptop. Same results.

Checked properties\firmware of the NeoTV NTV300SL unit:

Hardware version: 2.0.0.0
Firmware version: 2.1.0.0

The NTV300SL doesn't indicate any firmware updates available during the setup menu\process.

Other WiDi adapters checked all have hardware and firmware versions well above these values.

Re: Valid certificate for PKI configuration not found. (0xc00007e5)

webadmin@intel.com — Fri, 26 Oct 2012 22:09:02 GMT

One of the following items is likely causing the error:

The internal self-signed root hash was not properly set in the firmware
The self-signed certificate is not loaded in the correct certificate store for "rcsuser"
The self-signed certificate is missing private key or correct certificate details\settings

On the HP laptop, run "ACUconfig SystemDiscovery". The resulting XML file should include your custom root hash as an "Enabled" indicator next to it.

Additional insights on using Self-Signed Certificates shown in document for McAfee Community. My intent in directing you to this article is to re-use a recent posted\validate document, not necessarily to advocate on console\solution over another. See section for "Using a self-signed remote configuration certificate" at https://community.mcafee.com/docs/DOC-4211.

- TC

Intel AMT & Console Interoperability...Interested to know more?

webadmin@intel.com — Fri, 15 Jun 2012 15:06:35 GMT

How many consoles can talk to a system where Intel AMT has been configured? Although only one console\session can occur at a time - any number of consoles\applications can talk to Intel AMT. The trick is ensuring the Intel AMT configuration is compliant to the various console\application requirements within your environment.

There are three common steps:

Detection of Intel AMT by the console. This often includes Intel AMT version and configuration state
Configuration of the console\application with appropriate credentials and settings to communicate to Intel AMT
Configuration of Intel AMT to work with the target consoles or applictions within your environment

Some consoles, such as Microsoft SCCM or LANDesk, expect to own the configuration of Intel AMT. Other consoles, such as Altiris CMS or McAfee ePO Deep Command, may have specific Intel AMT configuration requirements yet are flexible in that an external utility (i.e. Intel SCS 8) can configure Intel AMT. Scripts and utilities such as Intel vPro PowerShell Module only require the correct credentials and certificate information are provided at the time of execution.

Last week in my lab, I did a quick test where the LANDesk console configured Intel AMT and a McAfee ePO Deep Command solution was able to use the technology. Recent customer scenarios have led to Altiris\McAfee, SCCM\Altiris, SCCM and RealVNC Viewer Plus, SCCM\Altiris\McAfee, BMC Marimba and vPro PowerShell, and so forth.

Are you interested to know more on how this is done? Write a comment below.

Re: How are you using the Intel SCS8 Deployment Guide?

webadmin@intel.com — Fri, 11 May 2012 15:40:08 GMT

The root certificate thumbprint (ArrowImage, starting with 6a)

Before you proceed with that - please understand that your Intel AMT client is configured. Once the initial configuration has been completed, you can adjust the configuration to add AD\Kerberos and TLS using the Intel SCS8 Delta Configuration process. For more information, see the Deployment Guide linked from http://www.intel.com/go/scs and attached for convenience

The remote configuration approach with the certificate is used ONLY if the other initial configuration approaches are not possible\preferred in your environment. In my view - if you must enter the MEBx to insert a custom certificate hash, you might as well complete the initial Intel AMT configuration.

In the Intel SCS8 deployment guide, focus on sections 4 through 6, and the necessary Appendix sections for the additional options desired. Section A.3 focuses on AD\Kerberos integration, and section A.4 focuses on TLS.

Re: How are you using the Intel SCS8 Deployment Guide?

webadmin@intel.com — Thu, 26 Apr 2012 15:58:41 GMT

Hi Mohammed - I have a few questions for you and will provide further guidance in in response to your inquiries.

What management console and Intel AMT operations are you planning to use?
Did you know the "ProvisionServer" DNS record is actually not required? (In fact - I often recommend that it not be used)
Have you reviewed the SCS 8 Deployment Guide? Focus specifically on sections 3-5 - determine what you have, configuration options, and apply only ONE configuration approach. Section 4.3 in particular provides a simplified decision tree on what method to use.

In my view - if you must touch each system to enter a custom root certificate hash, why not configure Intel AMT with basic settings instead? You can then use the "Delta Configuration" options mentioned in section 6 of the Deployment Guide to adjust the Intel AMT configuration as needed.

However, if you must use request and install a remote configuration certificate from an internal CA, see http://technet.microsoft.com/en-us/library/cc161804.aspx#BKMK_AMTprovisioning. (Specifically the section "To request and install the AMT provisioning certificate from an internal CA").

I reviewed your attachment and the steps look correct overall. On the "Configure CA Name", you can adjust the common name to an easier string such as "testCA". This will help later on when select TLS certificates as part of the Intel AMT configuration profile.

More information on TLS in the Intel AMT configuration profile available in section A.4 (4th main section of the Appendix) in the SCS8 deployment guide.

I hope that helps in your testing of Intel AMT.

- TC

How are you using the Intel SCS8 Deployment Guide?

webadmin@intel.com — Tue, 10 Apr 2012 16:07:01 GMT

With the release of Intel SCS 8 (See http://www.intel.com/go/scs), a Deployment Guide was also posted.

The Intel SCS 8 Deployment Guide provides an accelerated view into getting Intel AMT configured, how to adjust\maintain the configuration, 4 common deployment models, and summarized steps on how to apply the most common configuration options. Common Intel AMT configuration options include adjusting the FQDN of the firmware, customized authentication\authorization, Active Directory integration, securing communications via TLS, and Intel AMT over wireless.

How are you using the Intel SCS 8 Deployment guide for your environment?

Re: Redirection not working on Altiris 7

webadmin@intel.com — Thu, 01 Sep 2011 20:13:32 GMT

Best to contact Symantec support to further troubleshoot the issue.

Re: Got errors when using scs console to discover vPro clients

webadmin@intel.com — Thu, 19 May 2011 16:34:54 GMT

Take a look at http://communities.intel.com/community/openportit/vproexpert/blog/2011/04/29/troubleshooting-tcpconnect-wsman-soap-and-related-intel-amt-connectivity-errors

Based on the sequence of events using PID\PPS - where the setting of the ACL failed yet other setting succeeded - I suspect there is an incorrect setting in the configuration profile. It's a guess. If you follow the steps shared in the above article - this will provide some definitive answers.

Hope that helps.

Re: Got errors when using scs console to discover vPro clients

webadmin@intel.com — Mon, 25 Apr 2011 22:39:39 GMT

The nature of the errors with tcp_connect() indicates the network interface of the management engine is closed or disrupted during the configuration process. A number of items could cause this to happen. Outdated firmware, incorrect domain setting in the configuration profile, etc.

After reading through the replies and some of the attachements shared - I am curious to know what the AMTdiag tool results were for your environment among other items.

Please ensure the BIOS\firmware is updated on the client. The Intel AMT firmware specifically should be above 3.2.x for this particular system.

What is the "domain" in your configuration profile? This setting should align to the DHCP option 15 on the network segment.

You appear to be using Intel SCS 5.x. What exact version? (check "AMTconfig" in windows servers, or click on Service Status within the Intel SCS console)