ESET Security product for Exchange does a pretty good job in handling emails and blocking malicious content but I have found that some versions have caused headaches for Exchange and I have had to roll back to a previous version.

You have the ability to perform two options with upgrading. Either you can do an export of the config and then uninstall the current version or you can do an in-place upgrade.

I went with the in-place upgrade option and it went through without an issue. Here are some screenshots of the upgrade and the different steps:

Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 1
Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 2
Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 3
Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 4
Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 5
Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 6
Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 7
Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 8
Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 9

Post upgrade checking.

After the servers in the ESET cluster were rebooted, the cluster came back online and was didn’t error out.

Exchange 2019 :- updating eset mail security for exchange to v9
Exchange 2019 :- Updating ESET Mail Security for Exchange to V9 10

Other checks done was looking at the application log in event viewer and if there was an issue, topology errors would be logging like crazy but in this case no errors were logged.

This upgrade was a success.

Hope it helps.

    wpChatIcon

    Discover more from COLLABORATION PRO

    Subscribe now to keep reading and get access to the full archive.

    Continue reading