PENDING OSD failing following update to 1903 ADK

[W4050]

I've recently upgraded the ADK on our SCCM server from 1809 to 1903 and am now seeing OSD failing.

Windows PE boots and shows the shell during initialisation (Starting Windows PE...), then the machine reboots. I'm not even getting far enough to enter the password or selecting a task sequence to run.

Checking the logs on the OSD client shows the following lines:
Starting DNS client service.]LOG]!><time="13:29:32.477+480" date="06-03-2019" component="TSBootShell" context="" type="1" thread="940" file="bootshell.cpp:818"
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="13:29:32.477+480" date="06-03-2019" component="TSBootShell" context="" type="1" thread="940" file="bootshell.cpp:1012"
The command completed successfully.]LOG]!><time="13:29:32.477+480" date="06-03-2019" component="TSBootShell" context="" type="1" thread="940" file="bootshell.cpp:1094"
Execution complete.]LOG]!><time="13:29:32.492+480" date="06-03-2019" component="TSBootShell" context="" type="1" thread="940" file="bootshell.cpp:845"
hMap != 0, HRESULT=80070002 (..\environmentscope.cpp,493)]LOG]!><time="13:29:32.492+480" date="06-03-2019" component="TSBootShell" context="" type="0" thread="940" file="environmentscope.cpp:493"
m_pGlobalScope->open(), HRESULT=80070002 (..\environmentlib.cpp,335)]LOG]!><time="13:29:32.492+480" date="06-03-2019" component="TSBootShell" context="" type="0" thread="940" file="environmentlib.cpp:335"
this->open(), HRESULT=80070002 (..\environmentlib.cpp,561)]LOG]!><time="13:29:32.492+480" date="06-03-2019" component="TSBootShell" context="" type="0" thread="940" file="environmentlib.cpp:561"
::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (..\utils.cpp,1015)]LOG]!><time="13:29:32.492+480" date="06-03-2019" component="TSBootShell" context="" type="0" thread="940" file="utils.cpp:1015"
RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence]LOG]!><time="13:29:32.492+480" date="06-03-2019" component="TSBootShell" context="" type="2" thread="940" file="utils.cpp:1015"
GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="13:29:32.492+480" date="06-03-2019" component="TSBootShell" context="" type="2" thread="940" file="utils.cpp:1048"
End program: ]LOG]!><time="13:29:32.492+480" date="06-03-2019" component="TSBootShell" context="" type="1" thread="940" file="bootshell.cpp:877"

I can ping the FQDN of the SCCM server successfully from the OSD client, have ensured that there's a network access account present and have tried ticking the 'allow clients to connect anonymously' checkbox from the DP properties window.

I've now reverted the ADK on the SCCM server to 1809 and redistributed the boot images regenerating from the 1809 versions now installed, but still see the same issue. The same entries appear in the SMSTS.log on the client I'm attempting to image and the whole OSD process behaves in the same way. The issue therefore feels like it's something more fundamental than just an ADK version change. I've also tested using the old USB OSD media (1809) and that attempts to pre-stage the boot media and then fails with a generic error (0x80004005) - pre-staging the boot media for OSD is normal if the version is not the same as that on the USB memory stick, but those versions should now match, so I assume that something in SCCM has been configured

Can anyone help with where to start troubleshooting this please?

 

[jp67]

W4050, I was having the same issue as you described. Were you able to fix this or work around it? I was able to resolve this by removing all of the 3rd party drivers from my Boot Image and then update the distribution point. In the UDP Wizard, I checked the box to "Reload this boot image with the current Windows PE version from the Windows ADK". This brought in a fresh boot.wim without any 3rd party drivers injected into it.

 

[Edy]

everytime you updated ADK, you need to update the distribution point with the new boot image.

 

[jp67]

everytime you updated ADK, you need to update the distribution point with the new boot image.

Edy, in my case this was done multiple times while troubleshooting the issue. It wasn't until I removed all the drivers and then refreshed from the ADK again that it started working.