Xandros 0 Posted October 6, 2017 Share Posted October 6, 2017 (edited) I bought a Nod32 licence for a couple of years for 4 devices. I've currently only got Nod32 installed on two of those devices as I hadn't got around to putting it on the other two yet. Anyway long story short, my laptop got all screwy, couldn't boot into it, so I wiped it clean and reinstalled Windows. After setting it all up and updating it, I installed Nod32 onto it and activated with my key. It called the device "Rooter-1" (Rooter being what I call my laptop). I didn't think too much of this at first, however not long after the laptop died on me again, and wouldn't boot as before. I realised after doing some tests it was the hard drive that had started to fail and was probably on its last legs, so I replaced it and went through the whole process again. Reinstalled Windows, set it up, updated it, reinstalled Nod32, activated it. Only this time Nod32 called the device "Rooter-2". Now, I've realised that I've essentially activated Nod32 on the same computer three times now (when I first bought the licence, again after the first crash and a third time after I fixed the problem). And coupled with my desktop PC that I have already activated the licence on that equates to my four devices allowed on my licence. Clearly on the activation severs it has the devices that have been activated listed as Rooter, Rooter-1 and Rooter-2. But I can't seem to find a way to manage these devices names. I did come across an online licence manager but it's for business users only and not home users like me, and it doesn't recognise my licence key when I try putting it in anyway. As I say I bought a 4 device licence as I have another two computers aside from my desktop and laptop that I want Nod32 on but can't activate the licence on them yet. When I come to activating Nod32 on those two though eventually will I have issues because of this? Is there anyway at all I can delete the devices from my licence and rename my laptop to being just "Rooster" instead of "Rooster-2"? Edited October 6, 2017 by Xandros Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted October 6, 2017 Administrators Share Posted October 6, 2017 Couldn't it be that you have activated ESET via a wired connection the first time and then via a wifi connection? As for managing home license activations, this will be possible via my.eset.com as of v11 which should be released soon. Link to comment Share on other sites More sharing options...
Xandros 0 Posted October 6, 2017 Author Share Posted October 6, 2017 Well my laptop only connects via WiFi, it does have Ethernet but I never use it and actually have the port disabled in the BIOS. The only thing I did forget to mention was I'd been meaning to downgrade the laptop back to Windows 7 as it has never been particularly responsive with Windows 10, so when it died the first time I took that opportunity. Of course the second time I had to reinstall Windows after replacing the dying hard drive, it was still Windows 7 that I reinstalled but Nod32 still "bumped up" the number appended to the computer's name. Still if licence management will be implemented on my.eset.com soon then presumably that's where I should go to sort this out. Thanks. Link to comment Share on other sites More sharing options...
ESET Moderators Aryeh Goretsky 378 Posted October 10, 2017 ESET Moderators Share Posted October 10, 2017 Hello, It has been a while, but I saw something similar when I was creating a lot of VMs for testing. I ended up logging into my my.eset.com account, deleting the old Name … Name-N accounts, and then renaming the last of the accounts Name-N to Name. Regards, Aryeh Goretsky Link to comment Share on other sites More sharing options...
tmuster2k 22 Posted October 10, 2017 Share Posted October 10, 2017 that was likely just the computer names that were generated for each instance of Anti-theft only. Link to comment Share on other sites More sharing options...
Recommended Posts