System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Updating Content shouldn't cause running task sequences to fail

When you update content that is referenced by an application, devices currently running the task sequence will fail when they get to that step because the version of the files they were expecting is no longer available.

It has been suggested before to keep old versions of the content around on the DP so that these devices can successfully finish.

My suggestion is to either do that, or change it so that the content request is for a version equal to OR GREATER THAN what was validated at the beginning of the task sequence. This would be useful both inside and outside of OSD.

Packages can have a scheduled content update set up in the Configmgr GUI. Applications can have content updated for their deployment types via powershell. We use Task Scheduler to schedule these scripts over night so that they do not interfere w/ running Task Sequences.

Maybe another approach would be to not care about the version of the content at all. Regardless of approach, there should be a clear entry in the logs that content was used that isn't the same version as what was seen when validating content at the beginning of the task sequence. I'd put this in appenforce.log so that it is actually seen where the content is being used.