Ghost Solution Suite

iPXE supports wireless (SSID/PSK) as long as the drivers are included.

I know that Symantec does not officially support wireless for iPXE, but has anyone been able to sucessfully modify the PE for thier iPXE boot to include wireless settings for thier network(s)?

Wireless pxe?   Would have to see that to believe it, got any links to read about it?  The wireless NIC would have to have a boot rom and then in the bios/firmware be able to select said wireless interface for booting from.     I know none of the hardware I have ever had pass across my desk has had this option in the bios/firmware to support the wireless nic for booting.  Ethernet, even USB Ethernet, check but wireless not so much. 

Wireless windows PE is another thing but not pxe delivered.   If you boot from automation folers, dvd, usb, usb ethernet or some other creative way you could hack windows pe to make wireless work once booted to windows pe  but it wouldn't be recieving the boot files via PXE.  

The biggest stuggle with wireless windows pe (not pxe) is adding the needed components to windows pe and then scripting it to join the wireless network.  Things like what wireless name and then what form of authentication is used then to join that network.     There is lots of reading out there on how to modify pe for supporting wireless support.  Some seam reasonable some are more involved.    Because wireless winpe support isn't native there won't likely be any thing in here but it is a Win pe thing and once you had it going on say a usb boot disk that you built manually it should be able to be added to a symantec delivered windows pe package. 

This guy has a bunch of good stuff for win pe and wireless but it would have to be delivered some way other than wireless PXE. 

https://www.scconfigmgr.com/2018/03/06/build-a-winpe-with-wireless-support/

Even in the Microsoft forums they are saying it isn't an option.   For client systems that dont come with a wired NIC the manufacturer has to offer a wired USB nic that supports PXE booting.   Not every USB NIC supports PXE and a HP USB NIC won't nesasarily work on a Surface PRO.  You have to use the manufacture's recomended USB ethernet adapter to get pxe booting. 

Some discusson on the same but all pointing to the need to use some meathod to deliver the boot package and then work over wireless once the boot package is delivered. https://social.technet.microsoft.com/Forums/en-US/9d8e05ab-2bfa-4547-b2b4-81d855ef31ed/is-a-pxe-boot-over-wifi-amp-a-successful-osd-possible?forum=ConfigMgrCBOSD

If you find some thing let us know I am always game to try some thing new just to see if it can be done. 

I appreciate the response, but iPXE and PXE are not the same thing.

iPXE requires a local boot image (CD/DVD/USB/ISO), in my case a windows 10 PE which I created using GSS Boot Disk Creator.

What I'm trying to do is slip the WLAN configuration into the PE and force it to connect.

I've added a WLAN XML Profile and a bat file that applies the profile configuration and connects to the WLAN, but I'm not entirely certain I have them in the correct location in the configuration file for Boot Disk Creator.

I don't think we are on the same page.   IPXE as implemented in GSS 3.3 doesn't require boot media  is still PXE and delivers the boot files via  HTTP rather than TFTP.   The efficiency increase in IPXE is huge.   In my lab standard PXE takes about 5 minutes to deliver the boot files.    IPXE delivers the same files in under 40 seconds but in both cases it is delivered via the ethernet adapter that has the pxe boot rom on it.    

This is a better write up than available for GSS but same tech was added to both. 

https://support.symantec.com/en_US/article.TECH250831.html

I do understand that if fully implemented the ethernet NIC's boot rom could be replaced to then load an ipxe package that then could support wireless that would then talk to the PXE server via the wileless nic and then could recive the automation (winpe) boot package but we don't have that going and if a person did do that, windows pe still wouldn't have the NIC support to talk to the wireless network.   I guess it could be that as implemented in GSS and DS ipxe is being delivered and then chain loaded via the legacy pxe front end.   

Any way back to how to get wireless support in windows PE since you already have worked out how to deliver the winpe and are using boot disks.   The blog post on the first post has the most compleate info I have found.   But it has been a long time since I last tested it out.    I started with some third party pe boot disk builders to prove to my self that the hardware pe/re could even support wireless.    Then I followed simular steps as in that blog but it was long enough I don't recall the exact steps.    Performance will be a potential issue in the end if you do get it working.   

If in doubt about file locations you can try to then manualy call each piece from the command prompt and adjust as needed then once you are up and running and can proof of concept you can naviagate a way to get the files in the right spot on the boot disk  or script to call them in odd locations. 

Hope that is helpful and I look forward to hear about your progress.   I don't think it will be a feature added nativly to win pe any time soon but it is exciting to push the boundries.

I've got it working perfectly now, so I'll outline what I had to do incase anyone else wants to do the same:

1) Had to modify the WinRE.wim file and rename it as winpe.wim using the steps outlined here: https://www.scconfigmgr.com/2018/03/06/build-a-winpe-with-wireless-support/

2) Use the wim file to create my boot disk using "Boot Disk Creator"

3) Add my wireless device drivers in boot disk creator

4) Add my Wireeles Profile XML file to the configuration root.

5) Add a text file in "prestart" folder and paste the following: (change "WirelessProfile.xml" and "WirelessProfileName")

net start netman
net start wlansvc
wpeutil initializenetwork
netsh wlan add profile filename="%SYSTEMDRIVE%\WirelessProfile.xml"
netsh wlan connect name=WirelessProfileName ssid=WirelessProfileName
ping localhost -n 30 >nul

6) rename the text file to wireless.cmd

7) Build my boot image using the wizard with the following options:

Boot type: Files (copy boot files to folder)

Boot task type: Automation Boot

ICHCB, I appreciate your input and hope that information helps others as well.

That is great I am glad you got it going.   Curious what all you are doing wirelessly (imageing?)  and then what the perfomance is like compared to the wired equivelent.    

Thanks for looping back and putting what you found as working for others.