Agents is missing repo version numbers for some packages
Posted: Fri Oct 06, 2023 7:58 pm
This is common and easy to resolve. The caching managers that are set across your client environments manage the versioning of "Approved Applications" list whether package is enabled or disabled. They are responsible for checking each package for updated versions and noting that data in the database. But they only know about packages set in the approved packages list.
The agent showing no version number for a given package means that that package is not in the Approved Packages list. By adding that package to the Approved packages list, enabled or disabled, will cause it to also get versioned from the available repos. By leaving package disabled you will not deploy that package to any other agent by mistake.
Allow time for next cycle to run versioning for versions to update.
The agent showing no version number for a given package means that that package is not in the Approved Packages list. By adding that package to the Approved packages list, enabled or disabled, will cause it to also get versioned from the available repos. By leaving package disabled you will not deploy that package to any other agent by mistake.
Allow time for next cycle to run versioning for versions to update.