Open the BlackBerry Protect Connectivity Node installation file (.exe) that you downloaded from the management console.
If a Windows message appears and requests permission to make changes to the computer, click Yes.
Choose your language. Click OK.
Click Next.
Select your country or region. Read and accept the license agreement. Click Next.
The installation program verifies that your computer meets the installation requirements. Click Next.
To change the installation file path, click ... and navigate to the file path that you want to use. If you receive a message asking you to create the installation and logs folder locations, click Yes. Click Next.
In the Service account dialog box, type the password for the service account. Click Install.
When the installation completes, click Next.
The address of the BlackBerry Protect Connectivity Node console is displayed (http:/localhost:8088). Click the link and save the site in your browser.
Select your language. Click Next.
When you activate the BlackBerry Protect Connectivity Node, it sends data over port 443 (HTTPS) to the Protect Backend (for example na.bbsecure.com or eu.bbsecure.com). After it is activated, the BlackBerry Protect Connectivity Node uses port 3101 (TCP) for all other outbound connections through the Protect Backend. Do any of the following:
If you want to use a proxy setting other than the default port 443 to connect to the Protect Backend (<region>.bbsecure.com) to activate the BlackBerry Protect Connectivity Node, click the "here" link to configure the proxy settings and enter the information for the enrollment proxy. This link is only available on the "Name your BlackBerry Protect Connectivity Node" screen. If you do not configure the proxy settings from this screen and click Next, you can configure the proxy settings from the top right corner of the screen by clicking Settings > Proxy before it is activated.
Note: The proxy must be able to access port 443 to the Protect Backend. You cannot change the enrollment proxy setting after you activate the BlackBerry Connectivity Node.
In the Friendly name field, type a name for the BlackBerry Protect Connectivity Node. Click Next.
Click Browse. Select the activation file that you downloaded from the management console.
Click Activate.
If you want to add an BlackBerry Protect Connectivity Node instance to an existing server group when you activate it, your organization's firewall must allow connections from that server over port 443 through the Protect Backend (for example na.bbsecure.com or eu.bbsecure.com) to activate the BlackBerry Protect Connectivity Node and to the same bbsecure.com region as the main BlackBerry Protect Connectivity Node instance.
Click and select the type of company directory that you want to configure.
Link your directory to the BlackBerry Protect Connectivity Node by following the appropriate task:
To install a second BlackBerry Protect Connectivity Node instance for redundancy, download another set of installation and activation files and repeat this task on a different computer. This should be done after the first instance has been activated.
You can configure one or more directory connections, but if you have multiple BlackBerry Protect Connectivity Nodes, all of the directory connections must be configured identically. If one directory connection is missing or incorrectly configured, that BlackBerry Protect Connectivity Node will appear as disabled in the management console. You can make this task easier by copying directory connection configurations from one BlackBerry Protect Connectivity Node to another.
To change the directory settings that you configured, in the BlackBerry Protect Connectivity Node console (http:/localhost:8088), click General settings > Company directory. Click for the directory connection.
You can remove directory connections from an BlackBerry Protect Connectivity Node as long as you have no users or groups associated with it. If you remove a connection from an BlackBerry Protect Connectivity Node, you can re-add the connection using the same name as the deleted connection.
Aurora Endpoint DefenseAurora Endpoint SecurityInstallation or ConfigurationPublic