SCCM | Intune | Windows 365 | Windows 11 Forums

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING OSD misbehaving after 2403 upgrade

WanderingRobot

New Member
Messages
1
Reaction score
0
Points
1
Greetings,
We have one server that's doing just about all our OSD but post upgrade it just restarts the machine after loading the boot wim.
Never makes it into WinPE. We're using SCCM PXE service and I've attached the SMSPXE.LOG however, nothing in the log is sticking out to me and hopefully something is to someone else.

We have some test VM's we're trying OSD on for both pxe and boot media, and this one server just isn't having it.
Another DP in the environment will go to boot media without issue using the newly generated boot image so the issue seems to be with this one DP, it just happens to be the one that images for the company.

We are on the latest ADK 10.0.26100.1 and were using this may release prior to upgrading to 2403.
We are just using EHTTP for communication and a self signed certificate.

DP2024-10-27_09-00-32.pngSITE2024-10-27_09-01-07.png
 

Attachments

Greetings,
We have one server that's doing just about all our OSD but post upgrade it just restarts the machine after loading the boot wim.
Never makes it into WinPE. We're using SCCM PXE service and I've attached the SMSPXE.LOG however, nothing in the log is sticking out to me and hopefully something is to someone else.

We have some test VM's we're trying OSD on for both pxe and boot media, and this one server just isn't having it.
Another DP in the environment will go to boot media without issue using the newly generated boot image so the issue seems to be with this one DP, it just happens to be the one that images for the company.

We are on the latest ADK 10.0.26100.1 and were using this may release prior to upgrading to 2403.
We are just using EHTTP for communication and a self signed certificate.

View attachment 6688View attachment 6689
Are you using a custom winpeshl.ini file by chance? If so I can save you months of digging. I just spent 3 months with osd not working only to discover that our custom winpeshl.ini file was causing osd to do EXACTLY what you are describing. the ONLY was I was able to get things working was to remove the file from sccminstallfolder\OSD\bin\x64. Today (11/7/24) I found this and will be trying it too. as we use the tsbackground process: ) hope that helps.
 

Forum statistics

Threads
6,778
Messages
26,380
Members
16,762
Latest member
TooGreat

Trending content

Back
Top