Re: choco.exe missing
Posted: Wed Jun 09, 2021 5:46 pm
We have released build 3.0.0.43 today which does several things including possible fixes for items in this post. I will be posting this in several of the C4A posts currently active as this update has several fixes in it.
We have added in a new control variable to assist in setting the Excessive Running Commands test when running automation to do framework installs, App installs and App update. To view the properties for C4A run the following SQL
Should Produce the following:
The setting is called EXCESSIVECMDS with a default value of 3. To adjust value run the following SQL command
This will set the EXCESSIVECMDS value to 5. You can set it any where from 0 to 99 but 99 would be really excessive!
You will now see the Automation log on the Automate server reporting when skipping agents who exceed the excessive commands setting.
We have also added to the Automation Script functions for framework installs that if we are in a install event to remove any old Chocolatey directory before install attempt. Should help reduce install failures do to remints of elder installs of chocolatey.
We have added to the Automation Script functions for App installs and App Updates a loop sleeper which slows down the install and or updates of multiple applications to help in preventing public repo lockout for excessive connections from location. We added a control in the Global Manager to set the number of seconds the script is to sleep between every (5) application installs or updates. This control changes the LOOPSLEEPCOUNT property value in the "plugin_p4l_chocolatey_properties" table.
This is the first half of major update set to improve application delivery when on the public repo. Anyone using private repos or using Chocolatey licensing will not be affected by public repo lockouts.
The next update will be out soon and will be adding a new scheduling function and staggering of Automation across agents per Client which will further assist in preventing public repo lockout by staggering installs and updates across the agents of a client so not everyone attempts access to public repo at the same time. This will have a control setting to adjust as needed. The update will also allow for weekly and monthly updates instead of daily install and updates as an optional setting per client. The default Automation will still be daily.
We have added in a new control variable to assist in setting the Excessive Running Commands test when running automation to do framework installs, App installs and App update. To view the properties for C4A run the following SQL
Code: Select all
SELECT * FROM plugin_p4l_chocolatey_properties;- Capture.PNG (6.3 KiB) Viewed 3955 times
Code: Select all
REPLACE INTO plugin_p4l_chocolatey_properties(`Name`,`Value`) Values('EXCESSIVECMDS','5');You will now see the Automation log on the Automate server reporting when skipping agents who exceed the excessive commands setting.
Skipping applications installs for agentID [JTI-W10PC02] To many commands currently running [5]:::
We have also added to the Automation Script functions for framework installs that if we are in a install event to remove any old Chocolatey directory before install attempt. Should help reduce install failures do to remints of elder installs of chocolatey.
We have added to the Automation Script functions for App installs and App Updates a loop sleeper which slows down the install and or updates of multiple applications to help in preventing public repo lockout for excessive connections from location. We added a control in the Global Manager to set the number of seconds the script is to sleep between every (5) application installs or updates. This control changes the LOOPSLEEPCOUNT property value in the "plugin_p4l_chocolatey_properties" table.
This is the first half of major update set to improve application delivery when on the public repo. Anyone using private repos or using Chocolatey licensing will not be affected by public repo lockouts.
The next update will be out soon and will be adding a new scheduling function and staggering of Automation across agents per Client which will further assist in preventing public repo lockout by staggering installs and updates across the agents of a client so not everyone attempts access to public repo at the same time. This will have a control setting to adjust as needed. The update will also allow for weekly and monthly updates instead of daily install and updates as an optional setting per client. The default Automation will still be daily.