This thread might help http://social.technet.microsoft.com/Forums/systemcenter/en-US/a60feb9b-d968-4a2c-9449-773c61bcdf58/os-deployment-unable-to-read-task-sequence-wpeinitexe-does-not-start-automatically?forum=configmgrosd Mike D-
From: [email protected] To: [email protected] Subject: RE: [mssms] Slow network stack can't even start task sequence Date: Thu, 18 Sep 2014 15:10:25 +0000 This is all before the TS gets loaded for the first time, no IP address to contact the MP to get it. DHCP/TCP stack is too slow getting everything up before WinPE asynchronously hands off to the TS engine. To PE everything is fine. Think logon script to install a printer, but the user complains they have to wait on them to show up… William, have you looked into trying to add something to winpeshl.ini or startnet.cmd to slow down winpe to give it enough time to get networking up? startnet.cmd should be calling wpeinit.exe to get the network stack loaded, but you could add some stuff after that to add some time I think. Todd From: [email protected] [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Thursday, September 18, 2014 9:28 AM To: [email protected] Subject: RE: [mssms] Slow network stack can't even start task sequence There are certainly some TS variables that you can add into the boot image to slow down the reboot: http://technet.microsoft.com/en-us/library/hh273375.aspx SMSTSAssignmentsDownloadInterval and Retry sound like places to start > From: [email protected] > To: [email protected] > Subject: [mssms] Slow network stack can't even start task sequence > Date: Thu, 18 Sep 2014 14:00:31 +0000 > > 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 > > >
