Steps to upgrading SmarterMail and Windows Server?
Question asked by Douglas White - 12/5/2014 at 9:54 AM
I've been tasked with updating a mail server running Windows Server 2003 R2 x86 & SmarterMail 6.9 to another server running Windows Server 2012 R2 & SmarterMail 13.
The old server has ~50Gigs of mail on it now and looking at the KB articles, it is suggested that we upgrade SM to v7 first?
I'm trying to formulate an upgrade path to make the move.
Any suggestions?

3 Replies

Reply to Thread
Steve Reid Replied
If I were you I would install 6.9 on the new server, get it running right, then copy over the data and ensure the move works properly. Then update to v7 or v13
Employee Replied
Employee Post
Good afternoon Douglas,
Thanks for the inquiry about moving SmarterMail to a new server and performing an upgrade in the same process.  Please keep in mind that due to the file structure changes from SmarterMail 7.x and above we do recommend installing this build prior to implementing SmarterMail 13x.
We do have a few articles on how to perform the steps and you may be familiar with the server requirements and specifications.  Please note that you may want to configure the server first in preparation of the move. Please install any updates and server specifications, such as .NET 4x and any IIS components. 
I would suggest to try and implement at least the current build of SmarterMail 7.x on the old server to ensure that the folder structure changes takes place and then when you have the data backed up and you are ready to move to the new server you can either install version 7x and confirm that it is working properly and then install the current build of SmarterMail 13x.
Please let us know if you have any other questions and open a Support ticket.
Thank You.
Paul Blank Replied
In fact, I need to do the same with a much later version of SM and server 2003 x64. I intend to move the program to the new 2012 R2 server, get it running there, upgrade, have ST take a look at it (and yes, use a support incident), and then thoroughly test it as much as I can with a temporary domain name before using it in production. After full testing, I will move the database from the running server and re-install.

Reply to Thread