T3chGuy007

I fixed my issue.  I opened C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\trace.log and I found several errors that it could not resolve my ESET PROTECT server.  I then checked DNS on the NIC and someone had configured it with an old static DNS server.  Once I changed this to automatic, it immediately showed up in ESET PROTECT.

That means there's another policy that applies the same setting, therefore it was necessary to enforce the settings.

I can't think of a reason why a policy would not be applied. What settings are set by the policy? Did you try to enforce the settings by selecting the red flash icon instead of the blue dot?

I understand keeping ESET products up-to-date is very important, but why not leave it up to the customers who pay for your products to decide when to update their devices?  I always keep my products patched, but I decide when to apply them and schedule reboots.  I don't like it that you apply the updates without admin approval and when I login to ESET PROTECT, I find red alerts all of my devices.  What if you push out an update and two hours later, you find it causes a major problem?  You also said that you have an opt out policy, but I don't think you do.  If you did, you would allow customers to permanently disable auto updates and manage them on their own.  If some customers want to keep your auto update policy enabled, that's fine, but you should allow customers the choice to do enable it or keep it disabled without having to worry about it re-enabling.

I understand keeping ESET products up-to-date is very important, but why not leave it up to the customers who pay for your products to decide when to update their devices?  I always keep my products patched, but I decide when to apply them and schedule reboots.  I don't like it that you apply the updates without admin approval and when I login to ESET PROTECT, I find red alerts all of my devices.  What if you push out an update and two hours later, you find it causes a major problem?  You also said that you have an opt out policy, but I don't think you do.  If you did, you would allow customers to permanently disable auto updates and manage them on their own.  If some customers want to keep your auto update policy enabled, that's fine, but you should allow customers the choice to do enable it or keep it disabled without having to worry about it re-enabling.

I understand keeping ESET products up-to-date is very important, but why not leave it up to the customers who pay for your products to decide when to update their devices?  I always keep my products patched, but I decide when to apply them and schedule reboots.  I don't like it that you apply the updates without admin approval and when I login to ESET PROTECT, I find red alerts all of my devices.  What if you push out an update and two hours later, you find it causes a major problem?  You also said that you have an opt out policy, but I don't think you do.  If you did, you would allow customers to permanently disable auto updates and manage them on their own.  If some customers want to keep your auto update policy enabled, that's fine, but you should allow customers the choice to do enable it or keep it disabled without having to worry about it re-enabling.

I understand keeping ESET products up-to-date is very important, but why not leave it up to the customers who pay for your products to decide when to update their devices?  I always keep my products patched, but I decide when to apply them and schedule reboots.  I don't like it that you apply the updates without admin approval and when I login to ESET PROTECT, I find red alerts all of my devices.  What if you push out an update and two hours later, you find it causes a major problem?  You also said that you have an opt out policy, but I don't think you do.  If you did, you would allow customers to permanently disable auto updates and manage them on their own.  If some customers want to keep your auto update policy enabled, that's fine, but you should allow customers the choice to do enable it or keep it disabled without having to worry about it re-enabling.

Hello.  I do not want my PCs to automatically update to the latest version of Endpoint Security when it's released, so I created a new policy to disable the auto-update feature per the article below.  I assigned this policy to my 'All' OU and then I unassigned the built-in auto update policy from the same OU.  However, I upgraded ESET Server Security on my ESET PROTECT server and I discovered the built-in auto update policy was reassigned to my 'All' OU again.  How do I prevent that built-in policy from reapplying to all of my devices after an upgrade?  I want to handle software updates manually and not have it managed by ESET PROTECT.  I cannot delete the built-in policy, but it seems unassigning only works until the server is rebooted or upgraded.
https://support.eset.com/en/kb8147-opt-out-from-auto-updates-in-eset-protect-and-eset-protect-cloud

Hello.  I see that ESET Endpoint Security v8.1.2037.2 was released.  Are there plans to release v8.2 of Endpoint Security soon?  I just don't want to start upgrading my clients to v8.1.2037.2 only to have v8.2 come out a week later as what happened in the post below when v8.0.2039 came out and a week later v8.1.2031 was released.  I know v8.0.2039 was a hotfix and v8.1.2031 was a feature update, so I wanted to make sure there wasn't a feature update planned to be released soon.  Thanks!
 

Thanks for the clarification, but it would have been nice if the hot fix and feature update were released on the same day.  This way, those users who like to keep their devices up-to-date would have had the option to install v8.0.2039.0 or v8.1.2031.0.  I would have never updated our PCs to 8.0.2039.0 if I had known 8.1.2031.0 was going to come out a week later.

Hello.  This morning, I logged into ESET PROTECT and several of our PCs have the warning ""Secure Browser is non-functional".  I checked and we don't even have Secure Browser active, and to be honest, I didn't even know it was an option.  We are running ESET PROTECT (Server), Version 8.0 (8.0.1258.0) and ESET PROTECT (Web Console), Version 8.0 (8.0.191.0) with ESET Management Agent 8.0.1238.0 and ESET Endpoint Security 8.0.2028.0.  Any ideas on why we are seeing this now and how to turn off these warnings?  Thanks!
 

