Maybe its the requirement of a UNC path instead of a drive letter path?
You're going to a P:\Images\... instead of a \\server\share...
Maybe thats the issue?
Good thinking but no, the drive is mapped in the first action to give the template access to the share, tried it both ways.
Any juicy details in the provisioning log file under x:\ldprovisioning? Might be something in that to shed some additional light on the matter.
What happens when you enter the capture command yourself in a cmd prompt, after the Provisioning fails, but still in WinPE?
The validate button had validated a path to P:\Images\WIN7.wim. The previous action mapped a drive to P:\Images so of course when imagex was looking for P:\Images\WIN7.wim it should have been looking for P:\WINT7.wim... On clicking "Validate" I would have thought this would have been picked up as not correct....Not the best name for that button!!
1 of 1 people found this helpful
I'm one of the developers on the provisioning team and I just wanted to let you know that I saw this thread and we'll be having discussions about it. The validate button right now just validates that something exists in that field because provisioning allows for the use of variables, some of which can be defined at the device level, so it wouldn't even always be possible to find out what the path really is, much less check that the wim file exists there. I agree that the term validation would imply doing a bit more than that, and it's something we've talked about.
I don't have any kind of feedback on how or when we'll get this resolved, but I just wanted to show up and let everyone know that we do pay attention to the forums and we try to become aware of what your problems are as we determine how to shape our product.
Let me know if you have any questions or feedback on this.