---
title: "Sean Hanson (@seanrhanson) | Hashnode"
description: "IT Manager. Read the latest articles by Sean Hanson on Hashnode."
url: "https://hashnode.com/@seanrhanson"
---

@seanrhanson

# Sean Hanson

@seanrhanson · Joined August 2021

IT Manager

## Comments

[Ondrej Sebela 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.](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/610e173a528eff11aea8911f#reply-611d682aa285e422d5a133da)

Reply · Article · Aug 18, 2021 · [Adding support for OS deployment through Wi-Fi to SCCM](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a)

[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](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/610e173a528eff11aea8911f#reply-610eb4b3528eff11aea89f6f)

Reply · Article · Aug 7, 2021 · [Adding support for OS deployment through Wi-Fi to SCCM](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a)

[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.](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a/comment/610e173a528eff11aea8911f)

Comment · Article · Aug 7, 2021 · [Adding support for OS deployment through Wi-Fi to SCCM](https://hashnode.com/posts/adding-support-for-os-deployment-through-wi-fi-to-sccm/60c711884e04b16f76731b2a)