no one could give me any suggestion?
1 of 1 people found this helpful
Are the working and nonworking machines identical ? Anyway, there is a LANDesk vpro patch available since a couple of days.
vPro is very specific to the security configuration in the BIOS. I have found that after I cfg BIOS (cn, mode, dhcp, etc) or re-provision vPro, the it was best to see if LANDesk could "see" the vPro event log - assumes LD agent on vPro client. If it could connect to the vPro event log with the LANDesk agent installed, then I started to work backwards one step at a time. Very laborious as it takes one reboot per chg. If you could not connect, it is a vPro sec issue.
You can use the Intel Dev toolkit to troubleshoot issues. http://software.intel.com/en-us/articles/download-the-latest-version-of-manageability-developer-tool-kit/
Attached is a doc written by Brett Twiggs and Kimber Barton. It also has good info.
Thanks for your reply, may i ask where is the LANDesk vpro patch? how can i get it?
Is it Landesk tech group found this issue and release a patch for a fix finally?
Thanks for your infomation, the attached doc is really useful for me, thanks again!