Chocolatey.org has strict rate-limiting policies, which means you may start receiving that dreaded “429 error” in the middle of deploying or upgrade packages. This can cause a lot of issues with delivering packages consistently to any client location that has more than a few agents using the network.
By using UNC file shares at a given location, the selected Cache Manager will sync to this share with the Approved Applications downloaded from the chocolatey public repository. It will maintain this cache automatically keeping its contents current with the public repository.
Each client location will need to be configured where you will want UNC caching to take place.
In the Automate Control Center, expand a client to view its locations. Double click a location to open the location console. Under the General Tab, Scripts and Variables sub section, fill in the network share information, the username and password to use with share access and save the console.
- LocationCacheSettings.PNG (27.99 KiB) Viewed 5132 times
Now that you have your location network share established you can define the Caching Manager that will be responsible for populating and keeping cache up to date.
Open the client console and select the Chocolatey for Automate tab, Find an expectable agent to act as Caching Manager for the location you added the network share to. select agent and right click to reveal menu. Select to set agent as caching manager. If VPN's are in use and an agent can access remotely the network share then it should also be able to act as caching manager if needed. Using a local agent is always better on bandwidth.
- cachemanager.png (42.87 KiB) Viewed 5132 times
Lastly you need to tell the agents for a given location that UNC will be used. To do this select any agent that is in the location you want to use UNC. Right click agent to expose menu and select to set location to use UNC cache. This will cause all agents to have Use UNC flag set which will cause agents to temporarily join the CFA Manage UNC Sources sub group. This will cause agent to update its sources locally to set the network share as a priority 1 source. The fall back source will be the public repository.