3 Replies Latest reply on Aug 22, 2016 3:44 PM by csoto

    LANDESK 2016 Agent deployment with ARD?

    velo2k77 Apprentice

      With LDMS 9.6sp2 and older we have been able to pull the .pkg file off of ldlogon/mac and push it out with Apple Remote Desktop or just by installing it locally on the machine.


      With Landesk 2016 the pkg file is now enclosed in a dmg file.  When I pull the .pkg out of the .dmg file to deploy with ARD I get an error saying "LDMS Agent install failed: couldn't find components to install.  This installer needs to be launched from the disk image in which it was delivered."  I get the same message if I try to use the ldmsagent.pkg file  (when removed from the .dmg) and install it manually.  The installer seem requires being installed from inside the .dmg.


      Has anyone found a workaround for this as this complicates our method of deploying the agent to machines that don't already have the agent?

        • 1. Re: LANDESK 2016 Agent deployment with ARD?
          jerrod Apprentice

          I tried the same thing and found there was a hidden directory with a bunch of packages in the DMG. I just used a shell script to download and install from the DMG instead.

          • 2. Re: LANDESK 2016 Agent deployment with ARD?
            velo2k77 Apprentice

            We ended up doing something similar.  But then we also created an "offline installer" with the dmg embedded in the pkg.  So far both methods seem to work well.

            • 3. Re: LANDESK 2016 Agent deployment with ARD?
              csoto Specialist

              This was a real pain for us, as ARD was our go-to for getting a new agent out.


              I have a workaround that you can use in ARD (or command line via SSH on a onesey-twosey basis):

              mkdir /tmp/ldlogon

              mount -t smbfs //username:'password'@your.core.server/ldlogon/mac /tmp/ldlogon

              /usr/bin/hdiutil mount /tmp/ldlogon/Default\ Mac\ Configuration.dmg

              /usr/sbin/installer -pkg /Volumes/LDMSClient/ldmsagent.pkg -target /

              This will install the "Default Mac Configuration" Agent Configuration. Change that and the core server DNS as appropriate. Unless the "ldlogon" share has wide open read permissions (probably a bad idea), you'll also need to provide credentials for a user that has access to it (presumably what you run the scheduler service as).


              You can use the ARD "Send Unix Command" to do this.