1 Topic by tomierna

  • tomierna
  • Member
  • Offline
  • Registered: 2018-02-18
  • Posts: 9

Topic: iRedAdmin-Pro to Enterprise Edition Hesitance

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.7.3
- Deployed with iRedMail Easy or the downloadable installer? No
- Linux/BSD distribution name and version: Ubuntu 24.04 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hello group,

Thank you to Zhang and the team for providing an upgrade path from iRedAdmin-Pro to the Enterprise Edition.

I've followed the instructions at this link: https://docs.iredmail.org/iredmail.to.ee.html

...and then went to the Install iRedMail Enterprise Edition document which is under a heading that says "Run the full deployment as migration".

Executing /usr/local/bin/iredmail results in this message on the CLI: "Seems server doesn't have iRedMail Enterprise Edition installed, launch installer on port 8080." which is true - I've never installed EE on this machine, but it does have iRedMail and iRedAdmin-Pro installed on it.

After a brief battle with firewall rules to open port 8080 on the server, I started through the installation wizard.

I stopped just before the final "Confirm and Deploy" button because it didn't seem like the installation wizard knew that this was a migration. I expected that some choices would be pre-filled based on what I've already got running on the server and their existing configuration.

How is the deployment of the Enterprise Edition deployment wizard supposed to be run as migration? Or is there no difference and I just need to answer questions like "First email domain name" and "LDAP Suffix" in the same way as the server is configured for it to treat the install deployment as a migration deployment?

I'm hesitant to press the "Confirm and Deploy" button on this production server because of the verbiage describing running the install as a migration, but then seeing no indication the wizard thinks it is a migration - can anyone describe their experience here to give me some confidence?

Thanks!

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,352

Re: iRedAdmin-Pro to Enterprise Edition Hesitance

It's like a fresh installation, but it detects sql credentials under /root/.iredmail/kv/sql_user_*, then use them directly, so all sql databases will be well kept.

It also generates config files for all involved software, so it's very important to split the customizations you made in software config files to /opt/iredmail/custom/ manually. iRedMail EE maintains the core config files, and you override them with custom settings defined in files under /opt/iredmail/custom/, so it should work well and not lose anything.

3 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,352

Re: iRedAdmin-Pro to Enterprise Edition Hesitance

Updated migration tutorial to mention this moment ago:
https://docs.iredmail.org/iredmail.to.ee.html#summary

4 Reply by Juanito (edited by Juanito 2025-05-08 01:12:57)

  • Juanito
  • Member
  • Offline
  • Registered: 2011-07-18
  • Posts: 9

Re: iRedAdmin-Pro to Enterprise Edition Hesitance

Hi, I’ve been an iRedAdmin-Pro customer for years, and recently upgraded my license to the Enterprise Edition (still in the migration process).

As a reseller offering email services, I used to customize the Pro admin UI templates a bit — mostly to hide advanced features from my customers, or to change the logo to reflect my brand, so clients would identify the interface as part of my service.

Now, with the new binary-based EE version, it seems there’s no way to configure or hide these elements anymore. Is there any workaround planned, or should I consider this a permanent limitation?

Thanks!