Policy for clients / license drops

Discussion in 'ESET Server & Remote Administrator' started by JustinTD, Jan 25, 2012.

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

    JustinTD Registered Member

    Joined:
    Feb 26, 2011
    Posts:
    30
    Is there a way to setup a policy so the clients under that policy never drop their license? Or is there only that one setting under the advanced server properties?
     
  2. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    I'm not exactly sure what you mean by "drop their license" here. Can you explain? If clients are attached to a RAS, they don't need to be loaded with a license file. Just the target/credentials for the mirror they are attached to as well at the target for administration. Assuming you keep the license on your RAS up to date, all your clients should keep humming along properly.
     
  3. JustinTD

    JustinTD Registered Member

    Joined:
    Feb 26, 2011
    Posts:
    30
    I was referring to the maintenance portion where when a client does not phone home to the ERAS within a given period it drops the client from its' list freeing up that license. At current we have our set to 3 months, but we have some users who may go longer than 3 months phoning home. Ideally we would like to put them in a policy where the ERAS will not ever drop them, but other clients will drop after 3 months of no contact.

    Make sense?
     
  4. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    Unfortunately the cleanup routine is global to the server and I don't see any way to exclude specific objects from it. The best solution I can come up with to complete that task would be to set the Roaming User flag on all your mobile systems, then make a parametric group that only shows systems who do not have the roaming user flag AND have not connected to the RAS for 3 months and when members pop in there you delete them.
     
  5. JustinTD

    JustinTD Registered Member

    Joined:
    Feb 26, 2011
    Posts:
    30
    Great idea! I just implemented that. I adjusted the 'drop time' to 6 months and set a parametric group for 1 month of no connection; this will make it easy to determine problem clients also each month!
     
Thread Status:
Not open for further replies.