1 Reply Latest reply on May 12, 2015 11:19 AM by Tanner Lindsay

    package bundle deployment status stays active even if all packages in the bundle are finished installing

    Rookie

      We are on LANdesk 9.5 SP3.

      When I create a package bundle and add the single packages right from the beginning in the desired sequence without ever changing the sequence from within the bundle properties, the deployment of the whole package bundle works fine. --> Means that all packages are ok and that the sequence of the packages is also ok.

       

      If I add the packages in random sequence and then change the sequence of the packages to the same sequence as in the above (working) bundle, very often the resulting package bundle will install all the included package in the right sequence but then leave the deployment status of the whole bundle in the scheduled task forever on "active" instead of setting it to "successful" after finishing the deployment.

       

      This happens consistently on all target devices (100% of them - I had a target set of 43 devices) to which I assign the scheduled task which then deploys the package bundle

       

      Is this a known bug? (I am relatively new to LANdesk and brand new to this forum). I have researched in the community forums but have not found anything related to this.

        • 1. Re: package bundle deployment status stays active even if all packages in the bundle are finished installing
          Tanner Lindsay SupportEmployee

          I'm not familiar with this particular problem. There were improvements and fixes to status information and bundles in LDMS 9.6 SP1. I would recommend that you set up a test Core Server on 9.6 SP1 and see if you have the same problem. With LANDESK you are allowed (encouraged really) to have multiple Core Servers without any additional licensing fees, which allows you to have a test environment separate from your production environment for testing things like this and preparing for upgrades. If you continue to have problems, or can't try it out, I would recommend you open a case so that one of our engineers can help you work through any issues or perhaps identify a bug.