Hello. I was wondering a couple things about how the Chocolatey II update process works.
I have turned on "Exclude client from installs" both at a global and client level. As far as I am aware, this should mean that no software should automatically be installed.
I have "Exclude client from updates" and "exclude client servers from" turned off.
Those are pretty much all the options I have, apart from the box to "Exclude" the approved application.
From my understanding, with this setup, all of the applications should automatically "update" but not install correct?
I am running version 2.0.0 currently.
One of the reasons I ask is that if I look at a computer there is the option to "Update" an "uninstall". When I clicked "update" for one of the applications as a test, it kicked off chocolatey and upgraded the application.
This seems to suggest the application wasn't auto-updating (otherwise it wouldn't have updated if I clicked update since it would already be up to date, correct?)
Otherwise, let me know if that is incorrect.
Also is there some form of logging to verify things are actually updating?
Thanks!
Updates and Exclusions?
Re: Updates and Exclusions?
I would first watch our video on our YouTube Channel https://www.youtube.com/channel/UCpqAWz ... BQf8D3Mjaw
This should give you a fairly good working idea of how Chocolatey works and how it deploys to your networks. It also describes some fundamental processes that have to happen for you to get updates functional.
Chocolatey can not update directly without a install. If you have adobe reader 1.2.3 installed on a system, How does chocolatey know (1) it is there, (2) what "package" from what repo do you want to apply to manage that software package and then (3) What comes first Chocolatey framework or app management?
Let me explain:
Lets start with number (3) first. For Chocolatey to manage applications, Chocolatey must install it's self before it can be used to install or update applications.
(2) If you do not "enable" a package for the end system Chocolatey might see Adobe or Java but will not be able to associate a package on a repo your using to use as the updates moving forward. No association no updates..
(1) Once you have Chocolatey installed and packages enabled it will try and install package to make sure it is at the level Choco package demands. Moving forward from there it will maintain it (updates) Installing a package like Java where Java is already deployed does not hurt or take away from system. This would be just as if a new Java version came out.. It installs the new version over the old in the same way as reinstalling apps through Chocolatey would do.
This should give you a fairly good working idea of how Chocolatey works and how it deploys to your networks. It also describes some fundamental processes that have to happen for you to get updates functional.
Chocolatey can not update directly without a install. If you have adobe reader 1.2.3 installed on a system, How does chocolatey know (1) it is there, (2) what "package" from what repo do you want to apply to manage that software package and then (3) What comes first Chocolatey framework or app management?
Let me explain:
Lets start with number (3) first. For Chocolatey to manage applications, Chocolatey must install it's self before it can be used to install or update applications.
(2) If you do not "enable" a package for the end system Chocolatey might see Adobe or Java but will not be able to associate a package on a repo your using to use as the updates moving forward. No association no updates..
(1) Once you have Chocolatey installed and packages enabled it will try and install package to make sure it is at the level Choco package demands. Moving forward from there it will maintain it (updates) Installing a package like Java where Java is already deployed does not hurt or take away from system. This would be just as if a new Java version came out.. It installs the new version over the old in the same way as reinstalling apps through Chocolatey would do.