Loading
search-img

DavidH asked a question.

October 12, 2018 at 7:00 AM
Mac agent update to v6
Hello, Has anybody else tried pushing out the v6 Mac Agent?   We're in the process of doing that.  In the Inventory SMACC the computers show as successful: ...however not one of those machines reports in with the v6 agent.  They all still show as "Snow Agent - OS X 5.1.0" . Has anybody else managed to deploy v6 of the Mac Agent? Regards, David
  • 31 answers
  • 90 views

  • DirkNijs

    Hi David, Samuel, We installed manually MAC agent v6.0.1 to few machines. This cause a memory leak due to the xMetering. do you have that problem too? I raised a case at Snow, but so far no reaction yet. I rolled back to v6.0.0 but no solution. As you mentioned, as from v6, the xMetering x64 has been introduced... this make sense... it seems not yet stable... Has somebody else that memory leak also? (See first line in image below)
    Expand Post

    • Geoffrey Macquet (Flexera Software)

      Hi ‌, Sorry for coming back late - while checking your ticket i see that it has been linked to a registered problem record PRB0042292. Thank you for accepting the build tests, if you have not been contacted by the support engineer regarding these, you might get shortly. On a side note, our sustainment engineers added the thought that this might not be a bug, but rather a misinterpretation of how memory is presented in Mac OS. Basically, looking at virtual memory is not a very good indication of how much memory a process is actually "locking down". As example, a dev tested this and started xMetering2 on their own Mac, the virtual memory used shows > 4GB - but the real memory size is just 7MB. This might be regarding the way how currently addressable memory for the process is being represented, instead the actually used memory. Thanks, Geoffrey Macquet Customer Success Manager EMEA
      Expand Post

    • DavidH

      Thanks.  I have not seen that memory leak problem yet, but it's good to know about it. Where we have had problems I thought that v6.0.0 was the culprit. I thought that some of the machines which received v6.0.0 of the Mac agent were just broken and would need manual effort to install a newer version. Please keep us updated if you learn anything.  I will investigate more when I have time. Regards, David
      Expand Post

      • Gert-Jan Kosterman

        Hi David, I've got a question related to the MacOS agent: we want to deploy it with means of Microsoft Intune but do not get it to work? Do you deploy via Intune too of do you use another deployment mechanism? If it's Intune I would like to get in contact with you and hopefully learn how to deploy the Snow MacOS agent using Intune regards, Gert-Jan.
        Expand Post

  • MacGeno

    I have the same question, I also see when I do the deployment 6.0.1 And it should be 6.0.2 64bit  second question , can you use the inventory server to deploy an update of the snow agent one it has been installed on the Mac ?

    • Community Manager (Flexera Software)

      Hi, Yes, you can use Inventory Server to create Agent Updates to distribute new versions of the agents to already reporting Agents. If you have problems with updates, please contact our Support. Best regards Robin

  • SamuelBaughan

    Hi David, Could it be that you still have your previous Agent deployment "In Progress" in your Inventory Server? So maybe the new deployment pushes v6.0. But the old deployment, depending on how it is configured, might be pushing back v5.1 It is worth checking.

    • DavidH

      Thanks , I did think of that, but I think you have to specifically tick a box to allow agent downgrades.  However, I will double check it just in case.  I suppose the other possibility is that there is a bug and the downgrade is still happening even though the box has not been ticked...  It's worth double-checking.

      • SamuelBaughan

        Yes, I think that the push of agent updates is not 100% baked since sometimes, a published push does not start (I had the experience twice recently). I remember that a year ago, when I started with pushes of agent updates, I found out that playing with that tickbox would trigger the update, otherwise, it would not progress. In your case, it seems to be progressing but the reports say otherwise. It might be good giving that tickbox a go. Unfortunately, it is not clear how those pushes work: If you pause an old push, does the new push re-try to update the agents? Is the update based on a once-only check of the client or is it a continuous (daily?) check? For example, if I manually install an old agent (5.3) on an inventoried computer that had already received the new agent pushed (6.0), will the client receive the update again? Maybe a Snow specialist could shed some light.
        Expand Post

        • Community Manager (Flexera Software)

          Hi, By creating an agent update package, you make an update available for the targeted computers. Once the agent asks the server for updates (http.poll_interval) and there are updates available, it will download and apply them. The manually installed 5.3 will be updated to 6.0 again if you have a perpetual 6.0-update available for all computers. Best regards Robin
          Expand Post
10 of 31

+1.800.374.4353
CONTACT SALES SUPPORT HUB FLEXERA REVENERA
© 2026 Flexera. All rights reserved.
Privacy policy Terms and conditions Revenera Community Help
Loading
Mac agent update to v6