Failed to run Task sequence: The task sequence cannot be run because the program files for P01xxxxx cannot be located on a distribution point

Question

_{Sunday, January 27, 2013 5:09 PM}

I configured Operating System Deployment feature in System Center 2012 SP1 Configuration Manager to deploy Windows 7 on new machines, Computer start boot with PXE successfully -> load Boot image -> select task sequence -> then it show the following error:

Failed to run Task sequence
The task sequence cannot be run because the program files for P01xxxxx cannot be located on a distribution point.
For more Information, contact your System Administrator or Helpdesk Operator.

I can confirm the following:

1. Boot images and all task sequence dependence successfully copied to distribution point.

2. Network Access Account is configure with domain admin account.

3. Boundaries group configure with fast connection.

I tried to check all settings and all look fine, but still receiving the error.

Abduljalil Abolzahab

All replies (4)

_{Sunday, January 27, 2013 5:32 PM}

You said you created boundary group but did you create a boundary group containing a boundary for site assignment and content location? This is necessary for OSD to work simply creating a boundary group doesn't allow your clients to find content you need unless that boundary group have a DP in content location under the references tab. Guide: http://technet.microsoft.com/en-us/library/gg712679.aspx. Also make sure the packages/apps your referencing is on the DP's and view the SMSTS log on a client that's failing to run the OSD to see if that gives you useful info.

Boundaries

Each boundary represents a network location in System Center 2012 Configuration Manager, and it is available from every site in your hierarchy. A boundary does not enable you to manage clients at the network location. To manage a client, the boundary must be a member of a boundary group.

Configuration Manager does not support the direct entry of a supernet as a boundary. Instead, use the IP address range boundary type. When Active Directory Forest Discovery identifies a supernet that is assigned to an Active Directory site, Configuration Manager converts the supernet into an IP address range boundary. For more information about Active Directory Forest Discovery, see the About Active Directory Forest Discovery section in the Planning for Discovery in Configuration Manager topic.

Boundary Groups

Use boundary groups to manage your network locations. You must assign boundaries to boundary groups before you can use the boundary group. Boundary groups have the following functions:

• They enable clients to find a primary site for client assignment (automatic site assignment).
• They can provide clients with a list of available site systems that have content after you associate the distribution point and state migration point site system servers with the boundary group.

To support site assignment, you must configure the boundary group to specify an assigned site for clients to use during automatic site assignment. To support content location, you must specify one or more site systems. You can only specify site systems with the distribution point or state migration point site system role. Both the site assignment and content location configurations are optional for boundary groups.

When you plan for boundary groups, consider creating one set of boundary groups for content location and a second set of boundary groups for automatic site assignment. This separation can help you avoid overlapping boundaries for site assignment. When you have overlapping boundaries and use automatic site assignment, the site to which a client is assigned, might be to is nondeterministic.

The following sections contain information to consider when you configure boundary groups.

Justin Chalfant | Blog: setupconfigmgr.com | SCUP Catalog: patchmypc.net/scup | Please mark as helpful/answer if this resovled your issue

_{Sunday, January 27, 2013 5:46 PM}

Thanks for respond and sorry for missing information, Yes boundary group contain site boundary, it's already configured.

Abduljalil Abolzahab

_{Monday, January 28, 2013 8:36 AM}

Using the info P01xxxxx, just check the content status and is it really deployed to every DP.

In Task Sequence Deployment object, you may want to check, are you allowing the content to be downloaded from another DPs.

_{Thursday, March 28, 2013 12:40 PM}

I had this issue also.

Because we had added an additional Boundary since the SCCM System had been put into place and before the discovery methods had had time to discovery the new boundary it didn't exist. I had to create it manually and add it to the boundary group.

So, check the IP address your client is getting is within an IP raqnge that has a boundary and boundary group associated with it.