How the Chocolatey Workflow happens to an agent

[Cubert]

As of 3.6 you are working with groups and searches. These groups auto join agents that have met the requirements set down by the EDFs of each agent under management. Group management should be easy to troubleshoot, here is what to look for.

So this is the typical path an agent will take when a client is enabled.

• You select to enable workstations - This sets the EDF Chocolatey Approved to checked for all workstations

• Auto Join sees Chocolatey Approved flag and joins agent to "C4A Deploy Chocolatey", This group invokes a script to install chocolatey to agents every couple hours. Script sets "Chocolatey Installed" EDF when Chocolatey is successfully installed to agent.

• When agent has both Approved and Installed flags set, it will leave "Deploy Chocolatey" and auto join the master group Chocolatey For Automate, This group is responsible for scanning agents for installed packages.

• All agents in master group will get update command run (daily) by default. You can edit client schedule to force weekly or monthly updates instead.

• At any time you can add either a UNC cache share or a different Source like a Chocolatey proxy and set agents to use them. This will cause agents to auto join C4A Manage Sources or Manage UNC groups. This will cause group to update agent source configurations and sets EDF that settings are completed causing agent to leave group afterwards.

• If you want agents to auto install approved packages as part of the service then selecting auto install application in the client console will cause a EDF flag to be set. This causes agent to auto join the Install software packages group where it over a period of 1 day will have agent install software packages approved in App approval list.

Each of the operations are independent but all require that Chocolatey Approved, Chocolatey installed flags are set. Also there is a expected time frame when working with groups.

• Auto Joins happen hourly, that means it takes up to an hour for agent to join a group when flags are set and another hour to leave group once flags are updated.

• Scan Group is set to once daily, if an agent joins this group it may take 24 hours for scan to happen on newly joined agents.

• Auto install group runs 1 time daily, Applications may take 24 hours to show in lists

• Source management is set to every 2 hours as agents should come and go with one script run.

• UNC Cache Management runs once daily

These are all soft settings for script execution in each group. You can freely modify these time schedules to reflect your environment as needed. You would like scans more often? Modify the master groups "Chocolatey For Automate" script run to twice daily.

At any time you want to know where in the process an agent is, have a look at its EDFs under Chocolatey tab to see what groups it should currently be joined to and what activities that group preforms.

[Cubert]

Screenshot 2023-10-10 103333.png (64.23 KiB) Viewed 1230 times

Here is an example agent's EDFs for Chocolatey For Automate.

From this view you can determine that the agent is enabled, has chocolatey installed, was set to auto install applications and completed installs.

We have the Chocolatey version currently installed and the dates of last scan and last update.

This agent should have package data displaying in client view. And below the images shows packages under management

Screenshot 2023-10-10 103937.png (51.07 KiB) Viewed 1230 times