A package profile, or meta-package, comprises a set of one or more packages, including their dependencies and conflicts (generally called constraints), that you can manage as a group. Package profiles specify sets of packages that associated systems should always get, or never get. You can associate zero or more computers with each package profile via tags to install packages on those computers. You can also associate a package profile with an access group, which limits its use to only computers within the specified access group. You can manage package profiles from the Profiles tab in your organisation’s home page.
@yanisa-hs I created a package profile and deployed to a test group - worked well. So well that I created a new tag and a new package profile and deployed to all machines. However, machines from the test group display “non-compliant” after the change. The machines in question are 100% compliant and they were previously until the tag was updated and applied by a new package profile. Any suggestions for remediation?
We are also struggling to get the package profiles stable, the reports of compliant machines swing wildly - from 20 to 100 and back to 20 for example in a matter of days.
The meta package is in the client machine.
It might be related to the package reporting that behaves similarly, relating to numbers - but we are not sure which one is the origin of the problem.
Been asking around and researching, troubleshooting, no resolution as of yet 