eornate 4 Posted June 21 Share Posted June 21 (edited) Hi everyone, After migrate client to new server like the link : [KB7732] Migrate ESET PROTECT Virtual Appliance to ESET PROTECT Server (Windows) My clients appear on the console new server, however it was not appear icon Agent or collect the information of this client. Before migrate : After migrate : How to i can fix this issue ? Thanks. Edited June 21 by eornate Link to comment Share on other sites More sharing options...
ESET Staff Solution MartinK 383 Posted June 23 ESET Staff Solution Share Posted June 23 (edited) What happens is that ESET Management Agent was not able to recognize it was actually migrated, and thus it did not resent data to new PROTECT server, resulting in missing data - most probably there will be lots of other data missing regarding the device. In such a case, ESET Management Agent will try to resend and re-synchronize data after some time (around ~1 week), so maybe it already happened for this specific device in the meantime? Unfortunately it seems that migration guide is missing one step, that would help to mitigate this issue. We will consult this with documentation team and possibly extend guide with manual steps that might resolve this issue for all devices automatically. EDIT: I will also reference some older hints to target this issue: For SQLServer, check this explanation and also SQL query to be executed: For MySQL, check this: Edited June 24 by MartinK Link to comment Share on other sites More sharing options...
eornate 4 Posted June 24 Author Share Posted June 24 13 hours ago, MartinK said: What happens is that ESET Management Agent was not able to recognize it was actually migrated, and thus it did not resent data to new PROTECT server, resulting in missing data - most probably there will be lots of other data missing regarding the device. In such a case, ESET Management Agent will try to resend and re-synchronize data after some time (around ~1 week), so maybe it already happened for this specific device in the meantime? Unfortunately it seems that migration guide is missing one step, that would help to mitigate this issue. We will consult this with documentation team and possibly extend guide with manual steps that might resolve this issue for all devices automatically. EDIT: I will also reference some older hints to target this issue: For SQLServer, check this explanation and also SQL query to be executed: For MySQL, check this: Hi @MartinK, Thanks your reply. It worked after i restart client and server. Link to comment Share on other sites More sharing options...
Recommended Posts