Before you begin
| Applies to: |
- Forcepoint Web Security, v8.5.x
- Forcepoint URL Filtering, v8.5.x
|
When you upgrade your web protection solutions, the installer or appliance patch automatically upgrades all components on a given machine in the correct order.
As a result, if you have a main server or appliance hosting most of your web protection components (including Policy Broker), upgrade that machine first, then use the list below to
determine the upgrade order for any additional servers or appliances.
If your components are widely distributed, however, ensure that they are upgraded in the correct order, as follows:
Steps
- Policy Broker (primary or standalone)
If you are using Forcepoint appliances, Policy Broker runs on the
full policy source appliance or server.
Regardless of the other components running on the machine,
always upgrade the Policy Broker machine first. The other components on the machine are upgraded in the correct order.
-
Replica Policy Brokers
Upgrade replica Policy Brokers after the primary has been upgraded and before attempting to upgrade any Policy Servers associated with them. If Policy Server is installed on the
same machine, it will be upgraded at the same time.
-
Policy Server
Runs on all user directory and filtering appliances, and may run on other Windows or Linux servers.
-
User Service, Filtering Service, and Directory Agent
This includes all filtering only appliances, and may include other Windows or Linux servers.
-
Log Server and Sync Service
Make sure that all Log Database jobs are stopped before starting the Log Server upgrade. See Preparing the Log Database for upgrade.
-
Forcepoint Security Manager
-
Content Gateway, Network Agent
-
Transparent identification agents, Remote Filtering Server, filtering plug-in (Citrix XenApp or Microsoft Forefront TMG)
Next steps
Once all server components have been upgraded, upgrade client components (the logon application, Remote Filtering Client, Forcepoint Web Security Endpoint) in any order. See: