Thursday, June 4, 2026

1702 OSD Fails, There are no task sequences available for this computer

Issue reported: 1702 OSD Fails none of the build is getting pxe boot. Error: There are no task sequences available for this computer

Work-around :

Point 1: Run this query in SQL Mgmt. Studio to confirm that you have a duplicate;

select * from UnknownSystem_DISC inner join System_DISC on UnknownSystem_DISC.SMS_Unique_Identifier0 = System_DISC.SMS_Unique_Identifier0

Point 2: Run query to check for current unknown devices and copy their itemkey and GUID; select*from UnknownSystem_DISC

Point 3: Change registry value from 1 to 0 on site server to trigger unknown devices to be recreated. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS \COMPONENTS\SMS_DISCOVERY_DATA_MANAGER CreatedUnknownDDR=dword:00000001

Point 4: Monitor the DDM.log on your site server to see if SMS_DISCOVERY_DATA_MANAGER has picked up the changes and created the new unknown devices. Look for Created x86 Unknown Computer DDR Created x64 Unknown Computer DDR

Point 5: If it has no created new unknown objects after 10 minutes; Restart the server or the SMS_DISCOVERY_DATA_MANAGER service on the site to force it to detect the changed reg value. See previous step before proceeding

Point 6: Re-run the SQL command to see the new and old unknown devices; select * from UnknownSystem_DISC

Point 7: Delete both the old unknown devices using their itemkey that was noted down in the first step; delete from UnknownSystem_DISC where ItemKey = xxxxxxxxxx

Point 8: Update the unknown computers collection in SCCM

Point 9: You can either recreate PXE on your DP now (remove and add again) or do the next steps Grab the new itemkey and GUIDs from SQL Mgmt Studio; select * from UnknownSystem_DISC

Point 10: Update these values on Distribution Point with the corresponding itemkeys and GUIDsHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP UnknownX86GUID=xxxxxxxx-xxx-xxx-xxx-xxxxxxxxxxxx UnknownX64GUID=xxxxxxxx-xxx-xxx-xxx-xxxxxxxxxxxx UnknownX86ItemKey=dword:00000000 UnknownX64ItemKey=dword:00000000

Point 11: Restart WDS Server on Distribution Point

Point 12: Verify

Note: If you have more than one DP, do the last two steps on all of them.

For more reference Click Here

Happy learning!!!

Haresh Hirani
Email: [email protected], [email protected]
Facebook https://www.facebook.com/Hiraniconfigmgr-120189361980772/
Follow us: https://www.linkedin.com/in/hiraniconfigmgr 
Twitter: https://twitter.com/hiraniconfigmgr

Author

  • Hi, I’m Haresh Hirani the mind behind Hiraniconfigmgr.com. I’m a seasoned IT professional with deep expertise in Microsoft technologies, especially in Configuration Manager (ConfigMgr/SCCM). Over the years, I’ve expanded my skill set to cover a broader range of modern device management platforms like Microsoft Intune, Jamf Pro, ManageEngine Endpoint Central, and VMware AirWatch (Workspace ONE UEM), I use this blog to document real-world, tested, working fixes and walkthroughs from my daily technical experiences. The 💡idea is simple: if it helped me, it might help someone like you. My goal is to create a living repository of practical IT solutions for the community. If you find something useful, or if you want to collaborate, feel free to connect with me on LinkedIn or drop a message through the Contact page. Happy to help.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest posts