chetankb1 2 Posted December 3, 2016 Author Share Posted December 3, 2016 Earlier we were using 6.4.12002, after this problem only we have upgraded it to version 6.4.12004.0. Link to comment Share on other sites More sharing options...
Shaival 0 Posted December 3, 2016 Share Posted December 3, 2016 Hi, In my case I applied "File Security for Windows Server - Antivirus - Ransomware Prevention" & I found that this policy as culprit but only unassigned is not the solution for this topic you need to uninstall ESET File Security once after unassigned the ransomware prevention policy & you need to create a Product Activation task again it doesn't matter which version you are install. But as you know the Server's important it is not possible to restart without taking a down time. If there is a task for product deactivation it would be a better (& If there is a please let me know) because in this case you cannot deactivate the seat even through ELA beacuse license cannot synchronize. Link to comment Share on other sites More sharing options...
Shaival 0 Posted December 22, 2016 Share Posted December 22, 2016 Hello, Is there any link where we can find the latest ransomware protection policy without any bug? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,050 Posted December 23, 2016 Administrators Share Posted December 23, 2016 The policy was fixed several months ago. Just send a deactivation task to the affected clients followed by an activation task so that correct license details are retrieved from ESET's servers. Link to comment Share on other sites More sharing options...
Recommended Posts