domain controllers

Discussion in 'ESET NOD32 Antivirus' started by a_kerbouchard, May 5, 2009.

Thread Status:
Not open for further replies.
  1. a_kerbouchard

    a_kerbouchard Registered Member

    Joined:
    Apr 17, 2008
    Posts:
    35
    I have updated all 600 computers from version 3 to the latest version of 4 and started slowly on the servers. 21 file and printer servers have had no problems, so I tried one of our domain controllers.We immediately lost remote desktop to the server and file sharing and printing on the domain controllers were all disabled. I had all the exclusions but had forgotten the %systemroot%/sysvol exclusions. I am afraid to put version 4 back on their to test though. Any thoughts?
     
  2. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    You had an exception for the C:\WINDOWS\NTDS\ and C:\WINDOWS\SYSVOL\ directories set up, correct? That is usually where the issues result from when working with domain controllers. There are also other database directories you will want to exclude depending on the other roles you DC might be running such as DNS, WINS, DHCP, or FRS points.
     
  3. a_kerbouchard

    a_kerbouchard Registered Member

    Joined:
    Apr 17, 2008
    Posts:
    35
    Yep I had all the recommended exclusions, but I had forgotten c:\windows\sysvol
     
  4. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    I would try again with that one. Replication on shares like that combined with file locking conflicts would be enough to hose a server. I believe Microsoft has a white-paper on exactly how the exclusions should be set up for the SYSVOL directory along with other DFS shares if that applies to your environment.
     
Thread Status:
Not open for further replies.