Hello.  I just wanted to confirm that it was our recently installed WatchGuard that was preventing our clients from doing module updates.  I believe it was related to the WatchGuard proxy.  Thanks for the help!

For those of you in the same situation, I first had to install SP3 for SQL Server 2008 R2 Express because you can't directly upgrade to SQL Server 2017 Express unless you are running SP3.  I was running SP2.  Once this was done, I upgraded to SQL Server 2017 Express by using the custom install option.  I then opened ESMC and went to Help->About.  The DB version is now showing Microsoft SQL Server 2017 (RTM) Express Edition (64-bit) 14.0.1000.169.  I then went to Help->Upgrade Product and a new client task was created.  After a few minutes, I was kicked out of ESMC and I could not log back in.  A few minutes later, the login page wouldn't even come up, but after some more time, it finally came up and I was able to log back in.  ESMC is now showing it is v7.1717.0 and the Web Console is at v7.1.393.0.  The last thing I did was install SQL Server Management Studio (SSMS) on my server so I could manage the DB a little easier.
https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2017?view=sql-server-ver15
https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15

For those of you in the same situation, I first had to install SP3 for SQL Server 2008 R2 Express because you can't directly upgrade to SQL Server 2017 Express unless you are running SP3.  I was running SP2.  Once this was done, I upgraded to SQL Server 2017 Express by using the custom install option.  I then opened ESMC and went to Help->About.  The DB version is now showing Microsoft SQL Server 2017 (RTM) Express Edition (64-bit) 14.0.1000.169.  I then went to Help->Upgrade Product and a new client task was created.  After a few minutes, I was kicked out of ESMC and I could not log back in.  A few minutes later, the login page wouldn't even come up, but after some more time, it finally came up and I was able to log back in.  ESMC is now showing it is v7.1717.0 and the Web Console is at v7.1.393.0.  The last thing I did was install SQL Server Management Studio (SSMS) on my server so I could manage the DB a little easier.
https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2017?view=sql-server-ver15
https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15

For those of you in the same situation, I first had to install SP3 for SQL Server 2008 R2 Express because you can't directly upgrade to SQL Server 2017 Express unless you are running SP3.  I was running SP2.  Once this was done, I upgraded to SQL Server 2017 Express by using the custom install option.  I then opened ESMC and went to Help->About.  The DB version is now showing Microsoft SQL Server 2017 (RTM) Express Edition (64-bit) 14.0.1000.169.  I then went to Help->Upgrade Product and a new client task was created.  After a few minutes, I was kicked out of ESMC and I could not log back in.  A few minutes later, the login page wouldn't even come up, but after some more time, it finally came up and I was able to log back in.  ESMC is now showing it is v7.1717.0 and the Web Console is at v7.1.393.0.  The last thing I did was install SQL Server Management Studio (SSMS) on my server so I could manage the DB a little easier.
https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2017?view=sql-server-ver15
https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15

For those of you in the same situation, I first had to install SP3 for SQL Server 2008 R2 Express because you can't directly upgrade to SQL Server 2017 Express unless you are running SP3.  I was running SP2.  Once this was done, I upgraded to SQL Server 2017 Express by using the custom install option.  I then opened ESMC and went to Help->About.  The DB version is now showing Microsoft SQL Server 2017 (RTM) Express Edition (64-bit) 14.0.1000.169.  I then went to Help->Upgrade Product and a new client task was created.  After a few minutes, I was kicked out of ESMC and I could not log back in.  A few minutes later, the login page wouldn't even come up, but after some more time, it finally came up and I was able to log back in.  ESMC is now showing it is v7.1717.0 and the Web Console is at v7.1.393.0.  The last thing I did was install SQL Server Management Studio (SSMS) on my server so I could manage the DB a little easier.
https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2017?view=sql-server-ver15
https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15

@Palps,
Thank you for sharing this information.  In my case, I already had HIPS disabled in the client policy and I had the application status disabled as well.  I'm not sure why using the Security Management Center Components Upgrade task was still hit and miss.  As @tmuster2k pointed out, I got all my clients updated by downloading the .msi files for EEA and ERA and then using my patch management software to deploy.  At least it is working for you though and you are able to get your clients updated.  Thanks again for the information!

@tmuster2k
I downloaded the agent and antivirus .msi files from ESET's website and I first tried to deploy the agent through my patch management software and it failed.  I looked at the log file and I had several of these messages with a different .exe listed.  So I tried deploying the .msi for the antivirus and it worked.  I then tried the agent .msi again and it worked!  Thank you for the suggestion!  From now on, I'll use an AIO installer for new installs and then just download the .msi for upgrades.  Thank you again!!  
Info 1603. The file C:\Program Files\ESET\RemoteAdministrator\Agent\ERAAgent.exe is being held in use by the following process: Name: ERAAgent, Id: 3176, Window Title: '(not determined yet)'. Close that application and retry.