That is all WinPE that initializes the network stack, it has little to do with SCCM.
What version of WinPE? X86 or x64? Can you try a different boot image? Does it do it with PXE and CD-Rom/USB? Daniel Ratliff -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Craig Sent: Thursday, September 18, 2014 10:15 AM To: [email protected] Subject: [mssms] RE: Slow network stack can't even start task sequence I originially thought of these but not sure now, does it receive a TS advertisement? SMSTSAssignmentsDownloadInterval Use this variable to specify the number of seconds to wait before the client will attempt to download the task sequence policy since the last attempt (which returned no policies). You can set this variable by using a prestart command from media or PXE. SMSTSAssignmentsDownloadRetry Use this variable to specify the number of times a client will attempt to download the task sequence policy after no policies are found on the first attempt. You can set this variable by using a prestart command from media or PXE. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of William Jackson Sent: 18 September 2014 16:01 To: [email protected] Subject: [mssms] Slow network stack can't even start task sequence Thanks to this list I have been reading about the interaction between fast SSDs and slow network stack initialization, SMSTSMPListRequestTimeout, &c. But I have a problem where the computer I am trying to deploy to will automatically reboot before starting a task sequence. Looking at smsts.log, I see that it can't find a management point and gives up. If I open a command prompt to interrupt the automatic reboot, I can see that the computer has no IP address when the task sequence gives up, but obtains an IP address a few seconds later. Is there a way to make the task sequence engine/bootstrapper/whatever wait a little longer to give the computer time to obtain an IP address before giving up? Would I have to use a pre-execution hook for that? Thanks, William The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
