5 Replies Latest reply on Oct 11, 2013 5:39 AM by zman

    Combine 2 distribution packages into a single package

    Rookie

      Hi,

       

      I would need some advises if LANDesk software distribution is able to achieve this:

      I need to distribute 3 files to client's C:\Windows dir and 1 file to %userprofile%\appdata\roaming dir (current login profile).

      My users do not have local administrator rights to write files into C:\Windows.

       

      I am using LDMS 9.5. Now, to do this, I am creating 2 distribution packages:

      1. Package A: Copy the 1 file to %userprofile%\appdata\roaming dir - run as "Current user's account (set under Package's Accounts menu)

      2. Package B: Copy the 3 files into C:\Windows - run as "LOCAL SYSTEM" (set under Package's Accounts menu)

       

      Then distributing them as separate packages/ scheduled tasks due to user permission restriction.

      Is there a way to combine the distribution into single package?

      Or, perhaps start task on Package A running as current login user and upon completion, it will automatically continue with Package B running as local system account.

       

      I have been trying on setting "Additional Files" in the package but it does not work as expected. How does it work?

       

      Appreciate if someone can share some info on this.

       

      Thank you.

        • 1. Re: Combine 2 distribution packages into a single package
          synsa Specialist

          I haven't exactly tried it before in this specific scenario but you could try putting the first "package A" as "Preliminary" and "Package B" as "Main".  These options if you are not aware are available on the "Distribution package" menu when creating a scheduled task.

           

          Alternatively, I would personally script this and then send it out as just the one package i.e. copy the file to windows and then copy the user file to all users profiles (All using the system account). 

          • 2. Re: Combine 2 distribution packages into a single package
            Rookie

            Hi synsa,

             

            Thanks for the reply. I just tried using the prelim and main method, however the Package A and B both run as LOCAL SYSTEM where I can't see the file being copied into my login user profile.

             

            This is what I did, in Package B under distribution packages,

            1. Go to "Additional files" windows, add the path to my Package A script. Note, in my script, I did not specify which user to run as. I am relying on the LANDesk package "Accounts" settings to configure which user it should run as.

            2. Go to "Prerequisites", select "Run additional file" then choose my Package A.

            3. Create a schedule task on Package B (main).

             

            The task is able to run, it copies files into my C:\windows but not login user profile.

             

            Any ideas?

            • 3. Re: Combine 2 distribution packages into a single package
              synsa Specialist

              The only thing I can think of is to create a 3rd "do-nothing" type package which literally does nothing and put the other two packages as dependants in the order you want executed OR if you have 9.5 SP1 (unsure if 9.5 has the option) you can create a new bundle and put both packages in to the bundle and schedule the bundle deployment.

               

              Are you any good at batch, VBS or powershell?  I recommend just using a script.

              • 4. Re: Combine 2 distribution packages into a single package
                Rookie

                Great! Thanks a lot. It is working the way I wanted now using the 3rd package that calls Package A and B in sequence.

                Though it sounds complicated to call dependant packages, I am happy that it works now.

                 

                Awesome, synsa

                • 5. Re: Combine 2 distribution packages into a single package
                  zman Master

                  So some other options that may work.

                  1. Create one package (script package A and B) and Package A logic use startasuser http://community.landesk.com/support/docs/DOC-1575
                    1. Or for two distribution packages in the distribution package use run as current user (Package A)- You will still have two packages.

                   

                  I you use one package then there is less to troubleshoot and maintain. If you use two packages then you have to maintain two packages, etc...