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!

PENDING SCCM 2203 - Task Sequence failed because the files cannot be located on a Distribution point

timmyrichy123

Member
Messages
8
Reaction score
0
Points
1
Hello Together,
I'm really getting desperate now.
I'm very new by using SCCM and have some issues to deploy a OS to my Clients.
After I disabled PXE and uninstall WDS on my SCCM Server, I was first able to run a PXE Boot on one of my Clients. I select the Task sequence and become the message: Task Sequence failed because the file <filename> cannot be located on a Distribution point.
First I thought the Configuration Manager Client Package are damaged, but I try to create a other package to test it and have the same issue.
It came the same message with the filename of my boot image.
In other threads someone has written it could be an issue with boundary Groups, but I have no idea how to configure that and this was in SCCM 2012.
I hope someone could help me.

Thanks for you reply.

Bildschirmfoto 2022-05-14 um 14.27.44.png
 
not sure about "disabled pxe and unisnatlled WDS part" you need those to deploy. check distribution point properties to see if pxe is enabled. once you confirm that those exist then we move on. if it cannot find the boot image then you have to distribute it first. check the task sequence log smsts.log on the client machine.
 
I disabled PXE after the SCCM Installation, because the PXE don't work from the beginning, but i think this is not the problem.
Where is the log location ? The Client has no OS installed.
I redistribute the OS Images, Bootimages, und recreate the Tast Sequence.
Then I deploy all, but this didn#t work till now.
 
Thank you for your Help. I"ll try this later.

I"ve forgotten to create Boundaries und Boundary Groups.
I created them yesterday with an IP Range and activate all Discovery Methods.
Two of my Packages are still in Progress. Maybe they stuck there.
The SCCM Server and the DCs are in an Test Environment which in shutting down after my work, perhaps it have to run for a longer time.

I hope I became it to work.
I read in a another Thread that someone has added new Sites in Sites and Service forgotten to add the Subnets. Make it sense to try this ?I hadn´t added subnets manually, just an IP Range in the Boundarys.
SCCM is more complex I thought, but I don't give up !!! Knowledge is invaluable.
 

Forum statistics

Threads
7,160
Messages
27,950
Members
18,243
Latest member
AEUK

Latest posts

Trending content

Back
Top