I think, that the computer will do a network initialization as part of wpeinit –winpe. At least in my wpeinit logs, I can see the drivers loading for the NIC – and that is what wpeutil initializenetwork says it does - so calling initializenetwork after wpeinit –winpe might be redundant (I am not sure if I am right about this.)
As to how I am injecting a script in front of SCCM TS engine, I was mis-remembering without looking at my documentation. After consulting my notes, the key I was referring to is HKLM\System\Setup:CmdLine and I set it to “cscript <path to my join the network script>” I have to wait until the network stack is done loading. The LAN device Ethernet must be available and ready when I make those netsh calls. It feels like in WinPE 10, the client is waiting until the DHCP request completes. In my case it has to time out because we don’t allow non-auth computers on the network at all so they don’t even get a segregated vlan IP address – they get a 169 after timing out. As a test, I hooked the computer up to a port that is non-802.1x protected, and it went past the waitfornetwork spot in 7 seconds --- instead of 99 seconds on a protected port. To me that suggests that in WinPE 10 – the waitfornetwork command is now waiting until the net stack starts up AND the device has finished doing its negotiation with the network (DHCP returns.) When I boot the same computer off a WinPE 5 USB Stick that is configured to run the same script in the same way, it does not pause for 1.5 minutes as the waitfornetwork spot. It seems like I might need to abandon using the waitfornetowork process to wait for the NIC to be active – I was only using it because it was available. I should be able to engineer a way to wait for the network stack through WMI Calls - or simply waiting for a fixed amount of time like 10 seconds or something. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Wednesday, October 05, 2016 8:17 AM To: mdtosd@lists.myitforum.com Subject: RE: [MDT-OSD] WPEInit long delay in WinPE10? So how did this pan out? Trying to nail this down today and also having the same issues with WinPE 10 1511. So it seems that it’s my own API calls that makes this a mess for 1511, all older WinPE’s don’t have this issue. We are calling wpeutil initilizenetwork (from C++) and it does complete fast but then network is not available at some customers. The ConfigMgr media works fine so wonder what they do to make this go fast. Doubt that they call waitfornetwork as we would see the same timeouts there? Todd, how are you starting the process? Don’t get the “explorer shell” thingie”? Which reg key are you replacing? //A From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: den 4 oktober 2016 19:33 To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: RE: [MDT-OSD] WPEInit long delay in WinPE10? Try 1607, 1511 was crap IMHO. Lots of things fixed. I have also heard of this issue, but unsure if that is 1511 or 1607, will check and get back to you. //A From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller, Todd Sent: den 4 oktober 2016 18:14 To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: RE: [MDT-OSD] WPEInit long delay in WinPE10? Thanks Niall. Looking at the logs, I was wrong. It is not wpeinit –winpe that is taking so long. According to the log, it takes 375ms for the components to load and another 1875ms for the nic drivers to load – but that is only ~2.1 seconds total. it is wpeutil waitfornetwork that is responsible for the delay. I may as well post my script so that there is a better understanding… The delay comes where the script is in wpeutil waitforbnetwork… But WinPE 5 didn’t sit there for a long time. WinPE 10 does. I need to wait for the network device to become available or the rest of the script doesn’t work. There needs to be an “ETHERNET” device established in the OS for those netsh commands to work. So maybe wpeutil is waiting differently in WinPE 10 than it did in WinPE 5. It waits on that line for so long you begin to think may be something not working. WinPE 5 on the other hand breezes past this in 10-15 seconds - not 100 seconds as in WinPE10. I wonder if waitfornetwork waits until an IP address is assigned to the interface in WinPE 10 or something…. I could see it taking that long for the DHCP requests to time out – but that is not the experience in Win PE 5. The purpose of this script is to allow WinPE booted devices to get connected/authenticated to our 802.1x protected network in order to begin OS deployment. The script is called by explorer shell (via registry edit) and once the network is connected, the usual wpeshl continues with the Configmgr/OSD stuff. Script snippit WshShell.Run("x:\windows\system32\wpeinit -winpe"),1,true LogText "wait for network stack to start up" WshShell.Run("x:\windows\system32\wpeutil WaitForNetwork"),1,true 'Initialize 8021x strcommand= "net start dot3svc" LogText "starting 8021x service with " & strcommand wshshell.Run strcommand,5,true strcommand= "certutil.exe -addstore root " & ScriptPath & "domain.cer" LogText "Importing domain cert using " & strcommand wshshell.Run strcommand,5,true strcommand= "netsh lan add profile filename=" & ScriptPath & "Ethernet.xml interface=" & chr(34) & "Ethernet" & chr(34) LogText "Configuring Ethernet interface using " & strCommand wshshell.Run strcommand,5,true strcommand= "netsh lan set eapuserdata filename=" & ScriptPath & "Wired-WinPE-UserData-PEAP-MSChapv2.xml allusers=yes interface=" & chr(34) & "Ethernet" & chr(34) LogText "Supplyinf PEAP user credential using " & strCommand wshshell.Run strcommand,5,true {{{…. Run a loop to wait for an ip address… }}} objShell.Run("x:\windows\system32\winpeshl.exe"),1,true From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Niall Brady Sent: Tuesday, October 04, 2016 2:19 PM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: Re: [MDT-OSD] WPEInit long delay in WinPE10? what does the WPEinit.log file tell you ? are you having network issues ? On Tue, Oct 4, 2016 at 9:02 PM, Miller, Todd <todd-mil...@uiowa.edu<mailto:todd-mil...@uiowa.edu>> wrote: Since updating my boot disks to WinPE 10, I am finding that the initial call to WPEInit –winpe is taking a very long time. What used to take 20-30 seconds is now taking 2 – 3 minutes. I don’t know too much about the changes between WinPE 5 (8.1) and WinPE 10 (CB1511) I also haven’t tried to move to 1607 yet. I am using 1511 + the hotfix. Are there any tricks people know of to make wpeinit –winpe go faster? Has anyone else seen a massive slowdown here after moving to WinPE 10? I am initializing WinPE on my own prior to TS because we have 802.1x network and I have to initialize and authenticate to the network in WinPE before the task engine starts. ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________
