3
win 2008 R2 SP1 work with latest Smartermail?
Question asked by turtle - 4/6/2019 at 2:02 PM
Answered
My mail server is still running windows 2008 R2 SP1 standard

Will the newest release of smartermail install on this ?

5 Replies

Reply to Thread
0
Employee Replied
Employee Post
Technically you should be able to run the latest build of SmarterMail on Windows 2008 R2 SP1, though it is strongly recommended that you upgrade your server for a myriad of obvious reasons.  SmarterMail is built upon and requires the latest .NET Framework 4.7.2.
0
turtle Replied
To be more complete

IIS 6
dot net framework 3.5.1

Looks like .net needs updating.  IIS is a little dated too?

Scheduled hardware/software windows replacement is later this year.  Would like to continue using smartermail on this box until scheduled replacement.Newest windows this machine will support is 2008 r2 sp1. Been a steady user since SM 3.x..Never has a support ticket.  Maybe it would be best if someone from smarter tools took a look inside before I move forward with the upgrade?  Server is dedicated mail (no http etc)
1
Kyle Kerst Replied
Employee Post Marked As Answer
Your .NET framework will need to be updated, and .NET 4.7 installed at the very least. Your IIS version should facilitate set up of SmarterMail, but may also require updates (Windows Updates.) You can operate SM (latest) on Server 2008 but we cannot recommend or support this configuration as it lacks some key functionality we require to operate smoothly. My suggestion in this case would be to ensure you're running the latest available minor release of the version you are on currently (i'm assuming SM v15?), and then plan for an upgrade to SmarterMail (latest) once the server upgrade becomes feasible. 
Kyle Kerst System/Network Administrator SmarterTools Inc. (877) 357-6278 www.smartertools.com
0
turtle Replied
Current running version

SmarterMail Enterprise Edition
Version: 16.3.6989
1
echoDreamz Replied
I'd wait myself. Server 2008 R2 is hella old and nearly EOL. Stay with SM 16 and wait until you can update to at least Server 2016 then roll out SM 17.

Reply to Thread