Prepare Web Filter & Security for upgrade

On the new appliance, in the Appliance Manager perform a Full Appliance Configuration backup and save it to an off-appliance location.

1. Stop all discovery and fingerprinting tasks.
2. Route all traffic away from the system.
3. Ensure that your supplemental fingerprint repositories are fully synchronized with the primary repository.
4. Make sure all settings are deployed successfully. Log onto the Data Security manager. If the Deploy button is highlighted, click it.
5. If your organization was supplied with custom file types, change the name of the following files in the policies_store\custom_policies\config_files folder on the management server; otherwise they will be overwritten during upgrade.
   1. Change extractor.config.xml to custom_extractor.config.xml.
   2. Change extractorlinux.config.xml to custom_extractorlinux.config.xml.

      The filenames are case-sensitive.

6. If custom policies were provided, submit a request for updated versions before proceeding.

1. Back up your reporting databases.

   Refer to Microsoft documentation for instructions. The databases are named wslogdb70 (the catalog database), wslogdb70_n (standard logging partition databases), and wslogdb70_amt_1 (threats partition database).

2. On the Log Server machine, use the Windows Services tool to stop Websense Log Server.

Stop the Log Database jobs using these steps:

1. If you have a full version of Microsoft SQL Server (not Express), stop all database jobs as follows. (See below for steps to stop SQL Express jobs.)
   1. Log in to the Microsoft SQL Server Management Studio and expand SQL Server Agent > Jobs (in Object Explorer).
   2. To disable all currently active SQL Server Agent jobs, right-click each of the following jobs and select Disable:

      Websense_ETL_Job_wslogdb70
      Websense_AMT_ETL_wslogdb70
      Websense_IBT_DRIVER_wslogdb70
      Websense_Trend_DRIVER_wslogdb70
      Websense_Maintenance_Job_wslogdb70

      Disabling the jobs prevents them from executing at the next scheduled time, but does not stop them if a job is in process.

      Make sure all jobs have completed any current operation before proceeding with upgrade.

   3. After upgrade, verify that the jobs have been enabled. Enable any that were not automatically enabled by the upgrade process. Normal database operations will then resume.

2. If you have SQL Server Express, stop all database jobs as follows:
   1. Log in to the Microsoft SQL Server Management Studio.
   2. Expand the Databases tree to locate the catalog database (wslogdb70, by default), then expand the catalog database node.
   3. Expand Service Broker > Queues.
   4. Right click dbo.wse_scheduled_job_queue and select Disable Queue.
   5. The upgrade process will re-enable the job queue. After upgrade, verify that the Queue has been enabled.

      Enable it, if necessary, by repeating the process, this time ultimately selecting Enable Queue to resume normal database operations.

   When Log Server is upgraded, the upgrade process first checks the Log Database version and updates the database, if necessary. If you have multiple Log Servers, the database update occurs with the first Log Server upgrade. The database update, including the need to stop the database jobs, is not repeated when additional Log Server instances are upgraded.

1. Launch the Windows Services tool.
2. Scroll down to find Websense Log Server, then check the Log On As column to find the account to use.
   Important: As a result of a change made to avoid a potential vulnerability when a presentation report is included as a link in an email, report links in emails that exist prior to upgrading to v8.3 or later will no longer work.