
DanielV asked a question.
How to push an update to config for snowagent
Hi,
We have recently made changes to our config and need to push the changes to all the assets within the database. Can anyone point me in the right direction to do this as I really don't want to run another agent deployment and was hoping there was a way to push the new config out to the machines that I've already discovered/deployed.
Any help would be greatly appreciated.
Thanks in advance,
Dan
Hi,
How to push the snowagent.config file from SMAAC and what are the changes need to do?
Please help.
Best Regards,
Giri.
Hi Giri,
You are posting on a forum thread that is expressly answering that question...please take time to read the above answers, there is a link to the SMACC user guide, and I would also suggest taking Samuel's advice in creating a view to target a subset of devices to receive the update. It's less of a push, more of a pull. e.g. when an agent performs a heartbeat check-in, it determines whether or not it has any updates to take, if a config change has been made and the machine checking in matches the criteria (e.g. same config name, member of defined view) then it will take the update.
Hi Colin,
I have changed the config file as mentioned below in the master server:
C:\Program Files\Snow Software\Inventory\Agent
<Server>
<Endpoint>
<Address>https://Masterserver:443</Address>
</Endpoint>
<Endpoint>
<Address>http://Masterserver:80</Address>
</Endpoint>
</Server>
I have created a new view with a different config name will that work because as of now i haven't seen any agents. If it will not work how to change the config name as a previous one because in edit view there is no option to change.
Please check and let me know.
Best Regards,
Giri.
You should be able to update/add any files you like to an agent using SMACC. If you export the edited config file you have made, naming it snowagent.config...
Once complete, it should create an agent update job that will update the endpoints defined when they next 'check-in'.
As an aside, defining multiple endpoints as you have in your agent configuration has the following effect...