it means the auth key for your EEM server does NOT MATCH the one you distributed in the install package to the clients. It's usually because someone mistakenly deleted the server object from within EEM, and thought (wrongly) that recreating it would make everything ok.
compare the sdmcfg.ini files from your SBAdmin and client directories, and you'll most likely see the key is different.
Thanks for your quick response.
I will replace sdmcfg.ini file and chek it out.
I would also share one thing, generally when we sync. client first time, it will automatically create machine entry into DB with one uniq ID. In this case infected machine's uniq ID is already allocated to other working machine.
Infected machine's name is ABC and uniq id is 0x00007aef
0x00007aef id is already allocated to one working machine XYZ into server console.
can you post the scm.ini file from the client here? I expect something funny is up.
user is not available right now. I will post it ASAP.
here is the SCM.ini file from client machine.
seems good - I was worried this was a single object install set, but it's a group install which is correct. What I expect is that you have activated twice on this machine, and perhaps performed an eBoot recently, but the network name is different to the EEM name
make sure they are the same between Windows and EEM and it may sync again - without seeing the entire cilent log it's hard to tell.