Jump to content

T3chGuy007

Members
  • Posts

    44
  • Joined

  • Last visited

Kudos

  1. Upvote
    T3chGuy007 received kudos from LesRMed in Upgrade after upgrade after upgrade   
    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.
  2. Upvote
    T3chGuy007 received kudos from conorc in Secure Browser Warning   
    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!
     

  3. Upvote
    T3chGuy007 received kudos from Peter Randziak in Module Update Failed   
    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!
  4. Upvote
    T3chGuy007 received kudos from andpill in ESMC Upgrade   
    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
  5. Upvote
    T3chGuy007 received kudos from satellite360 in ESMC Upgrade   
    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
  6. Upvote
    T3chGuy007 received kudos from MartinK in ESMC Upgrade   
    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
  7. Upvote
    T3chGuy007 received kudos from MichalJ in ESMC Upgrade   
    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
  8. Upvote
    T3chGuy007 received kudos from Peter Randziak in Upgrade v6 to v7 Installation Error   
    @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!
  9. Upvote
    T3chGuy007 received kudos from Peter Randziak in Upgrade v6 to v7 Installation Error   
    @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.
×
×
  • Create New...