Corrected command:
Powershell.exe -executionpolicy bypass -windowsstyle hidden -command "&
{start-sleep -seconds 10}"
One note, you will actually have to add PowerShell to your boot image.
Daniel Ratliff
From: [email protected] [mailto:[email protected]] On
Behalf Of Daniel Ratliff
Sent: Thursday, September 18, 2014 12:37 PM
To: [email protected]
Subject: RE: [mssms] Slow network stack can't even start task sequence
That's interesting, I would also add you can easily accomplish this with
PowerShell, so no additional content is needed on your boot image.
Powershell.exe -executionpolicy bypass -windowsstyle hidden -command "&
{start-sleep -seconds 10}
You may need the full path to PowerShell too.
x:\windows\system32\windowspowershell\v1.0\powershell.exe
Daniel Ratliff
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
On Behalf Of Mike Dzikowski
Sent: Thursday, September 18, 2014 12:04 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Slow network stack can't even start task sequence
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]<mailto:[email protected]>
To: [email protected]<mailto:[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]>
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
On Behalf Of Jason Wallace
Sent: Thursday, September 18, 2014 9:28 AM
To: [email protected]<mailto:[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]<mailto:[email protected]>
> To: [email protected]<mailto:[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
>
>
>
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.
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.
