daspolfo 0 Posted October 21, 2024 Posted October 21, 2024 Hi, I've just installed the 8.2.800.0 version of Mac Eset Cybersecurity and when it restart, I can show in Help menu a wrong name for my computer ("iPad"...).. This name was also reported in ESET HOME app on my phone (it add a new computer to others...). I've cancelled the old name of my computer in ESET HOME and rename the new with the correct name but it don't refresh in Cybersecurity.. What's wrong ? Thanks for your help. Best Regards.
daspolfo 0 Posted October 21, 2024 Author Posted October 21, 2024 Ok I've found the solution... for those to whom this would happen: open ESET HOME app and cancel the old Mac name Rename the new (wrong) Mac with their old name (exactly the same) open Cybersecurity and go to help panel Click on "Modify subscription" Enter your license key and validate it reactivate the license and the name should be correct now Strange bug.. 🙃
Administrators Marcos 5,725 Posted October 21, 2024 Administrators Posted October 21, 2024 Please raise a support ticket. We distinguish between the device name and seat name. While the former should be synced with activation servers, the latter is determined only during activation.
daspolfo 0 Posted October 21, 2024 Author Posted October 21, 2024 (edited) It's seems to work perfectly now and the name is correct, even after a reboot. The strange thing is that the wrong name was an old computer who've already connected to my network. It's good now. On the other hand, I had a communication error during a restart but that should have nothing to do with it... (the servers are perhaps overdue for the update?) (the ESET HOME application was extremely slow during the problem and now is normal). Edited October 21, 2024 by daspolfo
Administrators Solution Marcos 5,725 Posted October 21, 2024 Administrators Solution Posted October 21, 2024 There are no issues with our update servers so should the communication error persist, please raise a support ticket for assistance with further troubleshooting.
daspolfo 0 Posted October 21, 2024 Author Posted October 21, 2024 with the process seen above everything works well 😉. It was a bug during the update.
Recommended Posts