Loading
search-img

SamuelBaughan asked a question.

January 3, 2019 at 8:00 AM
Agent updates outdated if targetting a view?
When we deploy a new version of the agent or a config file to a view using the SMACC, it seems like the collection of targets gets populated when the push is published ... but it appears as if the collection is never re-evaluated and failed updates are not retried. Am I wrong? If this is the case, does it mean that we need to create a new push regularly, just to catch up with failed agent updates and new computers that get still a v5.3 agent through SCCM?
  • 13 answers
  • 73 views

  • Portal User

    Hi Samuel.   This is what I find regarding updates and views: An "Agent update" is a perpetual job, which means that it will continuously look for devices that matches the view criteria and update the views. It is designed to work dynamically. It might be that it's simply a matter of having to wait for the server to attach the targets. If the initial command to attach them from SMACC doesn't go through for some reason, then the server will check for new targets for a job every 8 hours by default.  The agent updates are initiated by the agent, not pushed from the server. An agent will send a request for new updates, and if the request matches the update view filter it will be presented with a new config file. So the server will not exclude the computer name after X attemtps, but the agent can fail to retrieve or install the new config continuously.  It could be worth checking the agent log of a failed update to see why it failed.  Hope that this helps!  / Martin 
    Expand Post

    • Gert-Jan Kosterman

      Hi Martin and Samual, we noticed some time ago the same behaviour as Samual does now. Systems added later and matching the view criteria are added to the view list but seem not to be updated with a new config file or agent version. I checked with support (CS0021921) and during a remote session we found out that creating a new Devices View and new Agent Update rule referring to the new Devices View did fix this. But this is a workaround which needs to repeated multiple times as long as older agents/configs get deployed (best to fix this of cause..). So a fix in the Inventory (SMACC) is still  needed and appreciated Regards, Gert-Jan
      Expand Post

      • SamuelBaughan

        Thanks Gert! So I'm not going nuts it is really happening. Thanks for providing to the support ticket reference! Sam

      • Portal User

        Thank you Gert-Jan, this was unknown to me and contradicts some internal documentation on the matter.  I am Very happy that you were able to correct me on this one.  The ticket CS0021921 is very much alive, and since the perpetual jobs should keep the views updated I hope that the outcome will be a patch of the inventory server. 

      • TL800271

        Hi all, I agree with Gert-Jan's answer. I like the idea of perpetual update jobs to keep agents updated. The biggest issue I have found with perpetual jobs is that once a machine is on the "Failed" list it is not re-tried. In order to get around this issue, I have been effectively re-creating the perpetual agent update jobs every month or so. Tom
        Expand Post

    • SamuelBaughan

      Hi Martin, Thanks for those details. I'm a bit confused now because I used to have an Agent update running for a couple of months to update all Windows servers to v6.0.2 and it had remained unchanged for a month or so (almost complete and only few failures) but I could see that plenty of servers were showing still in the SMACC with an old agent. I created a Device View just for those old agent instances, it contained 800+ servers. I configured a new update targeting this view. Most of them updated straight away successfully in less than a day: So somehow, my previous update was stuck and/or not updating. I'll monitor this new update and see if it behaves better Has anyone seen the same symptoms?
      Expand Post

      • Portal User

        Hi Sam, I apologize for the misleading reply, you should listen to Gert-Jan. :-)    I can see that the ticket he has (CS0021921) is active, so reference to that when you talk to support. I know that the aim for these updates are to be perpetual and the views reevaluated on a scheduled basis, but it sounds like that there might be a problem with that. 
        Expand Post

        • Gert-Jan Kosterman

          Hi Martin, anything new on ticket CS0021921 since Inventory 6.0.4 still has the same agent update issue of not updating systems added later by filter after the original agent update rule was initiated based on the device view. This is becoming very annoying since I each time have to create a new device view and a new agent update rule, which in fact are the same as the older ones, to get the newly added systems updated as well... Thanks, Gert-Jan.
          Expand Post

          • SamuelBaughan

            Hi Gert, Why do you re-create the view each time instead of re-using the same view in a new update push? A few months ago, I have created from scratch (not cloned) all my views used for pushes of updates but they still do not push to all selected clients. I was wondering if re-creating the view each time as you do solves this issue ...
            Expand Post
10 of 13

Related  Product Forums


                     → Flexera One



                      → Snow Atlas



                      → FlexNet Manager



                      → Snow License Manager



                       → App Broker


       Need help finding an answer?


        Ask a Question →


+1.800.374.4353
CONTACT SALES SUPPORT HUB FLEXERA REVENERA
© 2026 Flexera. All rights reserved.
Privacy policy Terms and conditions Revenera Community Help
Loading
Agent updates outdated if targetting a view?