DerDa Posted October 9, 2013 Report post Posted October 9, 2013 Hi, I am having some issues while setting up several PCs using a PXE OSD task sequence to known Computers (I've added them manually using a file) with Windows 8 including several packages. My problem is that I can set up one or two PCs at the same time without any issues. Last night we tried to set up 15 PCs at the same time, but unfortunately only two of them succeded (the first two which were started - different DPs - so one per DP). The other PCs failed on different steps during the task sequence. As said when running only one PC there is no problem. Some Infos about my Environment: One Primary Site on a SCCM 2012 SP1 with one additional DP in another WAN location. The Servers are running Windows Server 2012. The PCs are all on other subnets and separated from the Server subnet. Packages and Updates are working well. Hope you can help me on this. Thank you Regards Ingo Quote Share this post Link to post Share on other sites More sharing options...
DerDa Posted October 10, 2013 Report post Posted October 10, 2013 I've attached some smsts Log files of three different PCs which have failed. Hopefully someone is able to help me. Thank you! Logs.zip Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted October 10, 2013 Report post Posted October 10, 2013 Failed to run the action: Install Office 2010 32Bit incl. LanguagePacks. Item not found (Error: 87D00215; Source: CCM) so you should check the logfile for that package and/or verify it actually exists on the distribution points Quote Share this post Link to post Share on other sites More sharing options...
DerDa Posted October 10, 2013 Report post Posted October 10, 2013 Thanks for your answer. As said I don't think that the problem are the packages where the TS failed, because the TS succeeded with other PCs. All PCs were started with the same Task Sequence. Furthermore you can see in the smsts.log that the files for Office were downloaded (e.g. 55281-smsts-20131009-125912.log) Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted October 10, 2013 Report post Posted October 10, 2013 it is that step that is leading to the failure, look at this picture, due to the failed app install (previously it reports The sms client service is not running, that's not good....) so you need to find out why that application is failing and what is cuasing the client service to stop, without further logging it's hard to tell, your smsts.log files are not showing all the logs, you need to increase smsts logging capability as described here http://gregramsey.net/2012/12/05/how-to-enable-debug-logging-for-an-os-deployment-task-sequence/ and here http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/12/how-to-change-logging-options-for-smsts-log-in-system-center-configuration-manager-2007.aspx Quote Share this post Link to post Share on other sites More sharing options...
DerDa Posted October 11, 2013 Report post Posted October 11, 2013 Thank you. I have now set up a new Boot Image and TS and will try with the logging settings again. I will post further information. Quote Share this post Link to post Share on other sites More sharing options...
DerDa Posted October 14, 2013 Report post Posted October 14, 2013 Hi, I have testes with 7 new VMs which are in the same subnet as the SCCM server with advanced logging enabled. You can find attached three smsts.log files. For your information: I haven't changed anything except of the Logging settings for the Task Sequence. So these are the same as in my first try. This time nearly all PCs failed at "SAP 730" Installation package which ran fine in the past tries. I've added two logs with SAP issue und one with Lotus Notes issue again. Regards Ingo SCCMLogs.zip Quote Share this post Link to post Share on other sites More sharing options...