satellite360 0 Posted March 16, 2017 Share Posted March 16, 2017 Hi In the ESET Remote Administrator the upgrade package ESET File Security for Microsoft Windows Server v6.5.12007.0 is showing as valid for Windows Server 2008 and 2003 only. Is this correct? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted March 16, 2017 Administrators Share Posted March 16, 2017 It must be just a glitch with the repository. EFSW 6.5 is compatible with all Windows Server systems, including Windows Server 2012 / R2 and WS 2016 too. Link to comment Share on other sites More sharing options...
satellite360 0 Posted March 16, 2017 Author Share Posted March 16, 2017 4 minutes ago, Marcos said: It must be just a glitch with the repository. EFSW 6.5 is compatible with all Windows Server systems, including Windows Server 2012 / R2 and WS 2016 too. So other users are seeing correct data in the ERA? Is there a way to force a re-synch of the repository? Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted March 16, 2017 ESET Staff Share Posted March 16, 2017 Most probably they see the same. In our releasing tool, we mark compatible systems for 32-bit and 64-bit systems. Repository shows one entry per product for both, and in the case you have reported only 32-bit systems are shown. We will follow up with the team responsible to update the metadata to show correct information. Link to comment Share on other sites More sharing options...
kkthnxbb 0 Posted March 16, 2017 Share Posted March 16, 2017 (edited) I got issue with this update, for a windows server 2008 i got HIPS problem - cant enable, in policy this feature must be enabled but its not. And in Windows server 2012 r2 Anti-Phishing protection is non-functional. Uninstall, Install or repair wont help. Edited March 16, 2017 by kkthnxbb Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted March 16, 2017 Administrators Share Posted March 16, 2017 1 hour ago, kkthnxbb said: I got issue with this update, for a windows server 2008 i got HIPS problem - cant enable, in policy this feature must be enabled but its not. And in Windows server 2012 r2 Anti-Phishing protection is non-functional. Uninstall, Install or repair wont help. Please do not hijack someone else's topic on a different subject / issue but create a new one instead. Also drop me a pm with the output from ESET Log Collector attached so that I can check the status and config of your ESET product. Link to comment Share on other sites More sharing options...
satellite360 0 Posted March 17, 2017 Author Share Posted March 17, 2017 18 hours ago, MichalJ said: Most probably they see the same. In our releasing tool, we mark compatible systems for 32-bit and 64-bit systems. Repository shows one entry per product for both, and in the case you have reported only 32-bit systems are shown. We will follow up with the team responsible to update the metadata to show correct information. Hi MichaelJ Thanks for the update - so you can confirm that the package I'm seeing is good to install and this is just a simple metadata issue? Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted March 17, 2017 ESET Staff Share Posted March 17, 2017 Yes, that is correct. Correct list of supported Operating systems is listed in product documentation and on the respective download page. This is only a metadata issue (as you can see, other server products, which are all based on EFSW are supporting all WS OS, including 2016. Link to comment Share on other sites More sharing options...
Recommended Posts