Filter
Top Products
Intel® vPro™ and Intel® Centrino® Pro Processor Technology Quick Start Guide
32
Appendix A: Troubleshooting
Additional troubleshooting information can be found at the Known Issues, Best Practices, and
Workarounds wiki: http://communities.intel.com/docs/DO
C-1247.
Intel vPro machine not discovered:
The Intel vPro machine may not have completed the “provisioning cycle” with the LANDesk core server.
One way to tell this would be to look into the AMTDiscService.Log (AMT discovery service log) which is
located in the “Program Files / LANDesk / Management Suite” subdirectory. Note: This log file will not
refresh dynamically when you have it opened. It must be closed and reopened to refresh. If the client
has properly provisioned, there will be an entry similar to the following:
Wed, 27 Jun 2007 15:53:42 Incoming Connection from 192.168.0.101:16994
Wed, 27 Jun 2007 15:53:42 Hostname: client20
Wed, 27 Jun 2007 15:53:42 Incoming data (32) is:
Wed, 27 Jun 2007 15:53:42 Version: 2
Wed, 27 Jun 2007 15:53:42 Count : 0
Wed, 27 Jun 2007 15:53:42 UUID : F228CDC0-84FB-11DB-915E-0013D4D07748
Wed, 27 Jun 2007 15:53:42 PID : PID0009Q
Wed, 27 Jun 2007 15:53:45 Added to UDD list
There are a couple of interesting things to point out in this example. First, note that the incoming
connection is coming from the device’s DHCP address. Next, the hostname will likely be the hostname
that is registered in DNS for this client. If the hostname is blank in the Management Engine or a
different hostname exists (in this example the hostname in the ME was iDBO), the hostname passed to
the LANDesk core server will likely come from the DNS entry.
The next thing to note is that the PID entry is shown. This helps you to see that the initial
authentication has been accepted. Note then that the device was added to the UDD (Unmanaged
Device Discovery). Another entry you could see instead would be:
Wed, 27 Jun 2007 15:35:19 already in managed list (nodename), info updated
If you do not see these entries the most likely causes are:
You have not matched the PID / PPS pre-shared keys between the Intel AMT client and the LANDesk
core server. The keys generated through the LANDesk System Manager Configure | Intel vPro Options
| ID Generation must match those you entered into the Intel MEBx.
You have a mismatched Management Engine password. The password that you entered into the LDMS
Configure | Services | Intel vPro Configuration tab must match the strong password entered into the
Intel MEBx. If you entered this manually, make sure you have matched all capitalization, numerals,
and special characters. If you have used “one-touch” provisioning via the USB key, make sure when
you generate the keys to be exported (LANDesk Management Suite | Configure | Intel vPro Options |