Failed to run task Sequence Code(0x80040102)

[Trub]

Greetings!

 

Looking for some help with an OSD task sequence.

 

I have a stand-alone site that does everything, no boundaries or boundary groups.

 

I enabled PXE boot and have that working. Created a task sequence to install Windows 8.1, PXE boot the laptop, select the TS and it fails instantly with "The task sequence cannot be run because the program files for WRI0001F cannot be located on the distribution point."

 

Copied off the SMSTS.log file from the client and found this

 

 

I done a lot of searching and found lots of folks having this problem and a lot have been resolved by correcting the boundaries and boundary groups or by making sure the packages are distributed. As I said earlier I don't have boundaries and boundary groups configured and I have made sure the content is distributed via the Content Status

 

 

 

And verifying the SMSPKGD$ share

 

Strange thing if I create another TS say for Windows 10, it will fail but for a different package, like the Config Manager Client or the USMT. Or if I delete the Windows 8.1 TS and create it again, it will fail but for one of the other packages.

 

Any help is greatly appreciated!

[Rocket Man]

I don't have boundaries and boundary groups configured

 

And have you tried Configuring them to check to see if this resolves your content location issues?

BTW.....I would think that the clients will not know which boundary it is a member of likewise the DP for content distribution if you don't specify/configure a boundary(s)

[michaelschindler]

I would at the very least check what the boundaries are (if any). For example if AD Forest discovery is enabled and you have it automatically creating boundaries based on sites and subnets a newly added network segment that is not added to AD as a subnet could create a situation where you have a machine that is not within a boundary.

[Trub]

Thanks for the replies, Mike and Rocketman,

 

We are a small shop and there were no boundaries configured so I checked the two boxes in AD Forest Discovery to allowed it to automatically create the AD and IP boundaries. I then created two Boundary Groups, added the IP ranges and AD sites to each respective group and assigned our single site to each group.

 

Gonna give that some time to simmer this morning and I will report back!

 

Thanks again for the responses!

[Trub]

Solved!

 

So as it turns out our AD sites and services was not setup correctly and the VLAN that the laptop booted up on was not there. I manually added the boundary for that VLAN, add that boundary to the boundary group and the task sequence works as designed.

 

Thanks again for direction!