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!
My task sequence fails with - "this task sequence cannot run because the program files for 00100002 cannot be located on a distribution point" (00100002 is config manager client).
If image is distributed correctly to Dp ,then it will take some time to replicate to Database. hence wait and refresh the policy and then run the task sequence again...
Hi, thanks for your reply. I've now got past that screen but am back to the first error
"This task sequence cannot run because the program files for 00100002 cannot be located on a distribution point". What can i do? which logs can i check?
I notice that my client package says 0 programs and has DEPLOY greyed out, so cant be deployed. Has anyone seen this before? the 'version' field is also blank
Hi,
This task sequence cannot run because the program files for 00100002 cannot be located on a distribution point
You can do following,
1. your network account to MANAGE ACCESS ACCOUNTS . It should work
2. Creating the Distribution Group and tying it to my Distribution Point
3. either you need to Update Distribution Point for the boot image, or that there are issues with your Boundary Group
If it is small business enterprise, then verify that DP is assigned to particular site or not.
1)
If it is assigned to Primary or seconadary site then, check those sites are within the protected boundary group or not.
2)
If it is not protected within boundary group, you need to set permission to protect within boundary group.
In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Site Systems.
Expand the site system server that is configured with the distribution point role that you want to protect.
In the results pane, right-click ConfigMgr site system, and then select Properties.
Click Enable this site system as a protected site system.
Click Select Boundaries.
In the Boundaries dialog box, click New.
In the New Boundaries dialog box, select a boundary from the list, and then click OK.
Once i install .Net Framework 3.5.1 Feature on the server, i was able to boot succesfully into SCCM Task Sequence Wizard.
I also was successfull installing the the PXE DP role from the console succesfully without having to install WDS first.
I think the problem is now solved. We only ever had one Active Directory Site in Sites and Services. Recently, our Network administrator created new sites, but hadn't added our subnets into Sites and services, so i think this was causing an issue trying to contact the DP.
Thank you for all the help/suggestions. I will double check that everything is now OK and confirm tomorrow.