I've just recovered my core from a bout of bad patches and for the first time in many months I have been able to use provisioning end to end without an error; specifically I have used PXE to boot a group of machines into WinPE where I select WinPE Provisioning and then run them through a lengthy Windows 7 deployment process.
So this was all great, but now that I have the machines up and running I can't run other provisioning tasks against them; the provisioning steps fail immediately. I'd like to know why.
Here is what I am trying to do:
I have a group of Win7 Pro 64-bit machines, all are alike, and I have just used provisioning to get the Win7 image down to them. They have all been configured appropriately and I can use the Win7 OS; they appear to work just fine.
...now I am trying to run another provisioning task against them which applies a bios configuration and a bios password. I am selecting these machines to run the provisioning task from the Win7 OS. When I do this and tell the task to START NOW, I observe the machines moving into the ACTIVE part of the schedule task, but then almost immediately they get dumped in FAILED. Sometimes when I try to do this against a single machine I notice that the scheduled task shows 1 active and 1 failed particiapant; this is when there is only 1 machine in the task...evidence that the task is failing immediately before it ever starts??? In any event the clients never show any hint of participating in a provisioning task.
When I look at the details for any given FAILED machine I see a result of NOT SPECIFIED and a return code of 0, or ZERO. If I select PROVISIONING HISTORY for the failed client I end up staring at a blank provisioning template...no details because there are no actions listed for it. If I get out of the scheduled tasks area and select PROVISIONING HISTORY from the actual client where it is found in NETWORK VIEW, I then see that my attempts to provision the bios on that computer are NOT listed in the provisioning history...it will instead show the most recent task which I actually was able to witness.
From the console I can remote control any of these failed machines and I can run inventory update requests against them. All other evidence shows that these agents are playing according to the rules...its only when I attempt to run a provisioning task against them that they refuse to play.
any thoughts on where I should begin to troubleshoot this problem?