Importing XML settings through GPO

Discussion in 'ESET NOD32 Antivirus' started by bradtech, Dec 6, 2009.

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

    bradtech Registered Member

    Joined:
    Nov 16, 2009
    Posts:
    84
    Is this possible? I'd like to import my NOD32 settings down through Active Directory Group Policy when a machine logs in... This is to verify that all my computers are actually configured correctly due to Technican mistakes in the past.. I found a couple machines that just had ESET installed, and was not configured correctly.
     
  2. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    The easiest thing would be to export the HKLM\Software\Eset Security\CurrentVersion\Plugins\01000600 key which contains your RAS configuration for the client, pushing that down through policy either through the new group policy extensions or by a silent registry merge in a machine startup script, and then set up policies in your RAC to enforce the settings you want.
     
  3. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    Hello,

    The only way to work with XML configurations on client machines is to use ESET Remote Administrator. SmackyTheFrog has the right idea to make sure the client is checking in to the ERA, but the Self Defense module usually blocks out changes to ESET registry entries.
     
  4. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    You're right, I completely forgot about that. In that situation I would do a re-deploy through GPO package assignment using a cfg.xml file with your basic configuration settings to make sure everything is phoning in to your RAS and then work from there.
     
Thread Status:
Not open for further replies.