Take out the Reboot action in your provisioning for 1. if it fails it will stay in WinPE and 2. you dont need a Reboot action if it is successful as CTOS already provideds the reboot.
If it fails again, and you are still in WinPE, check the actual log to the CTOS and see what it is telling you, that log is here:
In some of my experiences I have seen it fail if there is already a cmdline.txt c:\SYSPREP\I386\$OEM$, so I would just delete it and let CTOS create it.
Thanks you very much for the quick reply
I will give this a try
Hi, i resolved the issue following this troubleshooting action and osserving device behavior, i find that no action was taken, so the CTOS action could not be started at all, device in fact was not rebooted. I check the \\coreserver\ldlogon\provisioning folder and i saw that:
ConfigTargetoshandler.exe was not there so it was not on the boot.wim on the PXE (That's why no CTOS action satrted)
Confighandler.exe was not there (Agent install agent would have not work after all)
And LDWindowsprovisioning.XML was not complete with all the action, (genrally it contains all action list available and the sequence but it was truncated on many lines)
I replace all theese files from another Core Server same version (LDMS)+SP2), re-deploy PXE rep and now it works fine!
It was an upgrade's vicious, it's a bit strange,but it could happens!
If you need you could follow theese Troubleshooting steps
1 - On the core server backup all log files from the \\CORESERVER\ldmain\log folder. Then delete all files there.
2 - Boot your device from the PXE Menu selecting the option WinPE Provisioning.
3 - Once the device finishes booting close all the windows that might show - this means, do not start the provisioning process, instead close the window when it pops up.
4- Open a new command prompt window.
5 - Chang the path to X:\ldprovision
6 - execute -> ldprovision.exe -V 255 -c CORESERVER
Replace CORESERVER with the name of your coreserver and make sure to use a capital V in the '-V 255' option.
7 - Enter your credentials and start the provisioning process as usual.
8 - Once it fails collect all .txt and .log files from the X:\ldprovision folder.
9 - Collect all new log files from the \\CORESERVER\ldmain\log folder