Skip to main content

Installation Server Manager

Guide​

The MSI installation files and the associated Application server can be found in the corresponding sections. The following step-by-step guide will accompany you through the wizards.

Password Secure Server Setup

First you are required to read and accept the license terms. These can also be printed.

Password Secure Server Setup

The next step is to define the location. The suggested location can be retained.

If you want to use Netwrix Password Secure as an identity provider Configuration of SAML must be selected. Otherwise, it will not be installed.

Password Secure Server Setup

Start the installation.

Password Secure Server Setup

The last step closes the setup and opens (if desired) the Server Manager.

Password Secure Server Setup

Authentication​

After the installation, you can login directly to the Server Manager.

Server Authentication

NOTE: The initial password for the first login is “admin”. It should be changed directly after the logon.

Installation

The following pages will provide you with all the information how to install the different Netwrix Password Secure components.

System landscape​

The following overview presents a basic production Netwrix Password Secure system landscape. Version 8 allows the use of several database servers across all sites. These are then synchronized using Microsoft SQL server tools. Any number of application servers can be made available for the client connection. This ensures load distribution, and allows work without significant latency. This technology offers enormous performance advantages, particularly in the case of installations that are spread across worldwide locations.

Client (presentation layer)​

The client layer handles the representation of all data and functions, which are provided by the application server.

Application server (business logic)​

The application server is entirely responsible for the control of the business logic. This server only ever delivers the data for which the corresponding permissions are available. The multi-tier architecture described at the beginning allows the use of several application servers and ensures efficient load distribution.

Database server (data storage)​

Netwrix Password Secure uses Microsoft SQL Server to store data due to its widespread use, and its ability to ensure high-performance access even in large and geographically scattered environments. Smaller installations may also use the free SQL Express version.

Conclusion​

At least three servers are thus recommended:

  • Database server (MSSQL)
  • Application server (Netwrix Password Secure services)
  • Web server (IIS, NginX, Apache 2)

CAUTION: For databases in a production system, we recommend using a fail-safe cluster. Microsoft SQL Server can replicate the data to a different data centre, e.g via WAN. We also recommend providing a Windows server for each function. Separating the systems makes it easier to expand and scale the system landscape at a later point. However, it is not absolutely necessary to separate the systems. Accordingly, all of the components can also be installed on one server in the case of smaller installations or test environments.

Firewall rules / Ports​

MSSQL Server​

  • Port 1433 TCP for communication with application server (incoming)

Application server​

  • Port 443 HTTPS for connection to the Netwrix Password Secure license server (outgoing)
  • Port 11011 TCP for communication with clients or web server IIS (incoming)
  • Port 11014 TCP for the backup service (usually does not need to be unlocked)
  • Port 11016 TCP for the Web services (incoming; only when using the Web Application)
  • Port 11018 TCP for real-time update (incoming)
  • Port 1433 TCP for communication with SQL Server (outgoing)

Webserver (Web Application)​

  • Port 443 HTTPS to access the webserver from the client (incoming)
  • Port 11016 for communication to the application server (outgoing)
  • Port 11018 for the real-time update (outgoing)

Client​

  • Port 11011 TCP for communication with the application server (outgoing)
  • Port 11018 TCP (outgoing)
  • Port 52120 TCP with the add-on (outgoing)