Here are some important things to know before you begin setting up your Third-Party Update Policies.

Install Standard Apps

If you have a standard list of applications that are on all your end user's machines (e.g., Adobe Acrobat Reader DC, Firefox, Google Chrome, etc.), select “Install and Update.” 

Then, set their schedule to “Daily” and select a time for “Start Updating At” when end users are unlikely to be using their machines. In the example below, Syncro will check for updates to the standard applications selected above daily at midnight. 

Select “If offline, run at next boot" to ensure that the asset wont miss an update if it is offline or goes to sleep mode overnight.

Syncro will attempt the install on this schedule when the Third-Party Patch Policy is assigned to an asset. 

IMPORTANT: Only one Third-Party Patch Policy can be assigned to an asset at a time. (This differs from Windows Updates.) Whichever Third-Party Patch Policy is assigned to the policy folder level closest to the asset will override and replace any Third-Party Patch Policy above it.

Update if Present

If you're uncertain about which apps you want to install, choose the most common applications you know your end users have installed, and select “Update if Present.”

Chocolatey Package Considerations

Chocolatey Package install behavior can vary based on software vendors. Review Chocolatey’s package page for critical applications and always test before mass deploying to a large fleet.

If you're adding a new chocolatey package to the list, click View App to review the app in chocolatey: