Quick Guide to Agent Install Failures

Version 4

    Verified Product Versions

    LANDESK Management Suite 9.6LANDESK Management Suite 2016.x


    LDMS 9.x with any supported client OS



    The LANDESK agent install can fail for many reasons. This document is intended to be a quick guide for some of the basic things to look at. For a more detailed troubleshooting guide see: http://community.landesk.com/support/docs/DOC-31663



    If in the course of attempting to deploy a client configuration to a new client (i.e. client without the LDMS agents installed), you can check the following things to determine what the problem is:

    1. A common reason for failing is that the DNS database is misconfigured.  Check by pinging from the core to the client and the client to the core.  If the IP addresses don’t match up and if the pings don’t complete successfully, address this first before trying UDD again.
    2. Check the scheduled task handler log file for errors:  In the “c:\Program Files\LANDesk\ManagementSuite\log” folder you’ll find a couple of files to check:
      1. raxfer.log: log info for the remote-copy and remote-execute actions taking during the agent deployment.
      2. ScheduledTaskHandler_XXX.log:  The XXX is the number the corresponds to the task ID.  This contains log information for the task handler that deploys the agent.
      3. SchedSvc.log: Log info for the scheduler service.
    3. On the targeted client computer, monitor the root of the C drive (i.e. the C$ share) and look for a new directory created called $ldcfg$.  If this doesn’t get created it is likely that “Simple File Sharing” hasn’t been disabled on a Windows XP client or that the username and password in the service config utility on the core isn’t correct for this client. (As a test you can try mapping a drive from the core server to \\clienthostname\c$ to see if it works using the username and password entered in service config for the client.  If this fails, agent configuration will fail.)  After being created the $ldcfg$ folder should have a few files in it such as IPCheck.exe, tmpXXX.tmp (where XXX is a random set of characters), LandeskClientInstallStatus.txt.  When the install has completed this folder should be deleted automatically.
    4. Watch the Windows Task Manager and look for the following process that should run during the client deployment: 
      1. tmpxxx.tmp: Yes, this is an executable even though it has a .tmp extension.  If this fails to run, the service manager may be having trouble starting a service remotely from the core server.
      2. IPCheck.exe: Runs very quickly, it is likely you won’t see it run.
      3. wscfg32.exe: This is the main installer.  It takes a while to run.
    5. Ping the core from the client and make sure you get a response. If you don’t:
      1. Win2k 8– Go to firewall advanced settings and make sure network discovery is turned on.
      2. Win2k3 – Go to firewall settings, turn on the fire wall and check the following exceptions:
        • File and Printer Sharing
        • Remote Desktop
        • UPnP Framework
      3. Ping from the client and get a response from the server.


    For Additional Troubleshooting see:


    Agent Deployment Results in error: "Unable to contact the specified machine"

    Documentation for Agent Configuration and Deployment for LANDesk 9 release