Application Settings

The Application Settings tab sets general options for the entire module.

Actions

Note: Display 3rd Party Vulnerabilities option is removed. With this change the behavior of the module corresponds to the Hybrid value of that option, it means 3rd-Party Software Patches will only be included in scans and deployments on agents with Third-Party Support Enabled. User can enable third-party support on agents in Software Management > Machines Page.

Edit
- Reboot Action Email - Applies only if Do not reboot after update, send email is selected in a Deployment profile. Specifies the Subject and Body format of email notifications that a machine needs to be rebooted after a patch.
  The following variables can be included in your formatted email alerts and in procedures.

Within an Email	Description
<id>	machine ID

Compliance - Compliance checking is reported on the Dashboard page and in Info Center > Report Parts for Software Management.
Compliance Check - Specifies how often machines are checked for compliance, based on Kaseya Server time.
Scan Grace Period - Specifies the grace period included in compliance checking for scanning. A machine is out of compliance if—at the time compliance is checked—the last actual scan was later than the last scheduled scan plus the grace period.
Deploy Grace Period - Specifies the grace period included in compliance checking for deployment. A machine is out of compliance if—at the time compliance is checked—the last actual deployment was later than the last scheduled deployment plus the grace period.
Patch Tolerance - Specifies a percentage ratio of deployed patches to approved patches. A machine is out of compliance if deployed patches are less than the specified percentage of approved patches.

Note: 3rd-party patches are only included in compliance calculations if 3rd-party patching has been enabled for a machine.

Vulnerability Definition - Specifies whether to include or exclude suppressed patches. This option reflects on the entire module experience. This does not reflect in Info Center Software Management Report Parts.
Migration -
- Prevent an agent from running both Patch Management and Software Management at the same time - If checked, Software Management will not run Scan Now on an agent if that agent is configured to use any of these Patch Management features:
  - Patch Management Policy
  - Scan Schedule
  - Automatic Update Schedule
  - Machine Update Schedule
  - Patch Update Schedule
Settings -
- Private Profiles - If checked, profiles are only visible if the profile was created by you or if the profile is assigned to a machine assigned to the scope you are using. If Profiles are public, user will have visibility to any endpoints which have Software Management profiles assigned. Profiles are public by default. Applies to the following types of profiles:
  - Scan and analysis
  - Override
  - 3rd Party Software
  - Deployment
  - Alerting
- Display Third-Party Vulnerabilities - This historical function has been elevated to include the following options and behavior as a result:
  - Hide All - If selected, Third-Party Patches will not be included in scans and deployments.
  - Hybrid (Default Option) - Recommend option, If selected, Third-Party Patches will only be included in scans and deployments on agents with Third-Party Support Enabled. User can enable third-party support on agents in Software Management > Machines Page. For all existing tenants Display Third-Party Vulnerabilities is set to Hybrid. This option is enabled for all tenants.
  - Show All - If selected, this latest function will list all third party patches available for deployment on endpoint(s) without the need to enable or be licensed for third party updates.
    Technical Preview Note: This option is currently only supported for new native Kaseya engines which are currently in technical preview. It will be available for General Availability upon the new Software Management engine release.
- Deploy Windows 3rd-party installers from SMPM Catalog - If checked, Windows 3rd-party installers will be deployed from SMPM Catalog.
Note: Enable Native Kaseya Engines is removed from Application Settings.

Technical Preview Note: This option is currently only supported for new native Kaseya engines which are currently in technical preview. It will be available for General Availability upon the new Software Management engine release.