4 Replies Latest reply on May 19, 2017 1:12 AM by kthiry

    [LDMS 2016.3 SU3] Run from source does not work?

    kthiry Rookie

      Hello everyone,

       

      I'm trying to distribute packages using the "Run from source" option, but with no luck.

      Maybe one of you could enlighten me?

      Here's the setup:

       

      Servers:

      - 1 LDMS 2016.3 SU3 core server & 1 preferred server

      - The preferred server part is working and the shares are configured and reflects the HTTP folder structure

       

      Client:

      -  Freshly installed, with a proper 2016.3 SU3 agent

      -  The "Run From Source" option is enabled in [Agent Settings/Distribution and Patch Settings/Distribution-only settings/Download Options]

       

      Package & task:

      - The package path is an HTTP one (which is successfully resolved into UNC and redirected to the preferred server - see the logs below)

      - The "Run From Source" option is enabled in [Task settings/Download options]

       

      What seems to work:

      - Preferred server redirection

      - HTTP to UNC translation

       

      What does not work:

      - The UNC share isn't mounted and thus the package is never executed

      - I suppose the LSWD package can not run from source with a HTTP path line in the log is the reason why

      - Yet the agent return a success!

       

      sdclient_task*.log

      Fri, 05 May 2017 11:35:10 ******* sdclient starting to process task *******

      Fri, 05 May 2017 11:35:10 Task id to process: 3232

      Fri, 05 May 2017 11:35:10 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.3232.RunNow._zoy+XA+REUszuztfIBMfCa2K12E=.xml"

      Fri, 05 May 2017 11:35:10 The nostatus flag has NOT been set.

      Fri, 05 May 2017 11:35:10 Core name 'CORE-SERVER' obtained from the registry

      Fri, 05 May 2017 11:35:10 Sending task status, cmd line -coreandip=CORE-SERVER -taskid=3232 -retcode=229392442 -pkgid=1049

      Fri, 05 May 2017 11:35:11 IsFileInCache: Cache2.GetFilePrevCountEx failed - path=http://CORE-SERVER/Packages/Windows/7Zip-16.04-Inst.exe

      Fri, 05 May 2017 11:35:11 File (http://CORE-SERVER/Packages/Windows/7Zip-16.04-Inst.exe) is not in cache

      Fri, 05 May 2017 11:35:11 The nostatus flag has NOT been set.

      Fri, 05 May 2017 11:35:11 Core name 'CORE-SERVER' obtained from the registry

      Fri, 05 May 2017 11:35:11 Sending task status, cmd line -coreandip=CORE-SERVER -taskid=3232 -retcode=229392258 -pkgid=1049

      Fri, 05 May 2017 11:35:11 ExpandEnvironmentVariables Result:

      Fri, 05 May 2017 11:37:06 Updating system environment variable LDMS_PREFERRED_SERVER: PREFERRED-SERVER

      Fri, 05 May 2017 11:37:06 Download of 'http://CORE-SERVER/Packages/Windows/7Zip-16.04-Inst.exe' was redirected to '\\PREFERRED-SERVER\Packages\Windows\7Zip-16.04-Inst.exe'

      Fri, 05 May 2017 11:37:06 LSWD or Executable Client Thread

      Fri, 05 May 2017 11:37:06 PackagePath: [http://CORE-SERVER/Packages/Windows/7Zip-16.04-Inst.exe]

      Fri, 05 May 2017 11:37:06 LSWD package can not run from source with a HTTP path.

      Fri, 05 May 2017 11:37:06 Installation result 32

      Fri, 05 May 2017 11:37:06 RunPackageInstall: stop on returncode=32 of package=7Zip-16.04-Inst.exe

      Fri, 05 May 2017 11:37:06 processing of package is complete, result 50 (0x00000032 - code 50)

       

      sdclient.log

      Fri, 05 May 2017 11:35:10

      RunAppMain: command Line : /policyfile="C:\ProgramData\LANDesk\Policies\CP.3232.RunNow._zoy+XA+REUszuztfIBMfCa2K12E=.xml"

      Fri, 05 May 2017 11:35:10 Core name 'CORE-SERVER' obtained from the registry

      Fri, 05 May 2017 11:37:06

      Fri, 05 May 2017 11:37:06 CPolicyHistory::LoadHistoryDaysToKeep: No task history maintenance to perform, registry settings for task history maintenance mode is '-1'

      Fri, 05 May 2017 11:37:06 PostInstallInventoryScan: Getting post package install inventory delay setting.

      Fri, 05 May 2017 11:37:06 PostInstallInventoryScan: Not running post package install inventory scan, the inventory scan delay value is out of range, min is 5, max is 60, current value is '-1'

      Fri, 05 May 2017 11:37:06 The nostatus flag has NOT been set.

      Fri, 05 May 2017 11:37:06 Core name 'CORE-SERVER' obtained from the registry

      Fri, 05 May 2017 11:37:06 Sending task status, cmd line -coreandip=CORE-SERVER -taskid=3232 -retcode=50 -complete -pkgid=1049

      Fri, 05 May 2017 11:37:33

      RunAppMain: command Line : /refreshtaskhistory

      Fri, 05 May 2017 11:37:33 CPolicyHistory::LoadHistoryDaysToKeep: No task history maintenance to perform, registry settings for task history maintenance mode is '-1'

      Fri, 05 May 2017 11:37:33 RunAppMain: Task history refreshed.

      Fri, 05 May 2017 11:37:33

       

      Any tips? Am I missing something important?

        • 1. Re: [LDMS 2016.3 SU3] Run from source does not work?
          Tanner Lindsay SupportEmployee

          What happens if you change the package to have a UNC path? I know it gets redirected to UNC with the Preferred Server, but you aren't downloading, so it is basically being told to run from source from HTTP, which just doesn't work generally (just like with a browser you have to download applications from the internet before running). I thinking if you set the package as UNC instead of HTTP, it will work.

          1 of 1 people found this helpful
          • 2. Re: [LDMS 2016.3 SU3] Run from source does not work?
            kthiry Rookie

            Hi Tanner,

             

            Thanks for your answer.

            Yes, it works when the package have a UNC path. Is it mandatory in order to use the "run from source" option?

            I believed LanDesk could translate an HTTP path into a UNC one (as hinted in the .log file), that's why I was confused.

             

            Regards,

            Kevin.

            • 3. Re: [LDMS 2016.3 SU3] Run from source does not work?
              Tanner Lindsay SupportEmployee

              Yes, using UNC is required when you choose "run from source" because it just isn't really possible to run from source from HTTP. If you want to use run from source, the package has to have a UNC source, and any Preferred Server that you would like to have it use must have the UNC path available as well.

               

              As to translating between HTTP and UNC, yes, LANDesk/Ivanti can swap between the protocols for downloading files, but only for downloading. When running from source, some small instruction files may be downloaded but the main package will be run from the source, if it is UNC.

               

              Regarding run from source in general, in my experience doesn't always have the advantages that you might be looking for. If the idea is to conserve bandwidth, and you are doing a basic install, it doesn't necessarily reduce bandwidth - the files/data still has to be copied to the machine to install the software, and sometimes it works out to be larger, as some of the files were compressed. Additionally, you can't benefit from the bandwidth control/throttling because it is just executed by Windows and goes as fast as it can and is subject to any interruptions or network issues; and it must use UNC. Alternatively, if you download the files, it can come from a UNC share, or HTTP and the download of the files can be controlled to limit impact to the network, use multicast when targeting large numbers of machines, and benefit from peer downloading. However, in some circumstances running from source is a great option - maybe the installer can figure out that only a subset of files are needed, or maybe there is a storage constraint on the client machines.

               

              Hopefully this information can help you out when planning your deployments.

              • 4. Re: [LDMS 2016.3 SU3] Run from source does not work?
                kthiry Rookie

                Nice detailed post, thanks!

                My idea was to use run from source in order to minimize latency between actions in a provisioning context, but I guess, as you said, that the gain would be minimal.