We have a similar problem on some machines. Have you tried running an inventory scan on one of the clients with the /F /SYNC switches?
Yep tried that - still no joy. Strange that with these new machines it just doesn't seem to work.
If you are on 8.8 SP2 and these are using the newest AMT/vPro version (which they probably are, as they are new laptops), then you either need to go to SP3, or apply a patch. I believe the patch is AMT-20525. It enables vPro version 5 support. It also has a whole bunch of bug fixes and improvements. It's kind of like a vPro specific service pack.
If anyone is laready on 8.8 SP3 or higher, then this patch shouldn't be the problem, because it is included in 8.8 SP3.
Have you heard of any reports of this issue on SP3? I have a machine that has vPro technology and I have actually configured it on the client however when I go to the console I have no vPro options. Additionally, the AMT Information in the Inventory has a field for Provisioned, the values here should be 0 or 1 and this particular machine is just blank.
I was holding off for a couple of more weeks but we're going to go ahead and schedule our upgrade to SP3 this week. I should be able to let this thread know the results by the weekend.
Fingers crossed - real bad experience with the SP2 upgrade
I understand the fear after SP2. I can tell you that SP3 is a MILLION times more stable. Let me know how it goes when you update!
Mach6 is correct both in stating that LD8.8 SP3 is worlds better than the original SP2 and that SP3 has many updates to the vPro capabilities in LD 8.8. The Lenovo T400 is Intel's latest laptop processor (Montevina) and utilizes the latest vPro release 4 (5 for the McCreary desktops), SP3 does address many of these updates and should help you with the issue you are seeing on the T400.
We upgraded this morning to SP3 and yes it was very painless compared to SP2.
I haven't had the chance to test to see if the vPro problem is cleared yet but should be able later this evening.
On another note - does anyone know what version number VULSCAN.EXE should be after upgrading the workstations to SP3?
I've upgraded the Core, my remote console, and then set SP3 to autofix in Security and Patch Manager.
I've done a Security Scan on a couple of systems but didn't see the SP3 apply. The current reported version of vulscan.exe on the 'test' system is 184.108.40.206