Task Sequence deployed as Application

Question

Task Sequence deployed as Application

Matt Dillon 437

Trying out the new feature - Task Sequences as an Application and not exactly having the results I'd hoped for. It seems like the content will not download when run.

I have a Task Sequence that does some customizations (registry changes, user pictures, etc) and when deployed as a Task Sequence, it works fine. When I deploy it as an Application, I get the following errors in the logs:

AppEnforce.log:
The content path is not specified for DeploymentType ScopeIdxxx Content is assumed to be locally available.

AppDiscovery.log:
The Install action on AppDT "Sentinel Customizations - 20H2" xxx will not use managed content. The content location is not specified and is assumed to be locally available.

Not sure why the content will not download.

Thoughts?

Phil Brandvold 1 Reputation point

2021-06-25T20:54:18.263+00:00

I'm seeing the same issue with my ts type deployment for my app. I have the same issue called out in my log file on the client, but there's only one component of the TS that even CAN be distributed. I've tried re-distributing it to no avail.
Steve Burggraaf 1 Reputation point

2022-06-03T18:24:42.087+00:00

I'm not normally one to resurrect threads from over a year ago, but I'm in the exact same boat as @Matt Dillon . Has anyone found a resolution to this problem yet? Just like Matt, the task sequence itself runs perfectly fine as a standalone TS. As soon as I make it a deployment type in an application, I have the same errors in the logs.

2 answers

Your answer

Phil Brandvold 1 Reputation point

2021-06-25T20:54:18.263+00:00

I'm seeing the same issue with my ts type deployment for my app. I have the same issue called out in my log file on the client, but there's only one component of the TS that even CAN be distributed. I've tried re-distributing it to no avail.
Steve Burggraaf 1 Reputation point

2022-06-03T18:24:42.087+00:00

I'm not normally one to resurrect threads from over a year ago, but I'm in the exact same boat as @Matt Dillon . Has anyone found a resolution to this problem yet? Just like Matt, the task sequence itself runs perfectly fine as a standalone TS. As soon as I make it a deployment type in an application, I have the same errors in the logs.

Answer 1

SunnyNiu-MSFT 1,711

@Matt Dillon
Here is an answer to your question that hopefully you find helpful!

AppEnforce.log: The content path is not specified for DeploymentType ScopeIdxxx Content is assumed to be locally available.

To fix the issue, we may try to update the content on the DP, refresh the machine policy on the local client, then we could see the content starts to download followed by triggering the installation.

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.

Matt Dillon 437 Reputation points

2021-03-29T14:53:11.74+00:00

Well the thing is that this is a Task Sequence so there is no way to refresh/ update the dp's content. When I look at the Task Sequence itself, the content is 100% distributed. There is not option when deploying a task sequence using the application model to do anything with content.
SunnyNiu-MSFT 1,711 Reputation points

2021-03-30T07:59:56.373+00:00

If we couldn't find the TS in the drop-down menu, check our RBAC permissions. To be able to add a TS deployment type, we need to have the Read Task Sequence permission. It could be done by giving our account the Read-Only Analyst role (Which allows view on all Configuration Manager objects) or by creating a custom role with the sufficient permissions.

If the permissions are good, double-check that the TS doesn’t include the OS deployment or OS upgrade step and that we have not marked it as a high-impact Task Sequence.
Matt Dillon 437 Reputation points

2021-03-30T13:26:49.377+00:00

Let's start over, but you are definitely not understanding what is happening.
Matt Dillon 437 Reputation points

2021-03-30T13:27:22.34+00:00
I created a Task Sequence made up of "Run Command Line" and "Run PowerShell Scripts" type tasks which the new Task Sequence as Application Model supposedly supports.

I have deployed this Task Sequence as a Task Sequence and it works 100% of the time. The Power Shell scripts call Programs that are all Distributed.

I would like to deploy this Task Sequence using the new Task Sequence as Application model. This does not work 100% of the time because I get errors related to content.

With a normal Application, you are able to distribute the Application to Distribution Points. If you make changes to the Application, you can Update Content.
Matt Dillon 437 Reputation points

2021-03-30T13:31:56.563+00:00
Here is the exact steps I use to create this Task Sequence as Application.

SOFTWARE LIBRARY - Application Management - Applications - Choose folder I want to create the application in.

Create Application - Manually specify application information - fill in info/ add custom icon - Add deployment type - choose Task Sequence from drop down list - Give it a name - Choose the Task Sequence that was already created and tested as the Install task sequence - I skip the uninstall as I don't have an uninstall - I configure the detection rules (in this case a reg entry that gets created on the last task of the task sequence)

I select install for system - only when a user is logged on - normal (tried hidden as well) - and select allow users to view and interact with program installtion (tried this unchecked as well)

I add the requirements (the whole reason I want to do it this way) which is a custom OS detection, no software dependencies,
Matt Dillon 437 Reputation points

2021-03-30T13:38:17.263+00:00

Distribute Content is not an option nor should it be. It is a task sequence that has content that has already been distributed)

Perhaps this is the issue.

I deploy the application to my collection, (can skip past the Specify content distribution) and select install and Available.

The Application shows up in the Software Center and if I have selected Required - it fails and if I selected Available it fails after I run it for the original reason I posted here. I get content errors on my endpoints.

I am a Full Administrator on my SCCM console.

Thoughts?
Anonymous

2021-06-08T18:00:55.27+00:00

Did you find a resolution to this issue? I'm testing out the Task Sequence deployment type for Applications now and am running into this same issue.
ExhaustedTech 11 Reputation points

2023-11-28T05:17:03.1033333+00:00

Did you ever get this figured out? I'm trying to do the same thing and am getting the same error. I cannot get any information on this.

Answer 2

Matt Dillon 437

Alternatively, if someone can suggest some clever way to only run a task sequence if an OS is 20H2, that would be just as well. With the Application/ Task Sequence Model, I was hoping to take advantage of the custom software requirement and have it specify the os that way. I cannot seem to limit the deployment of the Task Sequence. I am going to upgrade SCCM soon. I hope that helps this issue as this could a very cool feature.

Rahul Jindal 11,626 Reputation points

2021-06-08T21:34:28.967+00:00

I will rather address your requirement than the problem you are facing. You can target a collection containing only 20h2 devices or you can add an OS condition at the beginning your TS to run only ehen OS build is 20h2.

Share via

Task Sequence deployed as Application

2 answers

Your answer