vboot really does not have any connection with your PXE server when being deployed as a scheduled task. All the tasks come back from the core. can you post your OSD log and we might be able to get some more info on this. They are on \\%coreserver%ldlog
When you schedule your OSD task, the name of the task will be in the title of the log file. You are in the right area, it just might be further down.
hi again EMiranda.....
Only log I seem to be able to locate is as attached. Maybe (hopefully this will make some sense to you??)
Yesterday OSD worked fine, all I did was update (manage) the drivers in WinPE as I had a model laptop not connecting or being recognised by WinPE to get an image pushed out to it....
maybe this somehow is the cause of the problems?
provisioning.log.zip 173.1 K
can anyone help with this issue???
I really need to get this resolved asap.
are you scheduling an OSD task or a Provisioning task? they are different things, you mention scheduled an OSD task in your post, yet you provided provsioning logs, so right now I am a little confused.
Thanks for the quick reply...
I am scheduling an OSD task. I couldn't find any log file you mentioned on the Core. So I looked on the PXE Rep - and found that provisioning log...! I was hoping it would be of some use.
I have had no luck with removal and re deploy of the PXE Rep following the removal of the driver added to the WINPE Image (as advised by a LANDesk support agent).
See a small screenshot of the task - the device (and all new devices) fail to get an IP address - is this correct until the image is pushed out??? I thought they got an address immediately.
The status of delayed indicates a provisioning task. I know you are trying to do an OS deployment, but are you using the OS Script technology or the Provisioning technology. As EMiranda said they are both VERY different things. Basically are you deploying a script or a template?
It is a Provisionig Template. Sorry for the confusion.
OK, Thanks for the updated info. What actions are you taking, and where do you see the error? A screenshot of the provisioning template results with the detail screen showing would be invaluable, if that's possible.
Actions taken =
Remove drivers from WinPE Image that I added.
Remove PXE Rep.
Re-deploy PXE Rep.
Reboot server (as a long shot!).
The error appears during the 1st phase of WINPE... >
too much stuff to type now, but the last step is the error as stated in the call title.
Sorry I used some confusing terminology. I'm wondering if you could tell me which Provisioning actions are taken in your Provisioning template (ie, what is the template trying to do).
Please let me know.
if your winpe is erroring out at x:\Windows\system32\cba8\LDDrvload.exe
that quite could be possible it is related to you injecting the driver into your winpe.
did you create a backup of your boot.wim? One easy test is to restore the backup of the boot.wim and try again and see if it does not error out, if you dont have a backup, try just removing the driver that you just installed and see if you can go further with out an error.
I am sure it is the driver I originally added to WinPE that has screwed this up - as the problem arose shortly after.
We should have a backup of the boot.wim (and the whole server!) from a week ago, so I could try restoring that and then re-deploying PXE Rep.?