orphan client cleanup?

Discussion in 'Other ESET Home Products' started by historicmountain, Jun 22, 2010.

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

    historicmountain Registered Member

    Joined:
    Aug 17, 2009
    Posts:
    9
    We're decommissioning the current home of the NOD32 Remote Administrator Console. I've installed the software on the new server, and created a task to update the configuration for the clients. Now I'm getting messages that I am over my license limit, because the clients are now listed under both servers. The closest topic I've found in the KB is Solution ID: SOLN884, which doesn't mention anything about this issue.

    How has anyone else dealt with this?
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    In the ERA Server setup - Server Maintenance, temporarily set the option "Delete clients not connected for the last..." to, let's say, 3 days and click "Clean up now". Then set the value back to the defaults (6 months) or whatever limit you want to use.
     
Thread Status:
Not open for further replies.