4 Replies Latest reply on Feb 22, 2008 8:41 AM by Jared Barneck

    Software distribution task looking in C:\ldclient for sdclient.exe

    Rookie

      This has happened in different areas of LANDesk without warning and for no apparent reason (especially in OSD).  Now our software distribution tasks are looking in C:\ldclient for sdclient.exe instead of C:\Program Files\LANDesk\LDClient... and all the computers return a "the system cannot find the specified file" error.  Has anyone else seen this or know how to fix it?  We have hard coded the correct path in our OSD scripts, but I am not sure what to do with software distribution tasks.

        • 1. Re: Software distribution task looking in C:\ldclient for sdclient.exe
          Rookie

           

          Hi,

           

           

          First of all, mention what version of LANDesk and SP you have installed. LANDesk resolves this variable %LDMS_CLIENT_DIR% to client's path. And client's path is reported in the Inventory (Computer.LANDesk Management.Client Path). If this is not in the Inventory, then run a full Inventory scan on all of your clients to make sure you have the correct data.

           

           

          • 2. Re: Software distribution task looking in C:\ldclient for sdclient.exe
            Rookie

            Sorry, our version is 8.7 SP3 and all of our clients have the

            C:\Program Files\LANDesk\LDCleint path to the sdclient.exe file.  Every

            now and then something makes it decide to look in C:\ldclient (which is from

            an older version) and everything fails.  I am not sure where to troubleshoot this.

            • 3. Re: Software distribution task looking in C:\ldclient for sdclient.exe
              Rookie

              We tried adding the path to the server's Environment Valriables and it now seems to be working.  Not sure if this was the fix, but I thought I would post an update.

              • 4. Re: Software distribution task looking in C:\ldclient for sdclient.exe
                Jared Barneck SupportEmployee

                Ronregan,

                 

                The earlier post told you everything you need to troubleshoot:

                 

                First of all, mention what version of LANDesk and SP you have installed. LANDesk resolves this variable %LDMS_CLIENT_DIR% to client's path.

                 

                So now you know we use a variable.

                 

                And client's path is reported in the Inventory (Computer.LANDesk Management.Client Path).

                 

                This is not an environment variable, it is a Core Server variable.  This variable is resolved on the Core Server based on Inventory data before the command is even sent to the client.  This is the location in the database.  From the console, right click on a device and view it's inventory.  Browse to LANDesk Management and look at the Client Path, if it is even there.  If it is not there, the default value of C:\ldclient is used.  This default value is hard set in the code currently. 

                 

                If this is not in the Inventory, then run a full Inventory scan on all of your clients to make sure you have the correct data.

                 

                The only way to make the device use C:\program files\LANDesk\LDClient is to have a full inventory scan from the machine.  You are probably having an inventory issue, so this machine does not have a full inventory scan.