Filter
Top Products
Intel® vPro™ and Intel® Centrino® Pro Processor Technology Quick Start Guide
33
Export or Import Intel AMT IDs) that you enter the same password in the field that says “Specify Intel
vPro ME password (for Intel AMT 2.5 or greater only)”. This needs to be filled in for any Intel vPro
machine of 2.1 or greater.
Intel vPro machine was discovered through UDD (Unmanaged Device Discovery) when a network scan
was run, but the Intel AMT option and Move to Management Database option are grayed out.
This error will occur if you run a network scan on the segment the Intel vPro machine resides on and it
has not completed the provisioning process and does not have a LANDesk client agent installed. Use
the same troubleshooting techniques as listed in troubleshooting item #1
Intel vPro machine shows up in my managed device inventory, but none of the Intel AMT options are
available.
This is another symptom of the Intel vPro machine not completing the provisioning process. Please
refer to troubleshooting item #1 to resolve
A second log file is also available to help understand the link between the Intel AMT client, backend
services (provision server, DNS, DHCP, LDAP and AD) and also LANDesk Management Suite 8.8. The
second log file shows the actual process between the Intel AMT client, your Domain services, provision
server and LDMS. In the examples below you can see exactly what is happening between the Client (in
the provisioning process with RCT) and the backend infrastructure, the first example shows a successful
provisioning using the RCT process where the Cert and hash were utilized to do the actual provisioning.
Note the third and fourth entries where the Domain responded with the FQDN and the actual host name
of the client being provisioned. The rest of the log shows each action and the response from the client.
The second log file shows a failed provision process and if you look at the third and fourth entries you
can see that the Domain did not offer the FQDN in the third entry and the fourth line presents with the
clients IP address instead of the client name. This is a fairly common situation where the Domain does
not resolve to the client for some reason. Some of the problems here are multiple client names with
the same IP address in the DNS forward or reverse lookup zones, other problems can be if the DNS and
DHCP service do not cleanup or resolve released IP addresses. Poor infrastructure (whether
maintenance or implementation) is the lions share of why provisioning fails, the log files helps point you
to where the problems are.
1. From the LDMS VM open Windows Explorer
2. Select Program Files>LANDesk>Management Suite>AMTPROV
3. Open the AMTProvMgr2.log