Skip to content

May 14, 2012

OSD: Access content directly from DP in TS problem

I ran into a problem after migrating my task sequences from Configuration Manager 2007 to 2012.  I found that I could not easily set my task sequence deployments to use the setting “Access content directly from a distribution point when needed by the running task sequence.”  By default it was setting itself to “Download content locally when needed by running task sequence.”

As I found documented on the web, I had to first edit all my packages (Boot images, OS Installers, Driver packages, software packages) to store content on the package share on distribution points.  To do this, edit package properties, click Data Access tab, and check the box “Copy the content in this package to a package share on distribution points”.  Once that setting was selected on all packages in the task sequence, I then regained the ability to select “Access content directly from a distribution point when needed by the running task sequence” option on the task sequence deployment.

However, I then found an additional issue, (I also found other users also having the same issue but with no solution).  Every time I selected the “Access content directly from a distribution point when needed by the running task sequence” setting and clicked OK, and then re-opened the properties, it would revert back to “Download content locally when needed by running task sequence.”  After many hours of troubleshooting I ended up discovering that as far as I can tell, this is simply a bug in the GUI.  Once you select the setting “Access content directly from a distribution point when needed by the running task sequence” it does appear to run with that setting, there is just no way in the GUI to confirm this setting is set.  Also, if you ever edit the deployment, you have to make sure to reselect the  “Access content directly from a distribution point when needed by the running task sequence” option everytime or it will revert back.

Hopefully this is helpful to someone and hopefully Microsoft will fix this GUI issue in an upcoming update.

Share your thoughts, post a comment.

(required)
(required)

Note: HTML is allowed. Your email address will never be published.

Subscribe to comments