NOD32 - Change where updates are saved localy

Discussion in 'ESET Endpoint Products' started by XenMike, Sep 19, 2012.

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

    XenMike Registered Member

    Joined:
    Sep 19, 2012
    Posts:
    2
    Location:
    New Zealand
    Hi,

    We are in the process of designing our new Virtual Desktop Infrastucture, we will be using Windows 7 virtual machines where the 'C' drive will be reset back to a standard image everytime the machine is rebooted (we will be using Citrix XenDesktop and streamed vDisks via Citrix Provisioning Services).

    - The 'C' drive is volatile and is wiped at restart
    - The 'W' drive is persistant and changes are retained

    Is there a way to configure NOD32 to save the virus diffinition updates to a location on the 'W' drive rather than the default location on 'C' drive?

    Thanks

    Mike
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    In this scenario, I'd suggest installing your Endpoint product to drive w:. Although the update cache and the content of quarantine stored in particular user profile folders will be erased after a reboot, this shouldn't be a problem. Modules as well as the engine are stored in the ESET install folder after the download and subsequent compilation.
     
  3. XenMike

    XenMike Registered Member

    Joined:
    Sep 19, 2012
    Posts:
    2
    Location:
    New Zealand
    Thanks for the response, that makes sense I guess :)
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.