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!

SOLVED Failed to resolve selected task sequence dependencies Code(0x80040102)

Status
Not open for further replies.

Trub

New Member
Messages
3
Reaction score
0
Points
1
Greetings,

First off, I would like to say thank you to this web site, it has helped me considerably in configuring System Center, I am very grateful.

My environment - Stand alone primary site, 1 server does everything, no boundaries or boundary groups.

My problem - I created a task sequence to install Windows 8.1, PXE boot to the sever works just fine, I select the TS for Windows 8.1 and it fails with Failed to Run Task Sequence. The SMSTS.log file shows

1-png.476


The package that it fails to find is the x64 boot image, which was just used to PXE boot the machine. I've checked the SMSPKGD$ share on the server and the WRI00005.wim package is in that location in a folder called WRI00005.

Network Access Account is a member of the domain admins group

So to recap, the boot package is distributed to the DP, no boundaries or boundary groups are setup since I only have a small network and one server that hosts all the site system roles and network access account is a domain admin.

Thanks again for the help!

Chris
 

Attachments

  • 1.PNG
    1.PNG
    37.4 KB · Views: 82
no boundaries or boundary groups are setup since I only have a small network and one server that hosts all the site system roles and network access account is a domain admin
You should configure the boundary and boundary group. There is no harm in configuring it. Also did you try redistributing the WRI00005 package to the distribution point ?. In most of the cases redistributing the package to DP resolves the issues.
 
Thank you for the reply. I have redistributed the WRI00005 package to the DP and verified that it was actually there by checking to the SMSPKGD$ share. I'll create the boundaries and boundary groups and assign the site server and see what happens and report back.
 
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!
 
Status
Not open for further replies.

Forum statistics

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