Several weeks ago we were running LDMS 9.0 SP1 and successfully using a VBOOT provision in our templates which allowed us to take a windows XP client from the XP OS into WinPE where it would pull down a Win7 Image. Those machines participated just fine and we made a number of Win7 deployments using our VBOOT-enabled template.
What happened next was that we were unable to take those, now Win7 clients, and use the same template to reimage them. Well we did the SP2 thing and applied a separate patch called "PRV-5265890" which was supposed to take care of this.
Anyway, now we have a problem whereby a machine that is running windows 7 will reboot with the VBOOT-enabled template and it will get into WinPE and clear the VBoot partition, but then it will stop participating in the task. The window goes away right after it successfully establishes contact with the console...if we manually reboot the client and log back into windows it will reboot again and right back into WinPE.
it pretty much loops again with the last statement in the CMD.EXE window showing that the WinPE session successfully contacted the landesk core....something something "success", but the window goes away and we're stuck in WinPE.
Another reboot takes us to the login screen but then the damn thing will reboot back into WinPE again if we log in.
The provisioning status for the machine shows that it is still RUNNING and that the final step in the first phase of the template, execute bootfile.exe, has not yet completed. Watching the progress in WinPE contradicts this because we know that the Vboot image was removed, otherwise the reboots would take us right back into WinPE rather than Win7.
Personally I think that the Vboot.WIM file, or whatever it may be called, is somehow hosed because it doesn't seem to permit a connection state with the provisioning template as soon as it gets into WinPE. Still, I have no direct evidence that this is the case as the correct device drivers are loaded with this .WIM and I know that I have not gone in and changed the .WIM nor the vboot instructions.
-anyone with a fix?