Jump to content

Peter Randziak

ESET Moderators
  • Posts

    3,511
  • Joined

  • Last visited

  • Days Won

    207

Posts posted by Peter Randziak

  1. Hello @sreece,

    how would you like the VA to cache the updates as it is not supposed to have internet access?

    As of now the ESET PROTECT VA has Apache HTTP proxy integrated in order to cache / forward the traffic for the clients, see https://help.eset.com/protect_deploy_va/10.0/en-US/enable_apache_http_proxy.html

    What is the use case? Is it a completely offline environment or why the ESET PROECT VA should not have the internet access? 

    Peter

  2. Hello @j-gray,

    On 2/21/2023 at 7:54 PM, j-gray said:

    So far, the activation issues have been cleared up for the most part.

    really glad to hear that 

    The issues 1 and 2 are on ESET PROTECT, we would need to check it from logs to see what is being sent to the server and what happened with the tasks.

    On 2/21/2023 at 7:54 PM, j-gray said:

    EI Connector does not show as installed under Installed Applications in client details even though it is installed.

    • I was hoping the upgrading the EI Connector would get it to register again, but no luck
    • We have approximately 160 clients where EI Connector is installed but EP Console does not reflect this.

    The issue is being discussed at https://forum.eset.com/topic/35383-os-x-ei-connector-does-not-register-in-ep-console-v10/

     

    On 2/21/2023 at 7:54 PM, j-gray said:

    We seem to have a huge increase in failed agent and connector installs and upgrades for OS X only due to repository inaccessibility with the following: Failed to synchronize package repository. See trace message for more details. GetFile: Cannot connect to host 'repository.eset.com' [error code: 20003]

    The error 20003 means E_HTTP_CANT_CONNECT_TO_HOST
    So this should be checked on the network level. Some IDS/IPS may bump the traffic.
    Workaround might be to use PROXY with caching - it might mitigate the situation, as there will already be pre-cached files

    Peter

  3. Hello,

    On 2/16/2023 at 9:52 AM, avielc said:

    I'll try to read between the lines for j-gray here.  (this is also true to me) 
    usual change log available for any EEA\EES\EP related updates are massively longer.( That's a good thing!)
    can you please escalate to EI team to invest some love into the change log too? 
    As you can see people like me and j, we dig deep. we want to understand the product better and get the broader picture to know if this update is critical or not and whether should be push it to production sooner than later. 
    This is true and important just as much for EEA\EP as it should be for EI. 

    sure, I will pass the feedback to the product manager responsible.

    I must admit that I prefer and like detailed changelogs too 🙂 

    On 2/16/2023 at 9:52 AM, avielc said:

    Thanks again for all the support mate, really appreciate all that you do for the community here.

    Thank you very much for your kind words and appreciation.
    Thank you for being active on the ESET Forums and your patience with tackling issues.

    Peter

  4. Hello @j-gray,

    I appologize for the confusion, as the info provided was not complete.

    The EI is not listed among installed applications locally, but it should be displayed in the ESET PROTECT console.

    We seen cases, when it was not reported into the management console, those were resolved by clearing the system cache on the macOS. 
    Hope it will resolve the issue for you too.

    Peter

  5. The issue is fixed in the Banking & payment protection module 1296. As of now it is available on pre-release update channel, full release is expected during the next week if no issues will be reported.
    The Protected websites redirection feature for Chrome and MS Edge browsers will be enabled back with the module update.

    The browsers restart is required after the module update to apply the fix.

    Peter on behalf of the teams involved

  6. 6 hours ago, Flipper69 said:

    I do not use the "Secure all browsers" feature as I prefer to use a separate B&PP browser session for all banking and payment sites and another non-B&PP browser session for regular browsing.

    secured (isolated) browser is a basic idea of the Banking and Payment protection. In the past, the „default“ was browsing in a standard i.e. unsecured browser. We changed this „default“ browser to secured, with the option to choose whether you want it to be the same as isolated browser (with essential extensions only), or with the extensions you like/want.

    For most of the users, enabling Secure All browsers improves their security in much wider range of scenarios, than just banking and payment and it is able to improve the protection for much more customers than the previous solution that relied on the redirection.

    For users who like the really isolated mode or „special browser mode“ (secured browser with custom profile directory and blocked all non-essentials extensions) is still accessible from desktop shortcut / start menu / product tile.

     This functionality will be preserved in the future.

  7. The issue is fixed in the Banking & payment protection module 1296. As of now it is available on pre-release update channel, full release is expected during the next week if no issues will be reported.
    The Protected websites redirection feature for Chrome and MS Edge browsers will be enabled back with the module update.

    The browsers restart is required after the module update to apply the fix.

    Peter on behalf of the teams involved

  8. Dear ESET Cyber Security 7 BETA  for macOS participants,

    as the full release is going to happen very soon, I would like to thank you all for your participation in the BETA program, especially for the feedback provided.
    We hope that the GA version will run well for you and for all our users too.
    We recommend to use the GA version once it becomes available.

    Peter on behalf of the teams involved

  9. The dev team decided to disable Protected websites redirection feature for Chrome and MS Edge browsers, until the issue is resolved in order to prevent the browsers crashes.
    The change will be distributed via an Rapid response module update (probably with version 21778).
    After the automatic update, the Chrome and MS Edge won't crash anymore, but the Protected websites redirection feature will not work until we release the full fix.

    Disabling the Protected websites redirection feature resolves the issue.

    Another way to resolve the issue is to use the Secure all browsers option.
    We apologize for the inconvenience caused by this issue.

  10. The dev team decided to disable Protected websites redirection feature for Chrome and MS Edge browsers, until the issue is resolved in order to prevent the browsers crashes.
    The change will be distributed via an Rapid response module update (probably with version 21778).
    After the automatic update, the Chrome and MS Edge won't crash anymore, but the Protected websites redirection feature will not work until we release the full fix.

    Disabling the Protected websites redirection feature resolves the issue.

    Another way to resolve the issue is to use the Secure all browsers option.
    We apologize for the inconvenience caused by this issue.

×
×
  • Create New...