--- title: "Discussion on \"Adding support for OS deployment through Wi-Fi to SCCM\" | Hashnode" description: "Discussion on \"Adding support for OS deployment through Wi-Fi to SCCM\". So you can reimage your devices on any Wi-Fi network" url: "https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a" --- [Feed](https://hashnode.com/feed) / Discussion # [Adding support for OS deployment through Wi-Fi to SCCM](https://doitpshway.com/adding-support-for-os-deployment-through-wi-fi-to-sccm?utm_source=hashnode&utm_medium=feed) So you can reimage your devices on any Wi-Fi network Jun 14, 2021 · 15 min read · doitpshway.com Updated Aug 11, 2021 Read the article - [#powershell](https://hashnode.com/tag/powershell) - [#os](https://hashnode.com/tag/os) - [#script](https://hashnode.com/tag/script) - [#cloud](https://hashnode.com/tag/cloud) - [#windows](https://hashnode.com/tag/windows) ## Written by [Ondrej Sebela](https://hashnode.com/@AndrewZtrhgf) @AndrewZtrhgf · Czech Republic [View profile](https://hashnode.com/@AndrewZtrhgf) System Administrator that loves PowerShell I work as System Administrator for more than 15 years now and I love to make my life easier by automating work & personal stuff via PowerShell (even silly things like food recipes list generation). ## Responses 2 Markdown supported · ⌘↵ to post [Mark](https://hashnode.com/@mark846) [Apr 26, 2022](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/626832977b6a339ac2d0224b) Hello Ondrej, thanks for this useful article. I´m stuck with the USB script in line 388. **Set-Content -Path $WinREWiFi -Value (Get-Content $WinREWiFi...** The script quits with the error message, that -Path is NULL. I checked the USB script and in line 384 there is a script named WinREWiFi.ps1: **$WinREWiFi = Get-Item "$wimMountPath\\Program Files\\WindowsPowerShell\\Modules\\OSD\*\\Public\\WinREWiFi.ps1** I mounted the modified boot.wim, which is on the USB stick and there is no such script in the specified path. Do I have to change something in the USB script? Is there any change in OSDCloud so that there is no WinREWiFi.ps1 script anymore? Thanks in advance and best regards, Mark [Ondrej Sebela](https://hashnode.com/@AndrewZtrhgf) [Apr 28, 2022](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/626832977b6a339ac2d0224b#reply-626a2d15aedfbdb0ce1a7018) You are correct. This part of OSDCloud was modified. I've fixed the [github.com/ztrhgf/OSD\_WITH\_WIFI/blob/main/customi…](https://github.com/ztrhgf/OSD_WITH_WIFI/blob/main/customize_sccm_usb_boot_image_to_support_wifi.ps1) script, so please try it again. [Mark](https://hashnode.com/@mark846) [May 4, 2022](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/626832977b6a339ac2d0224b#reply-62726ee6272fe72a917ccbed) [Ondrej Sebela](https://hashnode.com/@AndrewZtrhgf) Hello Ondrej, thanks for fixing the USB script, it works. I have another issue. I followed the article, but when I try to boot from USB, the task Test-WebConnection google.com fails. Also the task Testing Wi-Fi Network Adapter fails. A window opens and I can see the WiFi adapter in the network settings. I guess this is no driver issue. I injected the latest Windows 10 and WinPE drivers from DELL. "Transcript started, output file is X:\\windows\\TEMP\\wreconnect.log No Wi-Fi profile was found, making initial connection. (I deleted the WiFi profile for testing. Even with the profile, the sequence fails.) Start-WinREWiFi OK Test-WebConnection google.com FAIL Testing required WinRE content OK Starting WlanSvc Service OK Testing Wi-Fi Network Adapter FAIL Warning: Could not find an installed Wi-Fi Network Adapter Warning: Drivers may need to be added to WinPE" Any ideas what could cause this? I have the same WiFi adapter as described in your article. Thanks and regards, Mark [Sean Hanson](https://hashnode.com/@seanrhanson) [Aug 7, 2021](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/610e173a528eff11aea8911f) I've been working on implementing this, but I believe I'm missing something. I've successfully created the boot drive, connected to wifi, and selected a task sequence. The task sequence needs to be attached to the default boot image, else there would be multiple boot images available through PXE and regular wired imaging stops working. Due to that, wifi clients end up downloading the default Endpoint Manager boot image and restart to that image before applying an OS, which fails because at that point it is not connected to wifi. [Sean Hanson](https://hashnode.com/@seanrhanson) [Aug 7, 2021](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/610e173a528eff11aea8911f#reply-610eb4b3528eff11aea89f6f) I guess the issue is, when deploying a task sequence, it doesn't seem there's a way to make a deployment only be available to bootable media. It always includes PXE, and multiple boot images in a PXE environment doesn't work. If all imaging is done via bootable media, then the different boot images wouldn't be a problem [Ondrej Sebela](https://hashnode.com/@AndrewZtrhgf) [Aug 18, 2021](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/610e173a528eff11aea8911f#reply-611d63c7a285e422d5a1339e) Sorry I don't think I follow.. [Sean Hanson](https://hashnode.com/@seanrhanson) [Sean Hanson](https://hashnode.com/@seanrhanson) [Aug 18, 2021](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/610e173a528eff11aea8911f#reply-611d682aa285e422d5a133da) [Ondrej Sebela](https://hashnode.com/@AndrewZtrhgf) I've sorted this out, but it took awhile to understand all the components at play and figure out a way around the PXE issue. - If both wired and wireless systems were imaged using bootable media, then the correct boot image for each type would be on the media itself. Having different boot images for each wouldn't cause any issue. - With PXE, the most recent task sequence deployment dictates which boot image is pushed on a PXE boot. My understanding is that best practices say you should keep that as the default "Boot Image (x64)". If the last task sequence deployed to unknown devices is the OSDCloud boot image, that overrides the default boot image and was causing some problems with the wired systems. Ultimately, the fix was to make sure and recreate a deployment for a normal task sequence (that uses the default boot image) after doing any work on the wifi task sequences. That allows PXE to use the default image while still allowing the wifi task sequences to use the OSDCloud image.