Applications
Chapter 17.3: Configuring Mail and File Servers
Learn how to integrate EDCC with essential external services, including your email server and a file server.
🔐 Organization Administrator Only
Required Role: Organization Admin only
Access Level: Complete EDCC platform administration
Restriction: POD Admin and Viewers cannot access this section
Purpose: SMTP and file server configuration for system operations
Overview: Integrating EDCC with Your IT Ecosystem
The System > Application Settings page is where you connect the EDCC platform to your broader IT ecosystem. Properly setting up these services is a prerequisite for unlocking some of EDCC's most powerful automation and collaboration features.
This page allows an Organization-level Admin to configure two critical integrations:
Mail Server (SMTP): To enable all email-based communication.
HTTPS File Server: To enable remote OS installation capabilities.
Task 1: Configuring the Mail Server (SMTP)
Enabling Proactive Communication
This section allows you to connect EDCC to your organization's SMTP server. Configuring this transforms EDCC from a passive tool that you must actively check into a proactive communication hub that pushes critical information to you and your team.
Why This is a Critical Feature
Without a configured mail server, all system notifications are confined to the UI's notification center (the bell icon). Integrating an SMTP server enables proactive and automated communication for these essential features:
Team Member Invitations
This is the only way to add new users to the EDCC platform. The invitation system relies entirely on email to send access links to new team members.
Essential for user management
Proactive Event Notifications
You can receive immediate email alerts for important system events (e.g., critical hardware failures). This allows you to respond to problems quickly, even when you are not actively monitoring the dashboard.
Reduces response time to critical issues
Automated Maintenance Updates
EDCC can automatically notify you when a scheduled task, such as a firmware update for a POD, has been completed, providing a convenient audit trail.
Improves maintenance transparency
SMTP Configuration Explained
SMTP Server / Port
The address and port of your mail server (e.g., smtp.office365.com and port 587). Why it matters: These must be correct for EDCC to establish a connection with your email infrastructure.
Authentication
A toggle to enable SMTP authentication. Why it matters: Most modern mail services require a valid username and password to prevent unauthorized use. This should almost always be enabled.
User Name / Password
The credentials for the SMTP account. Why it matters: It is best practice to use a dedicated service account for this purpose.
From Email Address
The email address that EDCC will use as the sender (e.g., [email protected]). Why it matters: This affects how recipients see the email and may be important for email filtering rules.
To Email Address
The default recipient email address for system notifications (e.g., [email protected]). Why it matters: This ensures that critical alerts are sent to the correct team distribution list.
The Recommended Workflow: Test Before You Apply
Step-by-Step Process:
Fill in all the required server and credential details
Click the Test button. EDCC will attempt to send a test email to confirm the settings are correct
Once the test is successful, click Apply to save the configuration permanently
Best Practice: Always Test First
Always use the Test button to confirm your settings are correct before applying them. This prevents misconfigurations that could disrupt notification delivery.
Task 2: Configuring the HTTPS File Server
Enabling Remote OS Deployment
This section allows you to enable a secure, internal file-sharing service within the EDCC platform. Activating this is the cornerstone of EDCC's bare-metal provisioning and remote maintenance capabilities, turning your OS Repository into a functional, network-accessible library.
Why This is a Critical Feature
The primary purpose of the HTTPS File Server is to enable Remote OS Installation. It provides the essential mechanism for EnGenius nodes to access and mount bootable ISO files from the OS Deployment repository. This allows you to perform clean OS installations on new nodes or re-image existing ones entirely remotely, eliminating the need for physical media like USB drives and ensuring a consistent, scalable server deployment process.
HTTPS File Server Configuration Explained
File Sharing
The master toggle to enable or disable the HTTPS File Server. Why it matters: This service must be enabled for the Mount ISO Image operation to work. If it's disabled, all remote OS deployments will fail.
User Name / Password
The credentials required to access the file server. Why it matters: The nodes' BMCs will use these credentials to authenticate and access the ISO files. Setting a strong, unique password here protects your OS images from unauthorized access.
Configuration Process: After enabling the service and setting the credentials, click Apply to activate the file server.
Integration Dependencies and Impact
Feature Dependency Matrix
Team Member Management
Yes
No
Cannot invite new users
System Notifications
Yes
No
No email alerts for critical events
OS Deployment
No
Yes
Cannot mount ISO images remotely
Firmware Updates
Recommended
No
No completion notifications
Maintenance Reports
Recommended
No
No automated status updates
Security Considerations
SMTP Security:
Dedicated Service Account: Use a dedicated email account for EDCC, not personal accounts
Limited Permissions: Service account should only have send permissions
Authentication: Always enable SMTP authentication for security
Monitoring: Monitor email activity for unusual patterns
File Server Security:
Strong Credentials: Use complex passwords for file server access
Network Isolation: Consider network segmentation for file server access
Access Logging: Monitor file server access patterns
Content Validation: Only upload verified, scanned ISO images
Troubleshooting Common Issues
SMTP Configuration Problems:
Test Email Fails: Verify server address, port, and credentials
Authentication Errors: Confirm username/password and authentication method
Firewall Issues: Ensure SMTP ports are open in network firewalls
Email Delivery Problems: Check spam filters and email routing rules
File Server Configuration Problems:
Mount ISO Fails: Verify file server is enabled and running
Authentication Errors: Check BMC credentials and file server password
Network Connectivity: Ensure nodes can reach EDCC file server
File Access Issues: Verify ISO files are properly uploaded and accessible
Chapter Summary & Key Takeaways
SMTP is Required for Users & Alerts: You cannot invite new team members or receive email notifications without a correctly configured Mail Server
HTTPS is Required for OS Deployment: You cannot use the Mount ISO Image feature without enabling the HTTPS File Server
Always Test SMTP: Use the Test button to validate your mail server settings before saving them
Admin-Only: These settings are foundational and can only be configured by an Organization-level Admin
Security First: Use dedicated service accounts and strong passwords for both integrations
Test Dependencies: Verify both services work correctly before relying on dependent features
What's Next: Chapter 17.4 will explore Backup and Restore capabilities, where you'll learn to protect and recover your EDCC platform configuration and data.
💡 Pro Tip: Configure these integrations during initial EDCC deployment - many core features depend on them, and retrofitting can disrupt established workflows.