Jump to content

Error Upgrade EES 5.0.2254 to 5.0.2260 using remote install


zulhilmi
 Share

Recommended Posts

when I want to upgrade my EES 5.0.2254 to 5.0.2260 using ERA remote install, all client failed with remarks " No upgrade for this client". I try manually upgrade install on the PC successful. :(

Link to comment
Share on other sites

  • Administrators

The Upgrade client task won't work with the latest Endpoint v5 (5.0.2260) because of a new signature that cannot be verified neither by ERA nor existing Endpoint clients. Push install works like a charm, however.

Link to comment
Share on other sites

The Upgrade client task won't work with the latest Endpoint v5 (5.0.2260) because of a new signature that cannot be verified neither by ERA nor existing Endpoint clients. Push install works like a charm, however.

 

We have tried upgrading EEA v5 to EES v5 and stumbled on same problem. Since we can't use push we are forced to install manually...

Is this going to be fixed in future?

Link to comment
Share on other sites

The Upgrade client task won't work with the latest Endpoint v5 (5.0.2260) because of a new signature that cannot be verified neither by ERA nor existing Endpoint clients. Push install works like a charm, however.

is there any ERA latest version has been released?

Link to comment
Share on other sites

  • Administrators

 

The Upgrade client task won't work with the latest Endpoint v5 (5.0.2260) because of a new signature that cannot be verified neither by ERA nor existing Endpoint clients. Push install works like a charm, however.

is there any ERA latest version has been released?

 

 

The latest version of ERA is 5.3.33. However, it won't help you as your existing Endpoint clients won't be able to verify the new package signature. Use push install instead of an upgrade client task.

Link to comment
Share on other sites

  • Administrators

 

The Upgrade client task won't work with the latest Endpoint v5 (5.0.2260) because of a new signature that cannot be verified neither by ERA nor existing Endpoint clients. Push install works like a charm, however.

 

We have tried upgrading EEA v5 to EES v5 and stumbled on same problem. Since we can't use push we are forced to install manually...

Is this going to be fixed in future?

 

 

Please clarify why push install ain't an option for you.

Link to comment
Share on other sites

 

 

The Upgrade client task won't work with the latest Endpoint v5 (5.0.2260) because of a new signature that cannot be verified neither by ERA nor existing Endpoint clients. Push install works like a charm, however.

 

We have tried upgrading EEA v5 to EES v5 and stumbled on same problem. Since we can't use push we are forced to install manually...

Is this going to be fixed in future?

 

 

Please clarify why push install ain't an option for you.

 

 

Most of ports and services Push install requires are disabled on clients and we don't have Windows Domain in place.

Link to comment
Share on other sites

 

 

The Upgrade client task won't work with the latest Endpoint v5 (5.0.2260) because of a new signature that cannot be verified neither by ERA nor existing Endpoint clients. Push install works like a charm, however.

is there any ERA latest version has been released?

 

 

The latest version of ERA is 5.3.33. However, it won't help you as your existing Endpoint clients won't be able to verify the new package signature. Use push install instead of an upgrade client task.

 

Usually we do upgrade client task for previous version and no failure occurred. Since we try push install usually wont help in upgrade version.

Link to comment
Share on other sites

  • 2 weeks later...

 

 

The Upgrade client task won't work with the latest Endpoint v5 (5.0.2260) because of a new signature that cannot be verified neither by ERA nor existing Endpoint clients. Push install works like a charm, however.

is there any ERA latest version has been released?

 

 

The latest version of ERA is 5.3.33. However, it won't help you as your existing Endpoint clients won't be able to verify the new package signature. Use push install instead of an upgrade client task.

 

 

I'm left with option to walk around 60 clients and do manual upgrade. Can you confirm that future upgrades will work via upgrade client task?

 

ERA: 5.3.33.0

EEA: 5.0.2254.0

EES: 5.0.2254.0

Edited by bbahes
Link to comment
Share on other sites

  • Administrators

Most likely there will be no future versions of Endpoint v5. If there are (e.g. due to support of newer Windows 10 builds), the problem will be same as the digital signature will not be verified by ERA nor existing Endpoint clients.

Link to comment
Share on other sites

Most likely there will be no future versions of Endpoint v5. If there are (e.g. due to support of newer Windows 10 builds), the problem will be same as the digital signature will not be verified by ERA nor existing Endpoint clients.

 

Thanks for this info.  Is this move to force v5 users to switch to v6?

 

Can you please confirm part about signatures, please?

Edited by bbahes
Link to comment
Share on other sites

I'm left with option to walk around 60 clients and do manual upgrade. Can you confirm that future upgrades will work via upgrade client task?

 

ERA: 5.3.33.0

EEA: 5.0.2254.0

EES: 5.0.2254.0

 

You are lucky one with only 60 clients. We have 840 clients and only 50 of them are on-site and in AD. Others are in remote locations, most of them not accessible remotely. And this is the reason I am not happy about this (and not the first) surprise from Eset.

Edited by karlisi
Link to comment
Share on other sites

  • ESET Staff

In case you upgrade to the latest endpoint (5.0.2260) future upgrades will go smoothly.  It should be possible to use PCU update, to force upgrade the clients.

Is this way not acceptable for you? Here is the link to the KB article: hxxp://support.eset.com/kb3308/

 

This has nothing to do, with us forcing anyone to upgrade to ERA 6. It was caused by Microsoft, which dropped support for the certificates (old ones) used to sign our installation packages, so it was unable to download them using MS browsers (file was marked as dangerous). Also, those certificates will expire in a short period of time, so there was no other way for us, than to change them to the newer ones. We are sorry for any inconvenience.

Link to comment
Share on other sites

In case you upgrade to the latest endpoint (5.0.2260) future upgrades will go smoothly.  It should be possible to use PCU update, to force upgrade the clients.

Is this way not acceptable for you? Here is the link to the KB article: hxxp://support.eset.com/kb3308/

 

This has nothing to do, with us forcing anyone to upgrade to ERA 6. It was caused by Microsoft, which dropped support for the certificates (old ones) used to sign our installation packages, so it was unable to download them using MS browsers (file was marked as dangerous). Also, those certificates will expire in a short period of time, so there was no other way for us, than to change them to the newer ones. We are sorry for any inconvenience.

 

We will try PCU update in future. Thank you for this information.

 

Regarding old Microsoft certificates, don't they generate new ones? If you support v5 until Dec 2018 why don't you sign them with new ones?

Link to comment
Share on other sites

  • 2 months later...

Is this issue fixed?

In ERA 5.3.39 changelog I see:

 

Version 5.3.39.0

Fixed: Remote client update task now supports .msi-installers with updated digital signatures and allows seamless client upgrade to version 5.0.2260.x and later.
Fixed: With any other than blank password for the administrator account, the User Manager will refuse to create new users.
Added: Updated copyright statement for all product components.

 

https://www.eset.com/int/business/remote-management/remote-administrator/version-5/#download

Link to comment
Share on other sites

Is this issue fixed?

In ERA 5.3.39 changelog I see:

 

Version 5.3.39.0

Fixed: Remote client update task now supports .msi-installers with updated digital signatures and allows seamless client upgrade to version 5.0.2260.x and later.

Fixed: With any other than blank password for the administrator account, the User Manager will refuse to create new users.

Added: Updated copyright statement for all product components.

 

https://www.eset.com/int/business/remote-management/remote-administrator/version-5/#download

 

I was able to upgrade clients to 5.0.2260.x with this release.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

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