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

Image may be NSFW.
Clik here to view.

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"

Image may be NSFW.
Clik here to view.

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:

Image may be NSFW.
Clik here to view.

If the IP address is the same, go to step III. Full Synchronization

If the IP address is not the same as the one you had earlier on the Console, run the following command from the client machine:

"C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /V /mini

And execute a PolicySync:

"C:\Program Files (x86)\LANDesk\LDClient\PolicySync.exe"

This will verify and update your IP address to the Core Server and then trigger the APM page from the Core with the correct Client information. Your task will then continue.

III.  Full Synchronization

If the Common Base Agent is Loaded and the IP address is not different from the one you actually have, then the message is showing because one or more files / components have changed during the task deployment.

In order to be sure that your Core Server and Client are properly up to date one for the other, you can launch a full synchronization scan from your client machine:

"C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /NOUI /SYNC

This will send not a delta but all the data from the client to the Core without showing any user interface.

And execute a PolicySync:

"C:\Program Files (x86)\LANDesk\LDClient\PolicySync.exe"

Now your task should be running as expected.

Image may be NSFW.
Clik here to view.

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"