A split installation separates the Faddom application from the PostgreSQL database, allowing each to run on dedicated hardware. The UI server handles web traffic and discovery, while a dedicated database server hosts all Faddom databases. This article walks you through deploying a split installation of Faddom on Windows Server.
Important: Take snapshots of both VMs before starting.
Prerequisites
Before starting, make sure both servers meet the following requirements:
Both servers run Windows Server with Faddom installed
Both servers are joined to the same Active Directory domain
Faddom is installed and the license is activated on the UI server only
Port 5432 is open from the UI server to the database server
The database server has enough free disk space for the DB dump and the migrated databases
The UI server has enough free disk space to be able to store the DB dump
Note: To find out how much space is needed for the DB, go to C:\Program Files\Faddom\Postgre and check the size of the "data" folder.
How the split works
In a split installation:
UI server: Runs the Faddom application (Tomcat and Network Sensor) and connects to the remote database server. Local PostgreSQL is disabled.
Database server: Runs PostgreSQL only. Tomcat is disabled. All Faddom databases are hosted here.
Run the split installation script
The split installation script automates the main flow, including database migration and updating the Faddom configuration so the UI server points to the remote PostgreSQL server.
Follow the steps below to run the split installation script.
Step by step:
Download the split installation script from here
Run the script from the UI server as an administrator.
Follow the on-screen prompts to complete the migration.
Once the script completes, allow 2-3 minutes for Tomcat to fully initialize, then navigate to the Faddom UI.
On the login screen, select Use Windows credentials and log in with your domain admin account, with the LDAP checkbox unchecked.
On the license activation screen, click Activate. The activation key is pre-filled and no new license key is needed.
After activation, the dashboard loads with all existing data intact.
Verify the installation
After completing the procedure, confirm the split is working correctly:
The dashboard loads and shows existing assets, maps, and discovery data
Active discoveries, such as VMware, are still running
Local PostgreSQL on the UI server remains stopped and disabled
Troubleshooting
"Unfortunately, you don't have the required permissions to activate the license."
This screen appears when the connection pool fails to initialize. The most common causes are:
The machine account role wasn't created correctly on the database server
A firewall is blocking port 5432 between the two servers
The illuminit.properties file still points to localhost instead of the database server
Script didn't complete cleanly
If the script didn't finish successfully, or the Faddom UI isn't behaving as expected after the split, contact support@faddom.com. Common symptoms include:
"Permission denied for function" errors in the PostgreSQL log
Login succeeds but redirects to a permission-denied screen
"Failed to install license" error during activation
The "Use Windows credentials" button doesn't appear on the login screen
Note: A "NegotiateApiAuthenticator Failed to start" warning in the Catalina log is benign and appears on both single-server and split installations. It doesn't affect functionality and can be ignored.
If you experience any issues or need assistance with your Windows split installation, contact support@faddom.com.