Bloop

And here is additional information and even a resolution: I have been using "optional" deployment in my past attempts. When using "mandatory" deployment everything works as expected. Although the script that should delete the machine from the collection fails, but this is not really important. My log shows the "SMS_PXE_SERVICE_POINT" correctly ordering the machine to boot normaly ("abortpxe.com") on all subsequent boot attempts after sucessfull installation. Well I suppose this behaviour is intended. For my operating system delopyments I will use "mandatory" in the future.

I did some more investigating and I did susspect to be a victim of the PXE Flag Bug but I am not. I have implemented a script that reacts to Message ID 11171 and deletes the machine from the collection but I do no get this far. My log shows the "Task sequence engine" with ID "11142" "initiated system reboot" but a couple of seconds later I get "SMS_PXE_SERVICE_POINT" with ID "6311" "according to deployment <ID> machine will start with boot image <ID>" This is essentially the first reboot which should take the system into the installed environment.

Dear community, I have been setting up SCCM 2012 R2 for the last couple of weeks and have already learned a lot, however excessive googling and reading how-tos has not answered my question and solved my problem: After PXE deployment, what component is responsible to stop the advertising and when? After successfull OS deployment (Windows 7) the first reboot takes me straight to WinPE again. I have setup my machine to do PXE boot first (before any HDD) and disabled the F12 hint so I can do an unattended installation. Currently I am not doing anything unattended for trouble shooting. The installation process does work as long I remember to skip PXE manually and the OS is deployed correctly. Could you provide hints on where to look for logs and information? Best regards Bloop