System Requirements

This Article Applies to:

Avast Business Hub
Avast Small Business Solutions

Business Hub

Browsers (latest versions recommended)

Google Chrome
Firefox
Safari
Microsoft Edge

Any other browsers may work (e.g. Chromium-based browsers should function without issues). However, we test in the above browsers specifically.

Local Clients

Windows

11 — x64
10 (Pro, Education, and Enterprise editions) — x64, x86
8/8.1 (all versions except RT and Starter Edition) — x64, x86
7 SP1 (requires KB3033929) — x64, x86
Server 2022, 2019, 2016, 2012 (any edition with latest service pack excluding Server Core) — x64
Server 2008 R2 (requires KB3033929) — x64
Small Business Server 2011 — x64

Supported applications

Exchange Server 2019, 2016, 2013, 2010 SP2 — x64
SharePoint Server 2019, 2016, 2013, 2010

macOS

We support ARM-based chips on macOS devices.

AV 15.7 and below: OS X 10.11 (El Capitan) and higher - preferably macOS 11.x (Big Sur) or higher, with at least 500MB of free disk space
AV 15.8 and above: macOS 10.13 (High Sierra) and higher, with at least 500MB of free disk space

Patch Management

Windows

11 — x64
10 (Pro, Education, and Enterprise editions) — x64, x86
8/8.1 (all versions except RT and Starter Edition) — x64, x86
7 SP1 (requires KB3033929) — x64, x86
Server 2022, 2019, 2016, 2012 (any edition with latest service pack excluding Server Core) — x64
Server 2008 R2 (requires KB3033929) — x64
Small Business Server 2011 — x64

Preparing your devices for Patch Management

Windows Update: we recommend you change Windows Update settings for your devices via the Windows Update Center and/or Group Policy. We have provided our recommended settings in Recommended Windows Update Configuration for Patch Management. The recommendations are the same for Avast and AVG consoles.

Software Updater: older versions of the Cloud Console and CloudCare provided a Software Updater component that performed some of the same functions as Patch Management. Ensure Software Updater is disabled/uninstalled for devices.

Local System account: patches are deployed under the remote machine's Local System account, so you need to ensure deployment will be allowed by that account.

Hard Drive space: a minimum of 2GB hard drive space should be free to store patches. If you are using a Master Agent/Local Update Agent, that device should have a minimum of 5GB hard drive space.

Servers vs Workstations: If you plan to use different Patch Management settings for your server devices and workstations, you should place your servers into a separate policy. If you only want to update the Windows Server operating system then you should exclude all 3rd party vendors on the Excludes list to make sure that only Windows updates are being provided. See Deploying Missing Patches for more details.

Remote Deployment Requirements (Windows 7/8.x/10/11)

Domain Administrator credentials for the deployment.
Network information about the devices you are deploying to - you need this information to locate the devices on your network.
A Master Agent (see Setting Up Master Agents).
Target devices need to be in the same network as the Scanning Agent and Update Agent.
No third-party antivirus software installed on target devices.
In a workgroup, disable remote UAC using the steps here. Ensure it is re-enabled after deployment.