Some may not like the fact you can not monitor the status from the Windows Home Server Console but I have found ESET to be maintenance free using the default settings with no need for user intervention. NOD32 does not install as an add-in but is installed using remote desktop. ESET recently confirmed that ESET NOD32 Antivirus 4.0 Home Edition is compatible with WHS so this was a no-brainer for my setup. I just expect an antivirus program to do its job without constantly being in your face saying here I am. It is just plain unobtrusive and includes spyware detection which is a bonus. My current computers use ESET NOD32 because of its proven low use of system resources and CPU cycles. WHS includes a competent firewall so antivirus protection was next for WHS. Andrew has reminded us in his post Why You Should Always Run Anti Virus Software and Firewalls the importance of security. Remote access opens ports (or data access pipes) in the router and WHS firewall to the internet to allow the user to access files in WHS shared folders or use of networked computers configured for remote control access. But my first concern was security of WHS once remote access is turned on. Now that it is up and running, performing nightly backups of all my networked computers, I have been itching to explore the remote access feature while I am away. Last month I put together a home built Windows Home Server (WHS) first and foremost for its powerful backup features.
0 kommentar(er)
