I hope to find soon a solution from a way or another If i put manually the license, puf, activated in a flash (this, for various pc/workstation that will be merged in near future is not an option) I've already open a ticket to support but i'm still waiting a reply. The indicated error was "Token not found - ACT.9" I've checked everything in my knowledge, also disabling bridge whitout any policy or optional configuration and reinstall eset from scratch but nope, no way to activate. In this new production plant, the only one located outside our country, i've installed bridge on a windows vm for agent communication and cache updates with era server, and initially i've manually deployed AIO agent+ server security installer for a bunch of servers in this new location: they showing up in era console after a bit but nobody was activated. In out HQ we already have an Era as virtual appliance and different policies for varios scenarios (branch offices, standalone workstation.) using or not bridge for updates or agent communication: everything running smoothly. I'll gladly upload it here if someone points me where it is saved.įor a production plant located outside our main country, i have recenly deployed new hardware and whatsoever for managing it. I tried to find the instalation log, but could not find it. I also made sure we followed all instructions in the troubleshoot page for this error (), but it won't work. By the way, it has exactly the same applications we installed in the other server (in which the installation was successful).ĭoes anyone have a clue about what could be causing this issue? I tried to install through Deployment Tool and locally too, running it from the local disk with administrator privileges. It's important to note that the Server is brand new, we have just installed the operational system and is completely updated. It installs the Management Agent, the host becomes visible in ESET Protect Panel, but fails to install the security product. We are sure about it, because we have just installed this package remotely (using ESET Deployment Tool) in a Server.īut in this Server, it returns WIN.1603 error. The installation package itself contains both ESET Management Agent and Server Security, and is working properly. I'm having trouble installing ESET Server Security for Microsoft Windows Server, Version 8.0 in a Server running Windows Server 2016 Standard Edition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |