This article covers one of the reasons you might be facing this message. If you want to have a detailed troubleshooting guidance, please read the following article:How to troubleshoot tasks hung with a status of "Client has initiated asynchronous policy execution"

Environment

This message is present in LANDESK Management Suite 9.6    [26.11.14]

Description

When trying to deploy a package, whatever Task settings you use, you might see this message:

Client has initiated asynchronous policy execution

Cause(s)

This message tells you that the Client is trying to pull a policy from the Core Server and does not manage to get it as it looks to get stuck in a loop.

This highlights a communication issue between them.

It can be that:

• The IP Address has changed and has not bee updated which leads to a wrong identification process during Policysync
• The Common Base Agent is not installed / loaded and does not get contacted by the Core
• The Client has the wrong information in its registry that points to another Core Server

There might be other issues that will be reported if recognized.

Resolution

As explained earlier, we have to check these settings in order to ensure our Core and Client are ready not only to see each other, but to exchange data.

To do so, follow the next steps:

I.    Common Base Agent

From the Core Server

Right click on one of the client machine that has the issue and click "Properties"

What is important here is the Common Base Agent status.

If the status is: Not loaded

• You will have to uninstall properly the agent on your device by using the /forceclean parameter as indicated in this article: How to uninstall the LANDesk Agent
• Then delete the device from your Core Server inventory. If you want to be sure that the device is not anymore in the database, you can follow this article: Pending unmanaged client deployments - Devices are deleted but come back when refreshing
• After the device is deleted, double check the settings of your Agent configuration, then rebuild your agents, and schedule a deployment using our Unmanaged Device Discovery feature.
• Once the agent is properly and successfully deployed, check again the Common Base Agent status.

If the status is: Loaded

Go to the next step.

II.  Miniscan

Take note of your Client IP address, in our example:

192.168.1.63

Then go on your Client machine and check your actual IP address:

If the IP address is not the same as the one you had earlier on the Console, go to:

C:\Program Files (x86)\LANDesk\LDClient

And execute as an admin the following executable:

MINISCAN.exe

This will verify and update your IP address to the Core Server.

    This feature is automatically launched when modifying the IP address but an issue has been found and already fixed in the Service Pack 1 for LANDESK Management Suite 9.6 which has a soft release target of Mid to End December

Once this is done and you can see that your device now has the proper inventory data, you will be able able to recreate the scheduled task, target your device and start it:

If you see that your task remains in the "Task Queued at Client for Execution" status after that, please read the following article: How to resolve "Task Queued at Client for Execution"