richard.davignon Posted June 29, 2015 Report post Posted June 29, 2015 Hello, I have been experiencing a problem with WinPe booting up. When it hits the "establishing network connections" it reboots. I looked through the log file and do see that it sees my network adapter. This recently just started and happens on three different model computers. Any help would be appreciated. I have attached the SMSTS.log below. smsts062915.log Quote Share this post Link to post Share on other sites More sharing options...
Garrett804 Posted June 29, 2015 Report post Posted June 29, 2015 usually the reboot is due to a driver issue, the drivers you need for the WinPE environment are the sata controller and network. Turn on the Cmd prompt options and when you see it loading up in WinPE press F8 to pop up the command prompt. This will keep it from rebooting and allow you to see if it pulls an IP etc... 1 Quote Share this post Link to post Share on other sites More sharing options...
richard.davignon Posted June 29, 2015 Report post Posted June 29, 2015 I have done this already. I do get an IP address. Not sure what to do next. Quote Share this post Link to post Share on other sites More sharing options...
richard.davignon Posted June 29, 2015 Report post Posted June 29, 2015 Also, If I delete the computer from System Center and image it as a new unknown machine it works fine. Quote Share this post Link to post Share on other sites More sharing options...
mbourboin Posted June 29, 2015 Report post Posted June 29, 2015 ya, focus on NIC and Storage drivers in the boot image ! that would be my pick I'm facing the same problem with a new laptop HP 840 Quote Share this post Link to post Share on other sites More sharing options...
Jaybone Posted June 29, 2015 Report post Posted June 29, 2015 There are no task sequences available to this computer.. Please ensure you have at least one task sequence advertised to this computer. That's probably it. If you've got systems that aren't marked as approved, this'll happen. This can happen if, say, you're not joining them to the domain as part of the task sequence, or manually after imaging. I might be off here, but I want to say that the default settings are to auto-approve domain-joined machines, but not any others. Solution for that particular situation is to either Join them to domain in TS. Join them to domain manually. Right-click the system in the console and Approve. Delete from Config Manager so they show up as new. I usually just delete them - even when manually approving, it can take a few minutes before that pushes all the way through and allows you to deploy. Quote Share this post Link to post Share on other sites More sharing options...
Garrett804 Posted June 30, 2015 Report post Posted June 30, 2015 Ok if its a task sequence not available issue then its either an approval issue as was stated above or its a deployment issue with the task sequence not being deployed to a collection this machine is a member of. 1 Quote Share this post Link to post Share on other sites More sharing options...
