I had same problem with LD9 SP3. You had to run a inventory or status before getting the full benefits of Vpro.
Sorry but I had moved to LD 9.5 without figuring out that problem. However since spending so much time troubleshooting so many problems with Vpro I have a suggestion.
In the inventory look down the list for provisioned, I bet it has a 0. If it does or doesn't try running a scsdiscovery. Since i can't figure out how to attach a file I'm putting the contents of my bat file you can push out from landesk.
This pulls info from vpro chip and puts it into registry.
Cd "c:\program files\landesk\ldclient"
scsdiscovery.exe /output silent systemdiscovery /nofile
If "%errorlevel%"=="32" exit /b 0
You need to run a full sync inventory after this, you could add another line with the inventory scan as a all in one .bat file.
In upgrading to 9.5 I had to go back and do a Setup and Configure Vpro to get those computers that were already provisioned to work right.
What i mean by this on the right click menu on a computer, the vpro options would be grayed out except for the Setup and Configure vpro option. The setup and configure option runs scsdiscovery and also starts amtconfig.exe which starts the hello packets.
If the above .bat file does not help try adding a line to run the "c:\program files\ldclient\amtconfig.exe"
Thanks for your comments Mrgadget.
Updating 9.0 to 9.5 -> Okay, is not so bad, if the only thing that we have to do is Setup and Configure vPro and the problem is resolved, Okay.
Remote control via Intel KVM -> Okay, is good to know more people apart of me are having the same problem, So, while nobody say another thing, if redirection ports 16992 and 16994 are not enough to do remote control wiht KVM (AMT authentication), we'll do with intel vPro Options -> Status... and wait for 5900 port will be opened, then KVM will work. Okay.
In both issues the problem is resolved with right click mouse, So, it is not a so hard job. I think that there are worst things. So we´ll do a effort and we'll survive with this issues.
We have used scsdiscovery Intel tool only for troubleshooting, with this parameters:
SCSDiscovery.exe /Output file test.xml SystemDiscovery /NoRegistry
this generate a xml file, and you can see the state and values inside Intel AMT. But this intel tool is used for us only for troubleshooting, we want only to use LANDesk Management Console to activate and use vPro.