We have not had reports of any behavior like that. AMT\vPro is based in the hardware on the machine, and requires the correct drivers be installed for Windows even be able to interact with it. Do you see any of the processes for LANDESK AMT running on the clients at that point in time? (AMTConfig.exe SCSDiscovery.exe)
Have you been able to tie this down to an issue with vPro specifically?
it was something else.
my appologies for not closing this thread.