Pre-Installation Checklist
The Pre-Installation Checklist ensures successful ServiceOps deployment by systematically verifying all prerequisites, requirements, and preparation steps before installation begins.
This comprehensive checklist guides IT administrators and implementation consultants through all necessary preparations for ServiceOps on-premises installation. Following this checklist helps prevent installation failures, configuration issues, and post-deployment problems.
Common Pre-Installation Checklist
The following checklist items are applicable to all deployment models. Deployment-specific checks are detailed in the tabs below.
System Requirements Verification
Hardware Requirements
- CPU: Verify minimum CPU cores based on user load and chosen deployment model. Refer to the System Requirements page for details.
- RAM: Confirm minimum memory requirements based on deployment.
- Storage: Ensure adequate disk space.
- Network: Verify minimum bandwidth.
Operating System Requirements
- Supported OS: Ensure a supported version of Ubuntu or RHEL is installed.
- System Updates: Latest OS patches and updates applied.
- Time Synchronization: NTP configured for accurate time.
- OS Interface: Ensure only non-GUI / CLI-based server OS installations are used. GUI-based installations are not supported.
Software Dependencies
- System Packages:
apt install msitools(Ubuntu) or equivalent installed.
Network Configuration
Port Requirements
Ensure the following ports are open and accessible for proper ServiceOps functionality. The required ports vary based on the components and integrations you use.
Core Component Ports
- HTTP/HTTPS (80/443 TCP): Standard web access for users and technicians.
- SSH (22 TCP): Remote administration of the server.
- DNS (53 TCP/UDP): Domain name resolution.
- Main Server (8080-8082 TCP): Internal services for the main application server.
- Database (5432 TCP): Default port for PostgreSQL database communication
Monitoring and Management Ports
- SNMP (161 UDP): Monitoring network devices.
- WMI (135, 445, 5000-6000 TCP): Managing Windows-based systems.
- WMI Dynamic Ports (49152-65535 TCP): Dynamic ports used by WMI.
Email Integration Ports
- SMTP (25/587 TCP): Sending email notifications.
- SMTPS (465 TCP): Secure email sending.
- POP3/POP3S (110/995 TCP): Email retrieval.
- IMAP/IMAPS (143/993 TCP): Email access.
Directory Services and Remote Access
- LDAP (389 TCP/UDP): Active Directory integration.
- LDAPS (636 TCP/UDP): Secure Active Directory integration.
- Mesh RDP Server (8443 TCP): Secure remote desktop access.
- Mesh RDP Internal (4430 TCP): Internal RDP services.
Component-Specific Ports
- Plugin Server (5050 TCP): Communication channel for plugins.
- ARP (219 TCP): Address Resolution Protocol services.
- DMZ Server (8085 TCP): Required for DMZ server deployments.
Firewall Configuration
- Firewall Rules: Configure firewall to allow required ports
- Ubuntu Firewall:
ufw allow [port]for each required port - RHEL Firewall:
firewall-cmd --zone=public --add-port=[port]/tcp - Network Segmentation: Plan DMZ deployment if required
- Proxy Configuration: Configure proxy settings if needed
Connectivity Verification
- Internet Access: Verify internet connectivity for updates and licensing
- DNS Resolution: Confirm DNS is working properly
- Bandwidth: Verify minimum bandwidth requirements are met
Security Preparation
SSL/TLS Certificates
- Certificate Planning: Decide on SSL certificate strategy
- Wildcard Certificates: Obtain wildcard certificates if using subdomains
- Certificate Storage: Plan certificate storage location
- Certificate Renewal: Plan for certificate renewal process
Authentication Setup
- Active Directory: Plan AD/LDAP integration if required
- LDAPS Configuration: Prepare LDAPS certificates for AD integration
- SSO Planning: Plan Single Sign-On implementation if needed
- User Provisioning: Plan user import and provisioning strategy
Access Controls
- Administrative Access: Plan admin user creation and access
- Service Accounts: Create necessary service accounts
- Permission Planning: Plan role-based access control
- Audit Logging: Plan audit and logging requirements
License and Activation
License Procurement
- License Types: Determine required license types:
- Service Desk licenses
- Asset Management licenses
- Patch Management licenses
- User Count: Calculate required licenses based on user count
- Module Requirements: Identify required modules and features
- License Agreement: Review and accept license terms
Activation Codes
- Activation Code: Obtain activation code from ServiceOps Technician portal, Admin > Organization > Account > License Details tab.
- Agent Credential Profile: Create agent credential profiles from Admin > Discovery and Agents > Agent > Agent Credential Profile tab.
- File Server Credentials: Prepare file server credential profiles from Admin > Patch Management > Patch Settings > File Server > Credential Profile tab.
Environment Preparation
Server Preparation
- Clean Installation: Ensure fresh OS installation or clean environment
- System Resources: Verify adequate CPU, memory, and storage
- Service Accounts: Create necessary system accounts
- Directory Structure: Plan directory structure for installation
- Backup Strategy: Implement backup strategy before installation
Database Planning
- PostgreSQL: PostgreSQL will be installed with ServiceOps
- Database Storage: Plan separate storage for database if distributed
- Database Performance: Consider SSD storage for database
- Backup Strategy: Plan database backup and recovery procedures
Storage Planning
- Application Storage: Plan storage for application files
- Database Storage: Plan storage for database files
- Log Storage: Plan storage for system logs
- Backup Storage: Plan storage for backups (2-3x data size)
- File Server Storage: Plan storage for file server if required
Pre-Installation Tasks
System Configuration
- Hostname: Set appropriate hostname for server
- IP Configuration: Configure static IP address
- Time Zone: Set correct timezone
- Language: Set appropriate language settings
- System Updates: Apply all system updates
User and Permission Setup
- Administrative User: Create administrative user account
- Service User: Create service user account if needed
- Permissions: Set appropriate file and directory permissions
- Sudo Access: Configure sudo access for installation user
Network Configuration
- Network Interfaces: Configure network interfaces
- Routing: Configure routing if required
- DNS Configuration: Configure DNS settings
- Proxy Settings: Configure proxy if required
Final Verification
Pre-Installation Checklist Review
- All Items Checked: Verify all checklist items are completed
- Dependencies Met: Confirm all dependencies are satisfied
- Resources Available: Verify all required resources are available
- Team Ready: Confirm installation team is ready
- Backup Complete: Verify backup is completed before installation
Installation Readiness
- System Ready: Confirm system is ready for installation
- Network Ready: Confirm network is properly configured
- Security Ready: Confirm security measures are in place
- License Ready: Confirm licenses and activation codes are available
- Team Trained: Confirm installation team is trained and ready
Deployment-Specific Checklist
Select the tab corresponding to your intended deployment model to complete the final verification steps.
- Standalone
- Distributed
- Multi-Site
- High Availability (HA)
- Disaster Recovery (DR)
For a Standalone deployment, all checks are covered in the Common Pre-Installation Checklist. Ensure you have verified all items in that section before proceeding with the installation.
- Server Provisioning: Ensure separate servers are provisioned for the Application and the Database.
- Static IPs: Verify static IP addresses are assigned to both Application and Database servers.
- Network Connectivity: Confirm that the Application server can communicate with the Database server over the network, specifically on the PostgreSQL port (5432).
- Shared Storage: Plan shared storage if required.
- Latency Test: Perform a network latency test between the Application and Database servers. Latency should ideally be less than 10ms.
- Server Provisioning (Main Site): Verify that the server(s) for the main ServiceOps application and database are provisioned at the central site.
- Server Provisioning (Remote Site): Ensure dedicated servers for the File Server and Poller have been provisioned at each remote site.
- File Server Installation: Confirm the File Server component is installed and accessible from the Main Site.
- Poller Server Installation: Confirm the Poller component is installed and visible in the ServiceOps portal.
- Proxy/DMZ Planning: Plan for a Proxy or DMZ server if required for remote site connectivity.
- Network Connectivity: Confirm stable network connectivity between the main site and all remote sites.
- Firewall Rules: Verify that firewall rules have been configured to allow communication from the main server to the remote File Server and Poller servers (typically over HTTPS, Port 443).
- Server Provisioning: Verify that three separate servers are provisioned (Master, Slave, HA Observer).
- Static IPs: Confirm that static IP addresses are assigned to all three servers.
- Version Consistency: Ensure the same version of the Operating System and ServiceOps is installed on both the Master and Slave servers.
- User Account Consistency: Verify that the same SSH username and password (with
sudorights) exist on the Master, Slave, and HA Observer servers. - HA Proxy / Load Balancer: Plan the HA Proxy server and load balancer configuration.
- Firewall Rules:
- Confirm ICMP (ping) is allowed between all three servers.
- Confirm SSH (port 22) access is allowed from the Observer to the Master and Slave servers.
- Confirm PostgreSQL (port 5432) access is allowed between the Master and Slave servers.
- Failover Testing: Plan and document the procedures for failover testing.
- Server Provisioning: Verify that servers are provisioned for both the primary Data Center (DC) and the Disaster Recovery (DR) site.
- Resource Consistency: Confirm that the hardware, OS, and ServiceOps application versions are identical on both DC and DR servers.
- Stable Connectivity: Ensure continuous and stable network connectivity is established between the DC and DR sites.
- Firewall Rules: Verify that SSH (port 22) and PostgreSQL (port 5432) ports are open for communication between the DC and DR sites.
- User Account Consistency: Confirm that a consistent SSH username and password (with
sudorights) are configured on both DC and DR servers. - File Ownership: Check that the ownership of the
/opt/flotomatedirectory is correctly set tofmtuser:fmtusergroupon both servers.
chown -R fmtuser:fmtusergroup /opt/flotomate
- Script Cleanup: Verify that any pre-existing HA scripts (
master.sh,slave.sh) have been backed up or renamed on both servers to prevent conflicts.mv /opt/HA/slave.sh /opt/HA/slave.sh.bkp
mv /opt/HA/master.sh /opt/HA/master.sh.bkp