Overview
For both upgrades and new installations, please always follow the steps detailed in the Installation Guide, particularly to ensure correct responses to any Windows 'files in use' prompts encountered during the upgrade.
For client/server upgrades, the server instance must be running the same or a later version of Mailroom as the attached client(s). To determine the installed version, launch the Mailroom application and select Help > About.
To ensure compatibility, upgrade the server (EPService and Database service host) first.
Ensure you have a current registration code before commencing a Mailroom or EasyPost Services upgrade. The code can be obtained by any Bing Customer Portal user with sufficient permissions, or by contacting Bing Customer Service. The Account ID may also be required.
Registration codes expire 7 days from first use.
If upgrading from Mailroom v6.4 or older versions, stop the EasyPost database service, browse to the Mailroom database location, and delete the .config database folder. This is necessary due to a database key change.
Upgrade Steps
Download and run the EasyPost Mailroom msi. Follow the installation steps detailed here, acknowledging the additional upgrade screen in the wizard.
During the upgrade, a "Files in Use" dialogue may appear (see figure 1.1). Choose the option "Do not close applications. A reboot will be required", and click OK to continue.
Fig 1.1
Once installation is complete, launch the Mailroom and register the Mailroom if promoted using the registration code (and Account ID if required). You may also be prompted to register as a user if you haven't already.
Moving Mailroom Server
If mailing history is to be retained, back up all Mailroom databases using the Database Tool. File copy is NOT supported.
On the new server, download and run the EasyPost Mailroom msi. Follow the installation steps detailed in the installation guide
When the installation is complete you can restore the databases using the Database Tool.
Once databases are restored all existing Mailroom clients will need to be re-directed to the new server. Actions required depend on how the clients were connected initially.
- If network discovery was used, stop the EasyPost services on the old server, launch a Mailroom client, and confirm it detects the new server.
- If an environment variable (EP_SVC_HOST) was used, change the value from the old to the new server name.
- If the server name was manually entered, find the file C:\ProgramData\Easypost\MailroomConfig.json and change the "svc_host" value to the new server name on each client.