This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 54%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBJ%3C/text%3E%3C/svg%3E)
I have a new SCCM 2409 environment and I am trying to get OSD working on it.
I have a distribution point servicing a particular subnet that OSD will take place on. I have WDS setup on it. The DP has PXE support for clients enabled. "Allow this DP to respond to incoming PXE requests" is checked as is "Enable unknown computer support". "Respond to PXE requests on all network interfaces" is selected.
I have selected a test model and injected the NIC driver for it into the boot.wim. I have distributed the boot.wim to the DP and have it enabled in WDS. "Deploy this boot image from the PXE-enabled distribution point" is checked on the WIM properties.
Devices boot into WinPE but I just get the background and the wizard never starts.
The smsts.log does not show that the TS variables get downloaded as described on this page:
https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/os-deployment/understand-pxe-boot
I should see a path to a boot.var file like this:
Variable Path: \SMSTemp\2014.09.05.18.20.31.0001.{0C616323-A027-41B0-A215-057AF4F1E361}.boot.var
But a line like this does not appear in the smsts.log.
Also, I do not see a boot.var file at \SMSTemp on the DP which hosts WDS. There is only a boot.bcd file.
The example log at the site above shows:
TsPxe.dll loaded
Device has PXE booted
Variable Path: \SMSTemp\2014.09.05.18.20.31.0001.{0C616323-A027-41B0-A215-057AF4F1E361}.boot.var
Succesfully added firewall rule for Tftp
Executing: X:\sms\bin\i386\smstftp.exe -i 10.238.0.2 get \SMSTemp\2014.09.05.18.20.31.0001.{0C616323-A027-41B0-A215-057AF4F1E361}.boot.var X:\sms\data\variables.dat
Executing command line: "X:\sms\bin\i386\smstftp.exe" -i 10.238.0.2 get \SMSTemp\2014.09.05.18.20.31.0001.{0C616323-A027-41B0-A215-057AF4F1E361}.boot.var X:\sms\data\variables.dat
What I get is:
TsPxe.dll loaded
Device has PXE booted
Succesfully added firewall rule for Tftp
Executing: X:\sms\bin\x64\smstftp.exe get <DP IP address> X:\sms\data\variables.dat
Command line for extension .exe is "%1" %*
Set command line: "X:\sms\bin\x64\smstftp.exe" get <DP IP address> X:\sms\data\variables.dat
Executing command line: "X:\sms\bin\x64\smstftp.exe" get <DP IP address> X:\sms\data\variables.dat with options (0, 0)
Process completed with exit code 22
I will add that the device has a good IP address and I can ping the DP from the device successfully.
Why would the boot.var be missing? I find it odd that there is no attempt logged to even look for it.
Are the client, wds, dhcp on the same subnet? You may need to configure iphelpers if not already done. Error 22 does suggest issues with the configuration. I will also suggest to drop wds and configure pxe responder instead.
Thanks for the reply.
No, the clients are on a different subnet than the WDS and DHCP servers. I shall check to see if IP Helpers are configured.
Check, is your Unknown x64 and x86 have Task Sequence Deployment active to them? Click properties on accounts and look Deployment page, do you see TS active there?
Another root cause - look MAC adress of the device from SCCM and make sure it has no computer name already existing. If so, delete it.
Thanks for the reply.
Yes, the task sequence has been deployed to All Unknown Devices. The deployment is listed on the Deployment tab of All Unknown Devices, Unknown x64, and Unknown x86.
I shall check on the MAC address.
Thanks again.