Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS: Anti-Virus Scanning Exclusions RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    We are having problems with WHS and Windows 7 where discovery and display of network shares from the Win7 client takes about 1 minute!

    Also, when working in say, Word 2007 and pressing save to a network shared folder, Word hangs for about a minute also.

    If we turn off ESET NOD43 4.0.474 then the problem goes away.

    ARE THERE ANY RECOMMENDED EXCLUSIONS FOR ANTI-VIRUS SCANNERS FOR WHS?

    Thanks,

    James.
    Monday, February 8, 2010 2:57 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    No, there are no recommended exclusions from the Windows Home Server side. Have you checked with your AV vendor to see if they can help you, since your issue is with your AV product?
    I'm not on the WHS team, I just post a lot. :)
    Monday, February 8, 2010 3:23 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Thanks for the reply.

    ESET UK seem none-the-wiser, I'm afraid!

    James.
    Monday, February 8, 2010 7:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    hmmm...

    How about:

    C:\FS
    D:\DE
    D:\folders

    It seems some vendors make these exclusions by default in their AV products?

    James.
    Monday, February 8, 2010 8:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Those exclusions would effectively prevent your antivirus product from scanning anything in your server shares. To me, that says the AV product being considered isn't really suited for use on Windows Home Server, because the only ways files should reach your server are A) through a Windows Update (whether automatic or manual via the Update button in the console) or the shares...

    Have you considered a product from another vendor?
    I'm not on the WHS team, I just post a lot. :)
    Monday, February 8, 2010 8:54 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    we are beginning to...!

    The data looks like it's actually in D:\Shares, is it not though?

    Is there someone from MICROSOFT that actually has a rock solid answer about AV for WHS??

    WHO actually says that their AV product WORKS with WHS?

    ESET says it does, but UK support have roughly zero experience with it...

    James.
    Monday, February 8, 2010 10:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The data is not in D:\Shares\etc., no.

    Microsoft doesn't have an AV product for Windows Home Server, so I'd say you shouldn't expect them to have much to say on the topic, other than "Use a product designed for Windows Home Server; other products may cause odd issues."

    I've been using Avast! for Windows Home Server (the package with several client licenses) for two years.
    I'm not on the WHS team, I just post a lot. :)
    Monday, February 8, 2010 10:19 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    seeing as MS don't have any AV products for server 2003 or 2008, but do provide exlcusions lists for AV products, does the same thing exist for WHS?

    Kind regards,

    James.
    Tuesday, February 9, 2010 12:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi James,

    You are right - it's hard to find the information on what needs to be done for virus scanning.  I actually am in the midst of implementing ClamAV on Windows Home Server.  I was advised not to scan the parts of c:\fs, d:\de and d:\folders.

    Also you have to consider what happens when a virus is detected, how Drive Extender handles it and how you remove both files if it's a duplicate file.

    Cheers,
    Al
    --
    Tuesday, February 9, 2010 2:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    As I said, I doubt that Microsoft is going to issue any guidance that they haven't already provided.

    What that boils down to is:
    1. Any antivirus product not designed for use on Windows Home Server is likely to cause issues, including data loss issues, so
    2. You should only use a product designed for Windows Home Server on your server.
    I'll note that ClamAV is not designed for use on Windows Home Server, so I would not use it myself. Likewise NOD32 (your product) is not designed for use on Windows Home Server. The product I personally use is Avast! for Windows Home Server; I have the family pack which includes the server version and several licenses for the client version. There are other products: Fsecure has one, as does McAfee (though I don't know if that's available as a retail product; it's mostly distributed with OEM servers). BitDefender says their free version is compatible, but I don't have any experience with it. There may be others, as well.
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, February 9, 2010 3:31 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I agree with Ken - ClamAV is not supported on Windows Home Server - perhaps I wasn't clear enough about that in my post.
    --
    Tuesday, February 9, 2010 4:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    NOD32 IS designed and qualified for WHS, as per the ESET web site and indeed the installation instructions on the ESET KB.  ESET UK support have had so few calls about issues between WHS and NOD32 - and that is almost the problem I have; the lack of good info to solve the hanging with Win7.

    ESET did think I needed to make exlcusions, but pointed me to MS article 822158.  I pointed out that the information wasn't relevant to WHS but have found little (zero) other actual information *anywhere* else.  Hence you find me here.  As a MS partner, we are used to direct contact with MS PS support, but there seems to be zero help for WHS?

    What exactly IS the "guidance MS have already provided?"  other than to use a WHS qualified AV product, which I am doing?

    All I can assume is that NO ONE is able to give any technical information on AV for WHS, including MS, ESET or anyone else.  AVAST have a product, but we are in fact an ESET partner and have licenses already for a product that *should* work.  ESET should certainly have more info on this - but clearly not many (if any) other people are in the same position (i.e. they actually have a WHS, have ESET on it AND are having problems.  All the reviews of NOD32 v4 with WHS are glowing.)

    My next step will be to contact ESET HQ and see if they have any more info.  Unfortunately we seem to have drawn a blank here.

    James.

    Tuesday, February 9, 2010 9:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I understand where you're coming from, James. Unfortunately, the only guidance that I'm aware of directly from Microsoft is that sketchy consumer-oriented info I've already provided. I don't know of anything else that they might have provided to ISVs (though I wouldn't necessarily know about such things) but one would hope that a product designed for use on Windows Home Server would already have incorporated all such guidance.

    Since you're a partner, you can try the additional channels that opens up to you to see if there's anything more out there, though I don't think there is. 
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, February 9, 2010 9:54 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'll let you know what I find out.

    Thanks guys,

    J.
    Wednesday, February 10, 2010 7:31 AM