PROXIMANOVA-LIGHT.OTF PROXIMANOVA-LIGHTIT.OTF PROXIMANOVA-EXTRABLD.OTF PROXIMANOVA-BOLD.OTFPROXIMANOVA-BLACK.OTF
Get this font in here!
Hub vs. CloudCare Patch Management
This Article Applies to:
- Business Hub
- Avast Business CloudCare
Patch Management works differently in the Business Hub as compared to Avast Business CloudCare. Keep these differences in mind when you upgrade.
Configuring Exclusions
In the Hub, you'll be able to create exclusions for specific vendors, products, and patch severities. Excluded patches will be hidden from your patch list and will not be deployed in automatic installations.
When moving from CloudCare, all auto-approvals will be cleared so that you can configure patching exclusions instead. You can still manually deploy, schedule, and ignore patches.
For more information on patch exclusions in the Hub, please see Configuring Patch Management Exclusions.
Approving Patches
You no longer need to approve patches and keep track of what is approved or not. You can configure your policy, or visit the Patches page and manually install, ignore, and exclude patches. Instead of approving specific patches, you can exclude unwanted patches in the Hub.
Patches you approved in CloudCare will be reverted to Missing status when migrated to the Hub.
For more information on automatic vs. manual patching in the Hub, please see Automatic vs. Ad Hoc Patching.
Scheduling Deployment
Due to the changes in patching, you will need to configure exclusions and automatic patch deployment, if desired. No automatic patching will occur via the Hub until you set a new deployment schedule.
When you migrate to the Hub, the patch deployment schedule in policies is set to “Do not deploy”.
For more information on patch deployment in the Hub, please see Deploying Missing Patches.
Other Articles In This Section:
Patch Management System Requirements
Recommended Windows Update Configuration for Patch Management
Related Articles:
Scanning Devices for Missing Patches