dazza007

Hi I am experiencing the same issue as you and ESET have told me that if the computer is not under control of the RA server the I can only boot into safe mode to remove the local remote administrator. Some computers are 100s of miles away at remote sites. This took 3 weeks to conclude after submitting logs etc. The manual uninstallation removes the local database in C:\programdata\eset so removes communication to the RA server. Manually uninstalling and reinstalling the agent was my only method to fix problems with ESET. I don't have that now. What is also alarming that I have identified some computers that have received RA 6.5 fresh from WSUS Package installer would not uninstall at all (no AV or and comms to RA server) There is definitely an major issue here and it is important to fix the issue so that we can ensure our systems are safe. I have read of others with this issue and ESET support have reported that others have had this issue so please fix can you fix it ESET!

I was using WSUS Package Installer. The MSI provided the company details which creates a folder to which the packages are placed. The package is imported into WSUS, however a refresh or new login to the WSUS package installer, the package vanishes from the console.

I just had an issue using another method of deployment and figured out that the comma in the company name caused issues. Is it possible to remove the comma in the company name (ESET, spol. s r.o.. ) as it would commonly cause errors in different deployment mechanisms?

Thank you for getting back to me I have tested both scenarios fresh install and upgrade of the agent and the uninstallation fails. I switched off self defence and hips and the problem persists. I need to reinstall the remote administrator on a number clients that have RA installed but are not communicating with the ESET server. What concerns me is that you say "in general this should work" as a manual uninstall of the remote administrator and reinstall is my only solution to the bugs in the ESET software, now I do not have any solution to bring in computers to the remote administrator server. Regards, Darren

Following from upgrade of ESET remote administrator 6.4 to 6.5 Self defense is preventing manual uninstall of remote administrator 6.5. I have just installed RA 6.5 on a new computer and once the Remote Administrator has installed the AV software I cannot manually uninstall the Remote Administrator software. Have any other users had this issue or tested that you can uninstall the remote administrator software? Regards, Darren

I have tested the package with the correct permissions (double checked with effective permissions) of agent_x64 msi with the config.msi using msiexec locally and the I get 1603. I get the following errors in the logfile Property(S): P_DB_STATUS = DB_UPGRADEABLE Property(S): P_DB_CONNECTION_STATUS = OK Property(S): SOURCEDIR = deleted Property(S): SourcedirProduct = {41F12F70-5FA9-43F5-94F4-53B54EB4EEC4} MSI (s) (D0:F4) [15:33:25:593]: Product: ESET Remote Administrator Agent -- Configuration failed. MSI (s) (D0:F4) [15:33:25:593]: Windows Installer reconfigured the product. Product Name: ESET Remote Administrator Agent. Product Version: 6.5.522.0. Product Language: 1033. Manufacturer: ESET, spol. s r.o.. Reconfiguration success or error status: 1603. === Logging stopped: 06/04/2017 15:33:25 === The situation is not improved by manually uninstalling the software and reinstalling the software I tried the different switches /qn /qb no change. When manually installing and logging the package a popup conveys a critical error, the logs of which shows the same error above Manually installing the software, to update the previous release 6.4, starts a repair. The package has been used by group policy to update more than 300 clients, however I need to deploy the package too where group policy software deployment is not working. The password (that locks down the software) is not required is there a way of passing this to the msi? Many thanks Darren

Thank you, the agent needs port 2222 and ESET product 3128 In the config file when using a proxy should i be stating the proxy server or the main RA ?

Sorry just edited the post it is 8Gb there are 700 computers with 4 proxy servers

Hi We have a Server 2012 server running RA 6.5 with 8gb of ram, plenty of disk space and a one GB link. I noticed this in the event logs and I could not find any resolution online. The link in the event log is dead. The ESET database runs on SQL Server 2014 which is consuming 2.5 GB of the total memory with 1.5 GB free. svchost (908) A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation. See help link for complete details of possible causes. Resident cache has fallen by 4419 buffers (or 99%) in the last 31 seconds. The pagefile is set for the system to automatically configure with priority set for background services. Ideas?

Hi We have ESET 6.5.522.0 with clients running 6.4.0.2014 Av and agent 6.4.283.0 running Win 2012 and Win 7 clients. I am changing the infrastructure to have remote proxy sites and am going to use the config.ini to specify the settings for clients at the remote site, deployed through group policy. When specifying the servername should I be specifying the proxy or the main administrator server in the settings for the config.ini. I have apache proxies on the remote proxys sites, should the remote administrator clients config.ini also point to 3128 or 2222 for deployment? i have policies set to 3128 for the clients at the remote sites to talk to 3128 on the remote proxy set from the server which apply. I ask as I tested deployment with 3128 and it did not update, however deploying with 2222 to main server using the config.ini then apply settings to talk to apache proxy server on 3128 does update and not error. Many Thanks, Darren

I could sure get some help here. The question "Is it possible to update RA removing Endpoints that have been removed from AD?"

Hello, I have run Static Group synchronizations and I cannot seem to get the system to remove computers from Remote Administrator when computers have been removed from AD. I have 100s of unmanaged endpoints in RA. Is it possible to update RA removing Endpoints that have been removed from AD? Regards, Darren TASK NAME Static group synchronization TASK DESCRIPTION Static group synchronization with Active Directory created during installation TASK TYPE Static Group Synchronization SERVER TASK SETTINGS STATIC GROUP NAME ComputersOU OBJECTS TO SYNCHRONIZE Only Computers COMPUTER CREATION COLLISION HANDLING Move COMPUTER EXTINCTION HANDLING Remove GROUP EXTINCTION HANDLING Remove SYNCHRONIZATION MODE Active Directory/Open Directory/LDAP SERVER ############################## LOGIN ############################### USE LDAP INSTEAD ACTIVE DIRECTORY No SYNCHRONIZATION SETTINGS DISTINGUISHED NAME ############################# IGNORE DISABLED COMPUTERS (ONLY IN ACTIVE DIRECTORY) Yes INVOKED BY TRIGGERS TRIGGER NAME Static group synchronization TRIGGER DESCRIPTION Server Started; Invoked only next time the server starts