The thread moved from correcting a panel-versus-OS mismatch to reinstalling Windows Server 2025 with SQL Web Edition, then aligning SmarterMail with the customer’s owned 16.x license after the latest build capped them at Free Edition.
October 4 – 6, 2026
Control Panel Label Did Not Match The Running OS
The customer discovered their VPS had shipped years ago on Windows Server 2012 while the billing panel showed Windows Server 2016 after a platform migration—causing compatibility and trust issues for their project stack. Database Mart confirmed a clean reinstall was the right path (not an in-place jump from 2012), with the existing system disk attached afterward so SQL backups, SmarterMail folders, and site files remained reachable.
They asked for downtime estimates and whether SQL Server Web Edition would remain under their existing addon. Support clarified Windows Server 2025 support on VPS server hosting, SolidCP limits (SQL up to 2022), and that Web Edition could be installed on the refreshed machine rather than downgrading to Express.
October 8 – 10, 2026
Scheduled Reinstall: Windows 2025, SQL Web, Application Stack
After rescheduling to a staffed maintenance window, engineers reinstalled Windows Server 2025 on a new system disk, kept the VPS on its existing network assignment, and mounted the prior C: volume as additional drives (E: and F:) plus the original data disk as D:—including D:\VPSBackup-102026. They installed Node.js 20.13.1, SQL Server 2022 Web Edition (instance INS2016, mixed mode, TCP enabled on a non-default port documented in the ticket), SSMS, IIS with URL Rewrite, .NET Framework 4.8, ASP.NET Core Hosting Bundle 8.0.31, and SolidCP with SQL integration.
SmarterMail 15.3.6081—the version named in the early plan—was not available in support’s package library. With that gap acknowledged in the thread, the customer explicitly authorized installing the latest compatible SmarterMail build from support’s current installer, intending to migrate data from SmarterMail 15.3 on the attached legacy paths.
| Component | Target | Status after Oct 10 |
|---|
| OS | Windows Server 2025 | Installed |
| SQL | 2022 Web · INS2016 | Installed |
| SmarterMail 15.3 media | Legacy restore source | Package unavailable |
| Mail ports | Standard SMTP / IMAP / POP (+ TLS) | Not opened yet (Oct 10) |
Table reflects the post-reinstall checkpoint on October 10, before SmarterMail was fully online.
October 13, 2026
Latest SmarterMail Ran As Free Edition—Multi-Domain Blocked
Support completed installation of the current SmarterMail build on Windows Server 2025—the build the customer had approved after 15.3 media could not be sourced—and opened the standard mail ports requested in the ticket (specific port numbers were confirmed in support correspondence, not repeated here). The customer successfully re-attached one primary domain (~23 mailboxes, several GB) but hit Free Edition limits when adding the remaining domains whose folders still existed on D:.
Engineers recovered license metadata from a legacy config file on the attached F: volume: SmarterMail Professional Edition 16.x for 250 mailboxes, owned license, unlimited domains in policy terms, with upgrade protection expired in 2017. Activation attempts on the new build returned that the key was not valid for that product version—expected when the installer tracks a newer major line than the customer’s perpetual 16.x entitlement.
SmarterMail UI (latest build on VPS):
“The license key provided is not for this version.
Please upgrade your license at smartertools.com/purchase.”
Customer goal:
Professional 16.x + multi-domain restore from
D:\SmarterMailDomains\Domains\
October 14 – 15, 2026
Authorized Downgrade Install To 16.3.6989
Support asked for explicit authorization to fully uninstall the current SmarterMail version—including removing its program folders—and install build 16.3.6989 from SmarterTools’ 16.x download channel. The customer confirmed, noting they would need to re-register domains in the admin UI even for domains already restored on the interim install.
Alina’s team executed the change set: remove the newer installation, deploy SmarterMail 16.3.6989, preserve D:\SmarterMailDomains\Domains\, leave E: and F: attached, and keep the same mail ports open as on the October 13 install. SmarterMail admin URL and login details were provided only in the ticket; login used the existing Windows administrator credentials. SmarterTools license activation stayed with the customer’s own account in the admin panel.
“We have completed the SmarterMail installation as requested. Domain data path retained. Please verify admin login, confirm MailService is running, and re-register domains through the admin panel. Reply with ‘SmarterMail confirmed’ when everything works.”
Alina, Support Department · October 15, 2026
# Post-install verification (customer-side)
1. Open the SmarterMail admin URL from the ticket → login page loads
2. Log in with administrator credentials → dashboard loads
3. PowerShell: Get-Service MailService → Running
4. Test-Path D:\SmarterMailDomains\Domains → domain folders present
5. Activate 16.x license with SmarterTools account credentials
6. Re-attach remaining mail domains from preserved data
7. Reply “SmarterMail confirmed” when mail and license checks pass
At publication time the ticket was still open: the 16.3.6989 build matched the customer’s 16.x key, but SmarterTools activation and multi-domain restore were finishing on the customer side before the closing phrase.
