Share via

Task Sequence WIM file is pulled from primary site and not local DP?

durrie 406 Reputation points
2021-08-19T09:10:40.237+00:00

Hi all,

I have successfully built and deployed a number of MEMCM distribution points in branch offices using the following configuration...

  • Each branch office has a separate subnet defined in ADDS and assigned to a Site in ADDS.
  • Each branch office has a boundary configured in ConfigMgr. (type - IP Address range)
  • Each branch office boundary has the local DP assigned as a site system.
  • The DPs are PXE enabled, without WDS.
  • The DPs use HTTPS communication with a custom cert exported from my internal PKI and installed locally on each DP.
  • The task sequence is distributed (including all dependencies) to all DPs.

I can successfully boot PCs using PXE, the boot image pulls from the local site based DP, I enter my branch specific task sequence wizard password, I select my desired task sequence and it begins, partitions the local disk however...

Then when it gets to downloading the WIM for OS install it pulls the WIM file from my primary site server and not from the local DP?

Additional info - all branch based PCs successfully pull patches from their local DP repositories...

What am I missing here from an OSD perspective? Why is my WIM file pulling from my primary site and not my locally based DPs?

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
912 questions
0 comments
Accepted answer
  1. HanyunZhu-MSFT 1,841 Reputation points
    2021-08-20T03:03:02.327+00:00

    Hi,

    As you mentioned that, you met an error 0x80070002 when deploying WIM.
    The error code 0x80070002 means that "The system cannot find the file specified".

    To solve this problem, we may need to confirm that the option "Access content directly from the distribution point" has been checked in the step “Apply Operating System” first.
    124941-1.png

    Then, after configuring the WIM file for this set the “Copy the content in this package to a package share on the distribution point” setting in the Data Access tab of the properties of the WIM file.
    It is needed to redistribute the WIM file
    124869-2.png

    If the response is helpful, please click "Accept Answer"and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pavel yannara Mirochnitchenko 11,956 Reputation points MVP
    2021-08-19T10:34:43.217+00:00

    Make sure your wim is distributed to all DPs and also disable the option than clients can bull content from neiberhood.

  2. durrie 406 Reputation points
    2021-08-20T12:52:37.91+00:00

    Thank you HanyunZhu-MSFT,

    Indeed your suggestion has worked perfectly and the OS is now deploying and being pulled from the local Site based DPs.

    My TS is failing now failing on the "Setup Windows and Configuration Manager" step which comes next in the TS but I will raise a new question on that issue.

    0 comments