2 Replies Latest reply on Nov 12, 2013 2:55 AM by saint_stevo

    Packages only install on login

    saint_stevo Apprentice
      Hello

      We have noticed that since we went from enteo v6 to DSM 7.02 the only time our packages run on clients is after login, whereas before packages would apply shortly after deployment.

      Any ideas how we can get the packages applying as before?

      Thank You
        • 1. Re: Packages only install on login
          Klaus Salger Expert
          Hi,

          this is most likely because the agent and service polling frequency settings have been reset to higher values when updating to DSM7.
          You can adjust them in the infrastructure view / org or site / configuration / autoinstall settings / polling frequency of agent + / service settings / service polling interval.

          Before doing so - do you really need short polling intervals?

          From my point of view longer polling intervals (something like 10 or 12 hours) are better in general.
          1. the infrastructure is less loaded
          2. changes are not immediatly distributed to a high number of clients while you are changing it
          3. if something goes wrong the damage is less because a lower number of clients will be affected until you notice it
          4. users will be disturbed more seldomly because installations will usually start at startup or logon only
          5. if you want to update some specific clients after you assigned new packages you may do so by using "execute changes" from the context menu

          So there may still be reasons for using a short polling interval but it's well worth thinking about it.

          Cheers
            Klaus
          • 2. Re: Packages only install on login
            saint_stevo Apprentice

            Hi,

            this is most likely because the agent and service polling frequency settings have been reset to higher values when updating to DSM7.
            You can adjust them in the infrastructure view / org or site / configuration / autoinstall settings / polling frequency of agent + / service settings / service polling interval.

            Before doing so - do you really need short polling intervals?

            From my point of view longer polling intervals (something like 10 or 12 hours) are better in general.
            1. the infrastructure is less loaded
            2. changes are not immediatly distributed to a high number of clients while you are changing it
            3. if something goes wrong the damage is less because a lower number of clients will be affected until you notice it
            4. users will be disturbed more seldomly because installations will usually start at startup or logon only
            5. if you want to update some specific clients after you assigned new packages you may do so by using "execute changes" from the context menu

            So there may still be reasons for using a short polling interval but it's well worth thinking about it.

            Cheers
              Klaus



            Thank you very much, that all makes sense