Have a look at checkfornetwork and storage on windows noob, it runs before sny prestarts via a reg hack
Sent from my phone, please excuse any typo's as a result. > On 02 Dec 2015, at 18:21, Miller, Todd <[email protected]> wrote: > > I am interested in running a pre-TaskSequence routine every time my clients > boot into WinPE during a task sequence. What is the best way to accomplish > this? I’m not talking about a pre-execution hook which only runs on first > WinPE boot. > > I have added a command to unattend.xml on the WinPE image and it works great > for the first boot onto the WinPE OS, but when the TS engine stages the Boot > Image onto the disk for subsequent PE reboots, it overrides that function > with its own WinPEUnattend.xml > > Is there a way for me to insert anything in front of the Task Sequence engine > to run before the Task sequence takes over? > > I want to use this to attach to our 802.1x network, but it could be used to > re-establish DART or any of number of things. > > Of course I can insert items in the task sequence after every “Reboot” item > to re-establish the network, but it would be much better if I could just make > that happen at every reboot. Putting those in the TS itself sub-optimal > since there is a long delay at each TS startup if the network is not > available. Is there any way to insert my own code into the WinPE start for > all the staged PE reboots? > > I have started re-look at OSDInjection.xml as I used that previously to write > a custom smsts.ini file to my WinPE boot images. It doesn’t appear that > winpeshl.ini is listed in OSDInjection.xml so some other process is creating > that file? I think my best hope is to use this process to inject the > necessary 802.1x files into the WINPE image using the standard means for > extra files and then use osdinjection.xml to figure out how to modify the > WinPE startup process. Just not sure which ini file I need to inject/modify > that can survive both the WinPE build process and the TS WinPE staging > process. I think the console even overwrites the WinPESHL.ini file if I use > OSDInjection.xml to write a custom one. Ugh! > > > I really could use a way to inject a network startup process into the WinPE > boot process - not only to establish 802.1x connections but I think others > could use it to establish VPN early in the WinPE boot process as well. > > > > (Please --- I’m not interested in bypassing 802.1x in other obvious ways > like having build benches with 802.1x disabled ports or using MAC whitelisted > devices to bypass 802.1x auth… I know about those options and am using them > already. We want to get away from whitelisted USB Ethernet adapters for > deskside re-deploys) > > > Notice: This UI Health Care e-mail (including attachments) is covered by the > Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential > and may be legally privileged. If you are not the intended recipient, you > are hereby notified that any retention, dissemination, distribution, or > copying of this communication is strictly prohibited. Please reply to the > sender that you have received the message in error, then delete it. Thank > you.
