I have been troubleshooting my vpro for 8 months and consistent and easy provisioning it is not. As the discussion title says not consistent\not working.
Here's what I've found.
I have about 600 laptops, same model. out of 3000 that have mostly all zeros in the amt info in thier inventory. Unprovisioning does no good. Running a scsdiscovery grabs the same info out of the AMT firmware chip and puts it into the registry. I have concluded the manufacture did not turn these chips on. As a note I have some older computers with Vpro not turned on that give the same info in the amt inventory.
Also laptops that run wireless and wired give varying results when provisioning. If the computer is running wireless and Landesk has it registered under the wired ip you'll see in the log that it trys the wireless ip and fails. If the wireless is turned off then it will provision if the DNS server has deleted the wireless IP. And then theres DNS. In the DHCP registrations you'll see usually both wired and wireless IPs registered but in DNS there may be only one, it could be the wired or wireless ip. Sometimes I get them to provision by adding in the IP in DNS of the IP that is missing on both the DNS server at the site and the one my remote console gets its dns from, otherwise you have to wait for replication among the sites.
I have seen in the log where when i click the Setup and configure for computer X under the vpro options it trys provisioning computer Y. This I found was due to (my theory) when I looked in the computer X's registry in the Hklm\software\intel\scs7\scsdiscovery a ip is listed that matches Computer Y (Note the IP in the landesk console for Computer X is the correct one). Why does this happen? The only time I know of that a scsdiscovery is run (this grabs info from vpro chip and populates a registry file) is when the agent is installed.(Or in 9.5 selecting the vpro option Setup and Configure)
So at that time when the computer had the agent installed the IP of Computer Y did belong to this computer and must have been populated into some amt section of its Landesk database.
What I have have to do is since I already ran the setup and configure option which repopulated the registry with the right ip I then run a full inventory scan which copys that info from the registry to the database with the correct IP. So now run Setup and Configure again and it usually provisions.
I also recommend NOT using TLS On. Why, because I started that way and now I have several thousand computers that got a expired certificate so when you go to https://computer:16993 you can't get in. Another note here is my IE9 refuses any https://computername:16993. After googling I found out not all browsers act the same with secure urls. I had to download Firefox to get into any Https://computername:16993 that didn't get the bad certificate. So because of this I recommend not turning on TLS.
I want to add that I have had only one certificate in my cert store so I have no idea how this bad certificate happened. Firefox lets me view the certificate and it has little info and a expired date.
The few computers I have got my hands on with this problem I tryed manual unprovisioning and it went back the same way it was after re-provisioning.
Yesterday I was able to get another computer with this problem and it successfully unprovisioned and re-provisioned so I am scratching my head at this problem.