MeshCentral 2 - unknown device michael-7-x64
-
We have weird issue that when we add some devices to our Meshcentral 2 server, we also get unknown device called "michael-7-x64" added to the same group.
We had that issues few times so far, not always.
We removed "michael-7-x64" few times, and it came back again together with adding new device.
Now we still have "michael-7-x64" in our mesh.
Does anyone else have similar problem, and do you know why it happens? -
@Mario-Jakovina said in MeshCentral 2 - unknown device michael-7-x64:
We have weird issue that when we add some devices to our Meshcentral 2 server, we also get unknown device called "michael-7-x64" added to the same group.
We had that issues few times so far, not always.
We removed "michael-7-x64" few times, and it came back again together with adding new device.
Now we still have "michael-7-x64" in our mesh.
Does anyone else have similar problem, and do you know why it happens?If you remote to that, what do you get?
-
Try reinstalling MeshAgent on michael-7-x64.
-
This is an AV sandbox performing a scan and run on this application.
Happens regularly when deploying various remote management tools to devices with AV.
You'll get some Microsoft VMs, Bitdefender automated machines, Kaspersky, etc...It looks as though this SPECIFIC device name is from Bitdefender's sandbox :
https://www.reddit.com/r/msp/comments/c8z1kl/bitdefenders_sandbox_just_ran_my_screenconnectcw/ -
@manxam Thank you! Thats it. We use Bitdefender.
-
@manxam said in MeshCentral 2 - unknown device michael-7-x64:
This is an AV sandbox performing a scan and run on this application.
Happens regularly when deploying various remote management tools to devices with AV.
You'll get some Microsoft VMs, Bitdefender automated machines, Kaspersky, etc...It looks as though this SPECIFIC device name is from Bitdefender's sandbox :
https://www.reddit.com/r/msp/comments/c8z1kl/bitdefenders_sandbox_just_ran_my_screenconnectcw/Nice find!
