I've had a few cracks at making vPro work in different environments and so far I have to say the results have been at best random and at worst completely useless. My latest attempt today is a perfect example of what I mean and I just thought I'd see if I could get the bottom of it because, on paper at least, LANDesk with vPro integration would be pretty powerful.
This is my test setup:-
Test device (Dell Optiplex 780) on my desk which supports vPro v5 and has the latest HECI drivers installed
PID/PPS ID's generated on the Core (LDMS9 SP2)
The vPro password has been set on the Core
The first task was to get my test device provisioned using the PID/PPS ID. I entered this information into MEBx and entered the IP of the Core Server in the Provisioning Server section (I don't currently have the provisionserver DNS entry). When I rebooted the machine I had to wait a while (about 15 minutes) but eventually my device appeared in the UDD tool.
I checked on the test device using Intel AMT driver interface and sure enough it was nowing showing as "configured". As a further test I connected using a web browser from the Core to http://<devicename>:16992 and was able to connect using the password I had set in LANDesk. So far so good.
I then wanted to test the right click functionality in LANDesk so I selected 'Intel vPro Summary'. This hung the console for about 5 minutes before eventually displaying the summary page but with no data in it. I checked the AMTConfigDLL.log on the Core and noticed a number of HTTP 401 Unauthorised errors and repeated connection attempts. I waited 5 minutes and tried to do the same thing again - right-click, Intel vPro Summary and guess what - it worked after about 30 seconds! Immediately after this I tried again and it failed!!
Very frustrating! Would appreciate any insight. I've attached two images of the vPro Summary screen - one when it worked and the other when it didn't.