This article only applies if the majority of the task targets are able to run the task properly, but one or a few targets get stuck in Asynchronous Policy Execution state.  This indicates an issue with the devices themselves.  If ALL devices in the task get stuck in this state, it usually indicates a core-side issue which is addressed in these documents:

How to troubleshoot tasks hung with a status of "Client has initiated asynchronous policy execution"

"Client has initiated asynchronous policy execution" - Return Code 1354

Issue: Tasks are stuck in active with the result "Client has initiated asynchronous policy execution"

More Info

Asynchronous Policy Execution is not an error, but a status message.  It indicates that the task has not started on the target device because it is waiting for something else to complete.  This could be a vulnerability scan (vulscan.exe), a software install (sdclient.exe) or a process initiated by sdclient.exe or vulscan.exe (msiexec, wusa, cmd etc.).

Under normal circumstances, the other process will finish and close out allowing the task to move beyond Asynchronous state.  However, on occasion, the actions being initiated get stuck, preventing other tasks from continuing.  This document is intended to troubleshoot and address this condition.

Troubleshooting

First, check task manager on the device in question. Look for any of the following processes:

• vulscan.exe
• sdclient.exe
• MSIExec.exe
• sdistbat.exe
• cmd.exe

Sometimes, simply ending task on these processes or rebooting the client device will clear up the Asynchronous state.  If this doesn't work, or if none of these processes are running, then we will move on to clearing out stuck policies on the core and client.

1. On the core, locate the device in question in Network View, right click, and select Scheduled Tasks and Diagnostics.  This window will list all tasks the device has been targeted by from the core.  Look for any old tasks that are still in an active, working, waiting or any other state besides Done or Failed:
   
2. Double click the bad task, which will open it up in Scheduled Tasks.  You can then delete the task or remove the device in question from the target list.  This removes the policy for this task on the core.
   
3. Next, we want to clear out the policies on the client.  Open %ProgramData%\Landesk\Policies\ and delete all .xml and .STAT files.  Open the subfolders and delete any files in there as well. 
   
4. Back on the core, delete the original scheduled task in which the device is in asynchronous state, and recreate it.  Target the device and start the task, and it should now run successfully.
   
   

Attached to this article is a .ldms file that you can import to your managed scripts to accomplish this remotely or for many devices at once.  Select the version that matches your LDMS version.

PLEASE NOTE:  This script is provided as a courtesy only and may need to be edited or adjusted for your particular needs - Ivanti Support does not support custom scripts and will not be able to assist if this script causes unexpected issues.