Unable to deploy Application with a Task Sequence Deployment type AFTER modifying the Application.

Southland, John 1 Reputation point
2020-12-23T19:19:49.497+00:00

I am unable to deploy an Application with a Task Sequence Deployment type after modifying the Application.

Steps to re-produce

Create a Package which contains source files and the source folder is set to the FQDN file share where the source files exist. Do not create a Program for the Package.
Package is successfully distributed to all distribution points.
Create Task Sequence, NOT high-impact NOT high-performance power plane with two steps

  • Set TS var OSDLogPowerShellParameters to TRUE
  • Run PowerShell Script, select the package created above and script name of the .ps1 file

Successfully test the Task sequence by directly deploying the TS to a valid collection

Remove the TS deployment, and convert to an Application with the Task Sequence Deployment type
Create an Application, manually specifying the application info.

  • Single deployment type, type is Task Sequence,
  • Provide a app version number to keep track of changes to the application.
  • Select same Task Sequence
  • Provide a detection method
  • Install for system, whether or not a user is logged in

On this new application, create a deployment type, deploy as Available to the same collection as previously.
Manually reset the client so that the detection method is no longer valid and it needs to install the application.
Initiate the machine policy and app deployment policy. Wait Software Center to update and show the available application. Install the application successfully.

Now we simulate a new version of the application, which requires we update the application, for this test I will change JUST the application version.
Again, manually reset the client, initiate machine and app deployment policy. Wait Software Center to update and show the available application. Attempt to Install the application, but this time the application will go to an status failed with a retry button within a few seconds.

smsts.log

Successfully read 304 policy assignments. TSAgent 12/23/2020 10:58:29 AM 10492 (0x28FC)
Setting _TSTSDTInstallRequestId:{C99BEC8E-9D35-4607-851A-904396689080} TSAgent 12/23/2020 10:58:29 AM 10492 (0x28FC)
GetAssignment() returned NULL pointer TSAgent 12/23/2020 10:58:29 AM 10492 (0x28FC)
No task sequence policies are targeted to the provisioning device. Code 0x87d00215 TSAgent 12/23/2020 10:58:29 AM 10492 (0x28FC)
Error initializing Task Sequence environment. Code 0x87d00215 TSAgent 12/23/2020 10:58:29 AM 10492 (0x28FC)
Task sequence launcher deployment failed!. Code 0x87d00215 TSAgent 12/23/2020 10:58:29 AM 10492 (0x28FC)

As a work-around to get it to work. I delete the deployment, deploy again to the same collection with the same settings. Initiate machine and app deployment policy and then wait for Software Center to update. This time successfully install the application.
Here is the smsts.log from what I believe to be the point of failure previously.

Successfully read 306 policy assignments. TSAgent 12/23/2020 12:17:40 PM 10868 (0x2A74)
Setting _TSTSDTInstallRequestId:{47982FE8-E6DC-40AD-9EC5-E0970DB6BF65} TSAgent 12/23/2020 12:17:40 PM 10868 (0x2A74)
Policy id: SMS10000-BDC0009C-DBBBC9D6 TSAgent 12/23/2020 12:17:40 PM 10868 (0x2A74)
Policy flags: 0x00000016. TSAgent 12/23/2020 12:17:40 PM 10868 (0x2A74)
Debug mode: 0. TSAgent 12/23/2020 12:17:40 PM 10868 (0x2A74)

The only thing that changed between not-working and working was deleting and re-creating the deployment.

There are two other entries in this Q&A site that are very similar.
Applications with task-sequence deployment type not visible in Software Center - Microsoft Q&A
Application: Deployment Type - Task Sequence (pre-release feature) fails with 0x87d00215 - Microsoft Q&A

Digging through WMI at Root\ccm\Policy\machine\RequestedConfig CCM_TaskSequence, the TS does disapeear once I edit/modify the Application.

Get-WmiObject -Namespace ROOT\ccm\Policy\Machine\RequestedConfig -class CCM_TaskSequence  

Application installation error codes reference - Configuration Manager | Microsoft Learn
Based on this page, error 0x87D00215 is Item not found. And it references checking on application deployment or application content. In this case both SHOULD be valid, as both the Deployment and Package work before modifying the Application. Any change to the Application seems to break the connection between the Application and the Task Sequence Deployment Type.

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
894 questions
Microsoft Configuration Manager Application
Microsoft Configuration Manager Application
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Application: A computer program designed to carry out a specific task other than one relating to the operation of the computer itself, typically to be used by end users.
453 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Simon Ren-MSFT 29,716 Reputation points Microsoft Vendor
    2020-12-24T08:47:06.787+00:00

    Hi,

    Thanks for posting in Microsoft MECM Q&A forum.

    Yes, you are right, the error code 0x87D00215 means "Item not found". May we know what version of SCCM you are using?

    Thank you very much for your test and efforts. I will do more research and try my best to deliver it to the product team. Once there is any update, I will get back to you at the first time. Thank you for your kind understanding.

    Best regards,
    Simon


    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.