We'd love to hear about it! Click here to go to the product suggestion community
Our exchange server is going to be upgraded to 2019.
Is this version supported by PureMessage? Most documentation seems to refer to exchange 2016.
Exchange 2019 is not supported with PureMessage for Exchange 4.0.4 which is a latest version. Please refer this article to have information on supported OS and exchange version.
In reply to Jasmin:
Are you planning to release a new version soon that will support Exchange 2019?
Exchange 2019 was released in 2018....
In reply to Fil1:
Currently, there is no such update on the next version for the Puremessage for Exchange which will support 2019 exchange server.
If there is any update on this, it will be published on Community and Support Support twitter account. You can subscribe to message as well to get the notification.
Exhange 2019 on Server 2019 PureMessage version 4.04
IISCrypto best practice (https://www.nartac.com/Products/IISCrypto/Download) Apply best practice with IISCryto.Reboot
Disable UAC (msconfig tools)Reboot
Extract pmex64_404_sfx.exeIn the extracted folder there is a subfolder (C:\pme_404_64_AVAS\Resources)Run the following programsSQLNCLI.MSIVcredist_x64.exeSQLEXPR_x64_ENU.exeSQL default installation SOPHOS as instance name. (or make an other nice name) SQL Browser service on automatic.
Afther this start the setup from PureMessage and select localhost as database server.
Kind regards Robert Vergeer
In reply to RobertVergeer:
Thanks, worked a treat, I actually edited the reg first after reboot ran the install and failed to connect DB, so ran IISCrypto best practice and disabled UAC and rebooted and reran install, as all prerequisites installed prior to this, PM installed without an issue. I realize PM is nearling EOL but odd to leave PM hanging like this. The only issue is its unsupported.
In reply to CharlieCampbell:
Glad to know that it is resolved for you now.
In reply to Shweta:
Just jumping on this thread - we have the same issue - puremessage on Exchange 2019. When installing we get "unable to connect to '(local)\SOPHOS'. Please ensure that the selected SQL Server instance is available and that you have the access rights to connect to it'
Seems to be some SQL Authentication issue? We are unsure how to resolve it.
Support is sticking to its not supported go to sales - sales arent very proactive
In reply to Paul Curran:
No thre are leaving PM behind, move to Sophos to the cloud, and add mail in its rrally good, overcme some of the shortcomings of PM theta they never resolved.
But if like me you still have some on-premise, then the thread above does the trick from Robert Vergeer
Exhange 2019 on Server 2019 PureMessage version 4.04IISCrypto best practice (www.nartac.com/.../Download) Apply best practice with IISCryto.RebootDisable UAC (msconfig tools)RebootExtract pmex64_404_sfx.exeIn the extracted folder there is a subfolder (C:\pme_404_64_AVAS\Resources)Run the following programsSQLNCLI.MSIVcredist_x64.exeSQLEXPR_x64_ENU.exeSQL default installationSOPHOS as instance name. (or make an other nice name)SQL Browser service on automatic.Afther this start the setup from PureMessage and select localhost as database server.