Force MACOS Agent update

6 years ago

As far as I know, this is how we are doing ... it is basically (almost) the same as for a Windows client: Open a Terminal window (command prompt) on the Mac/Linux computer Enter this command: cd /opt/snow (and press enter) Next, enter the following command: sudo ./snowagent scan (and press enter) You might be prompted for a password, if so enter it Once the Agent completes scanning, some files should be created in this folder: /opt/snow/data The snowpack file should be in the above folder, it should be named like: result-xyz.snowpack Running the agent should trigger the update. Also, there would probably be the following switch available: sudo ./snowagent update I do not have any computer to test on, sorry. I then assume that running sudo ./snowagent send would send the snowpack file to the Inventory Server. We heard reports of instances when it was necessary to change the permission of the folder /opt/snow/data to everyone read & write.

Expand Post

Portal User
6 years ago
Thanks Sam - been trying to force it that way already. In the past it's worked fine.... none of my macs are picking up the new agent version from my inv server at the min....will keep trying... thanks!!! Adam
Expand Post
Portal User
6 years ago
cleared the update job and tried again, and what do you know it worked this time!! :-)
Expand Post
- SamuelBaughan
  6 years ago
  Happy it worked Out of curiosity, are you using a View based on the agent version or config name to push your updates? I am currently working on a ticket with Snow Support. This type of views does not update as we users would expect, the behaviour is not obvious, they actually update but there is a weird twist to that. I have been advised to use instead a criteria that does not change with the update. Example: If I need to update the agent, I will use the configuration name as a target filter If I need to update the config ... well, I have no solution yet for that The above is just a workaround as a test while looking for a final solution
  Expand Post
  - Portal User
    6 years ago
    Hi Sam For the macs I've just been using the config name. Interesting issue though. I've not seen that behaviour... Thanks again! Adam
    Expand Post
    SamuelBaughan
    6 years ago
    Support has explained that when an agent sends a heartbeat, it will check for and install updates if needed. But it will not update the Agent version and config name until the next full scan. In other words, the heartbeat does not update client info in the Snow Inventory. As a result, if the agent gets an update, an Inventory SMACC view based on Agent version will still show an old agent version although the agent has indeed been updated. This will be the case until the next day morning (likely) when the agent will run a full scan.
    Expand Post
    SamuelBaughan
    6 years ago
    Support has explained that when an agent sends a heartbeat, it will check for and install updates if needed. But it will not update the Agent version and config name until the next full scan. In other words, the heartbeat does not update client info in the Snow Inventory. As a result, if the agent gets an update, an Inventory SMACC view based on Agent version will still show an old agent version although the agent has indeed been updated. This will be the case until the next day morning (likely) when the agent will run a full scan.
    Expand Post
    Portal User
    6 years ago
    yes that's how I've always understood it works.... that's why agents appear in the inventory server but are greyed out until the agent sends the first inventory snowpack file.
    Expand Post

SamuelBaughan
6 years ago
As far as I know, this is how we are doing ... it is basically (almost) the same as for a Windows client: Open a Terminal window (command prompt) on the Mac/Linux computer Enter this command: cd /opt/snow (and press enter) Next, enter the following command: sudo ./snowagent scan (and press enter) You might be prompted for a password, if so enter it Once the Agent completes scanning, some files should be created in this folder: /opt/snow/data The snowpack file should be in the above folder, it should be named like: result-xyz.snowpack Running the agent should trigger the update. Also, there would probably be the following switch available: sudo ./snowagent update I do not have any computer to test on, sorry. I then assume that running sudo ./snowagent send would send the snowpack file to the Inventory Server. We heard reports of instances when it was necessary to change the permission of the folder /opt/snow/data to everyone read & write.
Expand Post
- Portal User
  6 years ago
  Thanks Sam - been trying to force it that way already. In the past it's worked fine.... none of my macs are picking up the new agent version from my inv server at the min....will keep trying... thanks!!! Adam
  Expand Post
- Portal User
  6 years ago
  cleared the update job and tried again, and what do you know it worked this time!! :-)
  Expand Post
  - SamuelBaughan
    6 years ago
    Happy it worked Out of curiosity, are you using a View based on the agent version or config name to push your updates? I am currently working on a ticket with Snow Support. This type of views does not update as we users would expect, the behaviour is not obvious, they actually update but there is a weird twist to that. I have been advised to use instead a criteria that does not change with the update. Example: If I need to update the agent, I will use the configuration name as a target filter If I need to update the config ... well, I have no solution yet for that The above is just a workaround as a test while looking for a final solution
    Expand Post
    Portal User
    6 years ago
    Hi Sam For the macs I've just been using the config name. Interesting issue though. I've not seen that behaviour... Thanks again! Adam
    Expand Post
    SamuelBaughan
    6 years ago
    Support has explained that when an agent sends a heartbeat, it will check for and install updates if needed. But it will not update the Agent version and config name until the next full scan. In other words, the heartbeat does not update client info in the Snow Inventory. As a result, if the agent gets an update, an Inventory SMACC view based on Agent version will still show an old agent version although the agent has indeed been updated. This will be the case until the next day morning (likely) when the agent will run a full scan.
    Expand Post
    SamuelBaughan
    6 years ago
    Support has explained that when an agent sends a heartbeat, it will check for and install updates if needed. But it will not update the Agent version and config name until the next full scan. In other words, the heartbeat does not update client info in the Snow Inventory. As a result, if the agent gets an update, an Inventory SMACC view based on Agent version will still show an old agent version although the agent has indeed been updated. This will be the case until the next day morning (likely) when the agent will run a full scan.
    Expand Post
    Portal User
    6 years ago
    yes that's how I've always understood it works.... that's why agents appear in the inventory server but are greyed out until the agent sends the first inventory snowpack file.
    Expand Post