New features for this release are described in the Release Notes for Websense Web Security and Websense Web Filter, version 7.1.1.
Select the Downloads tab, as shown below, and then select either
Websense Web Filter or
Websense Web Security, version
7.1.1.
For information about upgrading Websense software in specific integrated configurations, refer to the
Installation Guide Supplement for your integration product.
Before upgrading Websense software, make sure that the installation machine meets the system recommendations in the
Deployment Guide, including hardware specifications, operating system, browser, and database engine.
The Websense installer upgrades all Websense components detected on the installation machine, with the exception of the Remote Filtering Client and certain reporting components.
If Websense software is integrated with another product or device, all traffic is either unfiltered and permitted or completely blocked during the upgrade. The response depends on how your integration product is configured to respond when Websense filtering is unavailable.
When you upgrade the Stand-Alone Edition of Websense software, filtering stops when Websense services are stopped. Users have unfiltered access to the Internet until the Websense services are restarted.
Before upgrading to a new version of Websense Web security software, Websense, Inc., recommends performing a full system backup. This makes it possible to restore the current production system with minimum downtime, if necessary.
When you upgrade to v7.1.1, configuration settings for Active Directory in Websense Manager cannot be saved. Before upgrading, navigate to the
Settings >
Directory Services page and take note of your configuration. After the upgrade, this page needs to be reconfigured.
During the process of upgrading to or from v7.1.1, the parameter redirect_children, in the
squid.conf file located by default in the /etc/squid directory, is reset to default. Take note of your current setting for redirect_children because it needs to be reset after the upgrade.
If Remote Filtering Client is installed from the command line on a Windows machine, the REBOOT parameter, which defines whether the client computer is restarted automatically after installation or uninstallation, does not take effect. A manual restart of the client machine after installation or uninstallation of Remote Filtering Client works around this issue.
If you are running an upgrade on Linux, make sure that the hosts file includes the host name for the machine on which you are running the upgrade. This file is located in the
/etc directory, by default. Add a host name for the machine, if one is not included.
The installer detects the integration-specific components, such as plug-ins and filters, and upgrades them. To upgrade the filtering plug-in, run the installer on the machine running the integration product.
If you are changing your integrated firewall, proxy server, caching application, or network appliance, modify that product before upgrading Websense software. See the
Installation Guide or supplement for that integration product and your current version of Websense software.
To ensure the success of the upgrade, manually stop and start all the Websense services before beginning the upgrade. See
Stopping or starting Websense services in the
Installation Guide for instructions.
When upgrading a Filtering Service that is installed on a different machine from Websense Manager, you must upgrade Filtering Service in the same locale environment (language and character set) as Websense Manager.
The standard Websense installation program is also used for upgrades. After it starts, the installer detects that an older version of the product is installed. The installer also detects which Websense components are installed and need to be upgraded, and checks the version of the database engine to ensure it is compatible with the new version of the Websense software.
|
|
|
|
The Installation Guide Supplement for your integration product contains additional information needed to upgrade and configure Websense software to run with the integration product. Refer to the supplement before running the following procedures.
|
|
If you are upgrading or installing Log Server (Windows only), and will use a Windows trusted connection to communicate with the database engine, your logon user account must also be a trusted account with local administration privileges on the database machine.
If a full backup is not feasible, make backup copies of the websense.ini,
eimserver.ini, and
config.xml files, and move them to a different location. These files are located in the Websense
bin directory (C:\Program Files\Websense\bin or /opt/Websense/bin, by default).
|
a.
|
Check the etc/hosts file. If there is no host name for the machine, add one.
|
The installer detects the Websense components from an earlier version and asks how you want to proceed. You can upgrade the current system or exit the installer.
|
8.
|
Select Upgrade, and then click Next.
|
|
|
Do not install Policy Broker on multiple machines.
|
|
|
No, Policy Broker is installed elsewhere—select this option if Policy Broker is already installed on another machine. Then, enter the Policy Broker IP address. The default Configuration port is provided and should not be changed.
|
|
12.
|
Select a Websense Filtering Feedback option, and then click Next.
|
Selecting Yes allows Websense, Inc., to gather information about the use of Websense-defined protocols. This information is used to enhance protocol filtering.
The installer compares the system requirements for the upgrade with the machine's resources. These requirements are listed in the
Deployment Guide.
See the Known Issues article for a list of configuration settings that may need to be customized for your network after the upgrade.
