question

SebastianRompza avatar image
0 Votes"
SebastianRompza asked ·

Application: Deployment Type - Task Sequence (pre-release feature) fails with 0x87d00215

We are using MEMCM 2006 (HTTPS only) and activated the pre-release feature "Task Sequence as an app model deployment type install method" to deploy the Citrix XenDesktop Virtual Delivery Agent (VDA) 1909. Depending on the exit code this application's setup must be restarted after a reboot for a second time. Citrix recommends using a task sequence for deployment and I thought combining the reboot proof task sequence technique with the powerful detection rules of the application model would be great. Now the problem is that I can't make it work. Following a part of the smsts.log:

Successfully retrieved TS launch information. TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Time zone: -60,0,-60,0,10,0,5,3,0,0,0,0,3,0,5,2,0,0,0,Mitteleuropäische Zeit,Mitteleuropäische Sommerzeit TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Successfully retrieved Current TimeZone information. TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Retrieving DP Auth token from MP. TSAgent 20.10.2020 17:10:47 9820 (0x265C)
SSL, using authenticator in request. TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Successfully retrieved Distribution Point auth token from Management Point TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Downloading policy from https://MP.domain.net. TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Preparing Policy Assignment Request. TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Executing Policy Assignment Request. TSAgent 20.10.2020 17:10:47 9820 (0x265C)
SSL, using authenticator in request. TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Request client ID: GUID:XXXXXXXX-YYYY-YYYY-YYYY-ZZZZZZZZZZZZ TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Response client ID: GUID:XXXXXXXX-YYYY-YYYY-YYYY-ZZZZZZZZZZZZ TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Successfully read 131 policy assignments. TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Setting _TSTSDTInstallRequestId:{UUUUUUUU-VVVV-VVVV-VVVV-WWWWWWWWWWWW} TSAgent 20.10.2020 17:10:47 9820 (0x265C)
GetAssignment() returned NULL pointer TSAgent 20.10.2020 17:10:47 9820 (0x265C)
No task sequence policies are targeted to the provisioning device. Code 0x87d00215 TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Error initializing Task Sequence environment. Code 0x87d00215 TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Task sequence launcher deployment failed!. Code 0x87d00215 TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Active Request Handle. Error code 0x80070002 TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSAgent 20.10.2020 17:10:47 9820 (0x265C)
Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister with options (0, 0) TSAgent 20.10.2020 17:10:47 9820 (0x265C)

The error seems to be 0x87d00215 Item not found

Here is how I build the application so far:

  • created a package with the source files

  • distributed the package to the DPs

  • created a task sequence with a Run Command Line step using the package and the install command

  • configured a reboot and a second start of the command line depending on the _SMSTSLastActionRetCode variable

  • created an application with TS deployment type and the application detection rules

  • deployed the application to the target collection (device collection) as required

I realized that I cannot distribute the application (or the deployment type itself) to any DP because this deployment type has no source path.
The task sequence is not configured as high impact and I used no OSD steps.

There was a similar case but no real solution in the old forum.


mem-cm-application
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Amandayou-MSFT avatar image
0 Votes"
Amandayou-MSFT answered ·

Hi @SebastianRompza,

We could install the application manually in a computer to check if the application is normal. If so, please try to deployment it by using application or package tool of SCCM to check if single deployment is normal. If we create the deployment successfully, we could check distmgr.log to see if the application is copied to Contentlibrary, and finally copied from Contentlibrary to DP.

33844-10212.png


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.



10212.png (70.4 KiB)
· Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SCCMAdmin-5911 avatar image
0 Votes"
SCCMAdmin-5911 answered ·

Im having same issue, same error code. Running Task Sequence thru Application model does not work. get same error
"No task sequence policies are targeted to the provisioning device. Code 0x87d00215 TSAgent"

But If I deploy and run task sequence thru Software center , the task sequence works fine. Only when deploying thru the application model I get this error. Seems pre release feature needs some more work... ???

· Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.