I read a few blogs regarding this issue. Especially this one explains the problem very well and gives 3 good solutions:
The sample script described in this article might work, but in most of the environments I worked, you need computer policies (and/or user policies) applied to be able to connect to WIFI. This isn’t applied during OSD, which makes it very difficult to connect to WIFI during OSD.
Another solution I read about, is importing your device by UUID. I tried it, but when OSD finished on the device, SCCM will still register the mac address of the external ethernet adapter in the database.(and I’m not constantly sitting next to my device, waiting for an OSD to end, to remove the ethernet adapter quickly.) When importing a new machine by UUID, I couldn’t deploy with the same external ethernet adapter, because the mac address was already known. Makes sense, doesn’t it? 🙂
I found another simple solution that helped me and I wanted to share with you:
– Create a machine in sccm using the mac address of your external ethernet adapter.
– Start your OSD and let it finish (successfully).
– Log on to the machine (fe: with an admin ID) and try to connect to WIFI. When connected to WIFI, remove the external ethernet adapter.
– After 10 – 15 minutes, check the properties of the device in SCCM again. the MAC address should have changed to the MAC address of the WIFI network card.
Now, you can use the external ethernet adapter on a new device for OSD deployment. When using a required deployment, it might happen that PXE boot fails on the first time. If so, try to clear any required PXE deployment from the new machine and PXE boot it again.