Installation Guide for Linux and Windows #
LT AuditorMP is available for both Linux and Windows environments. Follow the installation instructions for your operating system below.
Prerequisites #
System Requirements #
| Linux | Windows |
| Root or sudo access required Supported distributions: SLES 15+ Ubuntu 22.04 LTS+ Debian 12+ | Administrator privileges required Supported versions: Windows Server 2019 or newer |
Network Access #
Ensure all required ports are open and not blocked by local or network firewalls.
End User License Agreement (EULA) #
Before installation begins, you must accept the End User License Agreement (EULA).
The installation scripts will display the agreement and prompt for confirmation before continuing.
Linux Installation #
Navigate to the Scripts Directory #
cd scripts
Switch to Superuser Mode #
sudo su
Make Scripts Executable #
chmod +x *.sh
Run the Installation Script #
./install.sh
Follow the on-screen prompts to complete the installation.
Linux Post-Installation #
Verify Services #
Check that all required services are running:
systemctl status lta-web
systemctl status lta-collector
Review Logs #
Collector Logs #
cd /opt/bluelance/lcollector/logs/general/
Web Application Logs #
cd /opt/bluelance/web/server/logs/
Managing Services (Linux) #
Using systemctl #
Start Services #
sudo systemctl start lta-web
sudo systemctl start lta-collectorRestart Services #
sudo systemctl restart lta-web
sudo systemctl restart lta-collectorStop Services #
sudo systemctl stop lta-web
sudo systemctl stop lta-collectorCheck Service Status #
sudo systemctl status lta-web
sudo systemctl status lta-collectorEnable Services at Boot #
sudo systemctl enable lta-web
sudo systemctl enable lta-collectorManaging the Web Application with PM2 #
The PM2 ecosystem configuration file is located at:
/opt/bluelance/web/ecosystem.config.jsStart the Application #
cd /opt/bluelance/web
npx pm2 start ecosystem.config.jsCheck Application Status #
npx pm2 listDetailed Status and Logs #
npx pm2 status
npx pm2 logsRestart the Application #
npx pm2 restart ecosystem.config.jsRestart by Application Name #
npx pm2 restart lta-webStop the Application #
npx pm2 stop ecosystem.config.jsStop by the Application Name #
npx pm2 stop lta-webSave the PM2 Process List #
npx pm2 saveMonitor Resource Usage #
npx pm2 monitNote:
After making changes in PM2, run npx pm2 save to ensure processes restart automatically after a system reboot.
Windows Installation #
Open PowerShell as Administrator #
Launch a PowerShell window using Run as Administrator.
Navigate to the Windows Directory #
cd WindowsAllow PowerShell Script Execution #
Set-ExecutionPolicy UnrestrictedRun the Installation Script #
.\Install.ps1Follow the on-screen prompts to complete the installation.
Reset the Execution Policy #
Set-ExecutionPolicy RestrictedWindows Post-Installation #
Verify Services #
sc query LTA_Web
sc query LTA_Server
sc query LTA_DataCollectorReview Logs #
Web Application Logs #
\Program Files\Blue Lance 2-0\Web\Apps\Logs\
Collector Logs #
\Program Files\Blue Lance 2-0\Collector\Logs\General\
Next Steps #
After installation, configure the appropriate modules to send logs and events to LT AuditorMP.
Documentation is available at:
Available Modules #
| Module | Description | Download |
|---|---|---|
| LT AuditorMP NSS Module | Sends NSS file activity events | Download NSS Module |
| LT AuditorMP EventLogCentral | Sends Windows Event Logs and NTFS file activity | Download EventLogCentral |
| LT AuditorMP PII Scanner | Scans and sends PII scan data for Windows and Linux systems | Download PII Scanner |
| LT AuditorMP PowerShell Orchestrator | Scans assessment reports for Active Directory and Entra ID | Download PowerShell Orchestrator |
| LT AuditorMP Entra Connector | Sends Azure Sign-In and Entra ID logs | Download Entra Connector |
Troubleshooting #
Cannot Access the Application Remotely #
Verify that 127.0.0.1 was not used during installation.
Use the server’s actual IP address or domain name instead.
SMTP Not Working #
SMTP settings can be updated after installation by editing the configuration files within the installation directory.
Port Conflicts #
Ensure required ports are not already in use by other applications before installation.
Service Errors #
Review application logs for warnings or errors in the log directories listed above.
Support #
For additional support, troubleshooting assistance, or deployment guidance, contact your system administrator or refer to the official documentation.
