How do I revoke licenses from ESET Remote Administrator

Discussion in 'ESET NOD32 Antivirus' started by VDGC, Sep 8, 2011.

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

    VDGC Registered Member

    Joined:
    Sep 8, 2011
    Posts:
    2
    We use Remote administrator on one of our servers to install NOD32 Antivirus on all our desktops and servers. But now we have some machines that are going out of service, so I want to remotely revoke this clients from our clientlist. Just deleting the cient does not seem to do the trick since they are re-enstated after a short while.
    Do I have to uninstall NOD32 on all obsolete clients one by one or am I missing an option in Remote Administrator. Seems logical to me there should be a way to uninstall the client remotely
     
  2. dmaasland

    dmaasland Registered Member

    Joined:
    Nov 10, 2010
    Posts:
    468
    Follow the remote installation procedure, but choose "Uninstall" at the package selection screen.
     
  3. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    You could always push down a configuration file to the clients you're removing that will clear out the RA server address and any client update parameters they have.
     
  4. JustinTD

    JustinTD Registered Member

    Joined:
    Feb 26, 2011
    Posts:
    30
    I use client passwords which are required to get a license from the server; when taking a client offline, I put them into a policy I created with a bogus password which, once downloaded, prevents them from recontacting the server.

    EXAMPLE:
    - Default policy uses the password BOB to connect to the ERAS.
    - A policy called REMOVED is created and the field for the ERAS password is changed from BOB to SUE.
    - I assign the REMOVED policy to the computer I want to break it's connection with and once it connects for it's normal interval, it pulls this new policy which changes it's config from BOB to SUE for the password.
    - Client goes to connect, server denies connection.

    This is based on a few assumptions...
    1. You set the ERAS to deny connections that are not authenticated.
    2. You have a relatively short update period (mine is 60 minutes.) If we are taking a system offline, we typically know 1-2 days before it goes offline; in events where it is offline right away, it is typically never powered back on (IE, the system broke etc...)
    3. You only have 1 ERAS access (we have 2, 1 local and 1 for WAN access; in this case the policy changes the password for primary and secondary passwords.)

    Hope that helps!
     
Thread Status:
Not open for further replies.