Forums on Intune, SCCM, and Windows 11

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!

NEW Microsoft Endpoint Config Manager Distributiuon Point wont run OSD Task Sequence

cflaggrun

Member
Messages
8
Reaction score
0
Points
1
We are currently running Microsoft Endpoint Configuration Manager 2207 which works great at our main location. We've recently added a new site and have tried setting up a distrubution point to pxe boot computers and deploy images at this remote location. When trying to pxe boot at the remote site I get to the osd task sequence wizard splash screen but when attempting to run it, it fails immediately with this error... "This task sequence cannot be run because the program files for XXX00003 cannot be located on a distribution point. For more infor contact...."

Looking in the DP Config status it shows that xxx00003 was successfully distributed, all green. Ive tried redistributing it, ive even removed the DP and reinstalled. Any insite to what might be going on is greatly appreicated.
 
We are currently running Microsoft Endpoint Configuration Manager 2207 which works great at our main location. We've recently added a new site and have tried setting up a distrubution point to pxe boot computers and deploy images at this remote location. When trying to pxe boot at the remote site I get to the osd task sequence wizard splash screen but when attempting to run it, it fails immediately with this error... "This task sequence cannot be run because the program files for XXX00003 cannot be located on a distribution point. For more infor contact...."

Looking in the DP Config status it shows that xxx00003 was successfully distributed, all green. Ive tried redistributing it, ive even removed the DP and reinstalled. Any insite to what might be going on is greatly appreicated.
what is the program thats failing ? is it an application or package ? i had a similar issue after replacing an MSI file but forgot to update the GUIDs in the application deployments
 

Forum statistics

Threads
7,135
Messages
27,868
Members
18,159
Latest member
jordysmits
Back
Top