Gary Jack

After failing over in VM Ware one of our DPs we now seem unable to PXE build anymore. We have looked through the log files but can not work out what is causing our Task sequence to fail now. We have attached a copy of the log file from a failed to build PC with the hope that someone on here may be able to enlighten us to where we should focus our attention on to resolve the issue. It seems to fail on Applying Operating system or if we skip this step it seems to fail on Applying Device Drivers. Error: 0x80004005 dism.log smsts.log smsts-20160329-190436.log

We receive a DHCP address, Press F12 to PXE build, It loads the boot image, It starts the process and displays the message "Preparing Network Connections" then sometimes it loads the window with the available Task Sequences, however more often than not it doesn't display the screen and just reboots the machine. If you try the same process a number of times on the same machine it will eventually work as expected. This issue has only recently started this week and We have no idea what may be the cause of it. Any ideas would be greatly appreciated as we have over 300 pc to build in 3 weeks.

I am currently implementing SCCM 2012 and already have SCCM 2007 in place. I have unchecked PXE building in SCCM 2007 and set up PXE building in SCCM 2012 but when I attempt to PXE build on one of our machines it still seems to receive the PXE request from the SCCM 2007 system. If anybody has any ideas why this is happening or where I need to check in 2007 to ensure the function is temporarily disabled then please let me know. 2007 PXE Screen

Thanks for the heads up about the execmgr.log, after viewing this log my colleague has managed to solve the problem and the packages are now installing on the machines. Many Thanks

We are experience issues trying to deploy software packages via task sequences in SCCM 2012. The task sequences deploy to our test collections and report as being 100% compliant but no software is ever deployed. If we choose to deploy the software with wakeup packets the client computer turns on but the process goes no further. We are able to deploy packages to collections outside of task sequences without any issue. This is a brand new SCCM 2012 server which we are in the process of testing, we having a fully working and operational SCCM 2007 environment which we plan on eventually migrating over. During the course of the 2012 install we choose initially to have only 1 distribution point, and then to share the distribution points from the 2007 setup, our plan once finished was to then uninstall the 2007 distribution points and re-setup them up as 2012. The packages are definitely assigned to the distribution points and indeed the task sequences appear and pop up on the client computers within software center. The SMSTS.log on the client computers do not seem to update and neither does the distmgr.log, I can only assume we have missed something in the SCCM 2012 setup, task sequences & software deployments are not a problem in 2007. Is someone please able to put us out of our misery and point us in the right direction, thanks