Customizing the client installation package

Deploying the Remote Filter Module | Forcepoint URL Filtering | v8.4.x, v8.5.x

Before deploying Remote Filtering Client to users' machines, create one or more installation packages. An installation package includes configuration information to specify how the client connects to one or more Remote Filtering Server instances, whether Internet activity is logged for the client, and so on.

You must create at least one customized installation package to successfully deploy Remote Filtering Client, and can create multiple installation packages.

To create an installation package:

Navigate to the folder containing the configuration tool (by default, Websense\Web Security\DTFAgent\RemoteFilteringAgentPack\) and double-click WebsenseEndpointPacakageBuilder.

The Endpoint Package Builder opens.

Mark the Forcepoint Web Security Endpoint check box, then select Remote Filtering Client. Also select a language from the drop-down list at the bottom of the page. This is the language used to display messages to the end user (if any such messages are enabled).

When you are finished, click Next.

Select one or more operating systems (Windows 32-bit, Windows 64-bit, or Mac OS X) for which to create an installation package, then enter and confirm the anti-tampering Password that administrators may use to modify or uninstall the Remote Filtering Client. Also specify whether or not to Protect the installation directory from modification or deletion.

When you are finished, click Next.

If you selected one or more Windows operating systems, specify the installation path for Remote Filtering Client on end user machines.

Select Use the default location to install Remote Filtering Client in the directory displayed in the tool.

Select Use this location to enter a custom installation path.

If you selected only Mac OS X as your client operating system, this screen is not displayed. On Mac OS X machines, Remote Filtering Client is installed in the Applications directory.

On the Internal Connections screen, enter the internal IP address or hostname and internal Port of each Remote Filtering Server to which this client will connect. Use the > button to move the information to the selected list. When you are finished, click Next.

Remote Filtering Client sends its heartbeat to these IP addresses and ports to determine whether or not it is inside the network.

If you have multiple Remote Filtering Server instances, Remote Filtering Client rotates through the list in order until a functioning server is located.

Remote Filtering Server has a 2-minute inactivity timeout period. If the client connects, and then does not send an Internet request in the timeout period, the server drops the connection. When the next request is made, Remote Filtering Client goes through its list to connect again. This protects server performance by reducing the number of unused connections that might otherwise accumulate.

On the External Connections screen, enter the external IP address or hostname and Port of each Remote Filtering Server listed on the previous screen. Use the > button to move the information to the selected list.

Each server must be identified by an externally visible IP address or fully qualified domain name (FQDN).


	Important Be sure to use the same format (IP address or FQDN) that you used when installing Remote Filtering Server.

When Remote Filtering Client is outside the network, filtering requests are sent to Remote Filtering Server via the specified IP address or FQDN and port.

Indicate whether or not to Log user Internet activity seen by Remote Filtering Client instances installed using this customized installation package, and then click Next.

Use the Trusted Sites list to enter up to 4 URLs, IP addresses, or regular expressions for sites that Remote Filtering Client users can access directly, without being filtered or logged. Click Add to enter a URL, IP address, or regular expression.

When you are finished, click Next.

Indicate whether or not to Notify users when HTTPS or FTP traffic is blocked, then, if notification is enabled, specify how long (in seconds) the message is displayed.

10.

Enter and confirm the Pass phrase used for communication with Remote Filtering Server. This must match the pass phrase created when Remote Filtering Server was installed.

When you are finished, click Next.

11.

Specify a Save location for the new installation package. Enter a valid directory path or click Browse to navigate to the path.

12.

Click Finish.

The new installation package can now be used to deploy Remote Filtering Client to users' machines.