Jump to content

How to roll back the update from 10.1.2046 to 10.0.2045?


Recommended Posts

  • Administrators

Please elaborate more on why you would like to roll back to the previous version. V10.0 is in limited support now. Installers could be provided by technical support if there's an actual problem that prevents you from using the latest v10.1.

Link to comment
Share on other sites

I have a previous version installer.

The new version does not support specifying an environment variable (%userprofile% and others) in firewall rules, so after the update, many rules that are distributed through policies stopped working.

Link to comment
Share on other sites

  • Administrators

Just to make sure, switching to the pre-release update channel didn't help? In particular, check if it works with these modules or not:

Firewall module;1438.2
Configuration module;2075.3

Link to comment
Share on other sites

  • Administrators

In Endpoint 10.1 advanced setup, it's here:

image.png

Or you can set it up via a policy here:

image.png

Link to comment
Share on other sites

  • Administrators
1 minute ago, labynko said:

Will this solve the described problem?

That's what we would like you to confirm. If it solves your problem or not.

Link to comment
Share on other sites

  • Administrators

Do you update from ESET's servers or from a local mirror? All Endpoint v10 users have already received the latest firewall module yesterday or earlier so switching to the pre-release update channel should not be needed any more.

Link to comment
Share on other sites

At our customers we suddenly have third-party software like Veeam being blocked which never were blocked before. Tried the pre-release version but no change.

I now have to start making rules for all the software not working anymore which didnt have any issues at all before the update

 

Unlike OP, restarts dont help for us obviously.

Edited by PatrickB
Link to comment
Share on other sites

Yesterday the problem also affected version 10.0.2045. Restarting the computer helped.

Link to comment
Share on other sites

59 minutes ago, Marcos said:

That's what we would like you to confirm. If it solves your problem or not.

In 10.1.2046 this problem was solved by configuring updates according to your instructions.

But that's not the last problem ...

Link to comment
Share on other sites

  • Administrators
14 minutes ago, labynko said:

In 10.1.2046 this problem was solved by configuring updates according to your instructions.

Do you update Endpoint on clients from a mirror? The thing is that Endpoint 10.x should have already received the latest version of modules yesterday at latest without the need to activate pre-release updates.

Quote

But that's not the last problem ...

What other issues are you having with v10.1?

Link to comment
Share on other sites

what should we do for mirror networks ? it seems that networks with Server Security Mirror have still the problem because they did not receive 1438.2 .

Link to comment
Share on other sites

Posted (edited)

Problem with DameWare Mini Remote Control 12.2.4.11.

Now, when trying to connect to a remote computer at the last stage ("Initializing Desktop. Please wait..."), the connection hangs.

Edited by labynko
Link to comment
Share on other sites

Same problem. Using offline update via Mirror tool. In our case , we did not receive FW module updates. Why, because updates via Mirror tool for EP10 has only DLL folder, and not detection engine updates. So we were using EP9 folder for offline updates... Please can you repair EP10 structure created by Mirror tool, also include engine updates? THank you. As workaround we copy DLL folder from EP10 to EP9 and FW modules for v10 endpoints has updated, and all FW rules are working...

Edited by kelepe
Link to comment
Share on other sites

  • Administrators
9 minutes ago, kelepe said:

Same problem. Using offline update via Mirror tool. In our case , we did not receive FW module updates. Why, because updates via Mirror tool for EP10 has only DLL folder, and not detection engine updates. So we were using EP9 folder for offline updates... Please can you repair EP10 structure created by Mirror tool, also include engine updates? THank you. As workaround we copy DLL folder from EP10 to EP9 and FW modules for v10 endpoints has updated, and all FW rules are working...

When updating Endpoint from a mirror, v10 must be updated from the v10 folder, v9 from the v9 folder, etc. While update files are same, sometimes (like this time) we release module updates for a particular Endpoint version in the first round, e.g. when the modules are necessary for correct functioning of the program.

I've tried running the mirror tool and it created an offline mirror for v10 alright. Please explain what you meant by " because updates via Mirror tool for EP10 has only DLL folder". Endpoint uses dll modules and dll.nup files in the mirror for update. Only very old versions (Endpoint 6.5 and older) were using dat files instead of dll but those are already EOL and not supported.

Link to comment
Share on other sites

Marcos, what version of Mirror toll are you using? Or can you post cmd what are you using. In our case only EP9 folder has nup files for Detection engine. EP 10 folder has only DLL folder , and dll.nup files....

Link to comment
Share on other sites

  • Administrators
7 minutes ago, kelepe said:

Marcos, what version of Mirror toll are you using? Or can you post cmd what are you using. In our case only EP9 folder has nup files for Detection engine. EP 10 folder has only DLL folder , and dll.nup files....

Mirror Tool v1.0.1560.0

It creates a complete mirror of v10 update files *.dll.nup (\mirror\eset_upd\ep10\dll\update.ver), including the engine.

mirrortool --outputDirectory mirror --offlineLicenseFilename mirrorEES.lf --mirrorType=regular --intermediateUpdateDirectory temp --excludedProducts=ep4 ep5 ep6 ep7 ep8 ep9 era6

Link to comment
Share on other sites

Thank you Marcos. I have just double checked our cmd, pretty much the same, except we do not explude ep9 product. EP9 mirror structure \mirror\eset_upd\ep9\dll\update.ver (all dll.nup files) and \mirror\eset_upd\ep9\update.ver (all engine updates *.nup). EP10 folder structure \mirror\eset_upd\ep10\dll\update.ver (all dll.nup files) not \mirror\eset_upd\ep10\update.ver and therefore no *.nup files.... Running Mirror tool v1.0.1560.0  on differernt computers, none of them give me \mirror\eset_upd\ep10\update.ver. Or am i missing something???

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...