Jump to content

Agent V7 show as Updated in ESET Protect V8


Recommended Posts

Hi Dears.

We have a problem in upgrading agent 7.0.579 to V8 in one of our customers network.

ESET Protect V8 show Agent v7.0.579 as Updated ! So Upgrade task will finish successfully without any changes !! Repository in Online.

We install a New Server and transfer Database to new server , Problem is persist.

Upgrading with GPO will work ! but Upgrade Task will not work because ESET says it is up-to-date !

 

 

 

Agent.PNG

Dashboard.png

Link to post
Share on other sites
  • ESET Staff
6 hours ago, kamiran.asia said:

ESET Protect V8 show Agent v7.0.579 as Updated ! So Upgrade task will finish successfully without any changes !! Repository in Online.

In short, problem is, that this version of AGENT (7.0.579.0) was to be used only with ESMC that was distributed on Japan market and thus it has a specific versioning and compatibility settings. In case it is used with non-Japan ESET PROTECT, it won't upgrade automatically and only possibility is to upgrade it manually -> and once it will be upgraded to globally available version (= compatible with your ESET PROTECT), it will have no issue in upgrading next time.

Could you please confirm machine was previously managed by Japan ESMC installation?

Link to post
Share on other sites
11 hours ago, MartinK said:

In short, problem is, that this version of AGENT (7.0.579.0) was to be used only with ESMC that was distributed on Japan market and thus it has a specific versioning and compatibility settings. In case it is used with non-Japan ESET PROTECT, it won't upgrade automatically and only possibility is to upgrade it manually -> and once it will be upgraded to globally available version (= compatible with your ESET PROTECT), it will have no issue in upgrading next time.

Could you please confirm machine was previously managed by Japan ESMC installation?

No All Version was Enu.

Link to post
Share on other sites
  • ESET Staff
32 minutes ago, kamiran.asia said:

No All Version was Enu.

Actually it could have been ENU, but this device seems to have been deployed from Japan version of ESMC (maybe just installer created in such ESMC was used), or possibly just migrated from such environment.
But regardless of that, this AGENT won't upgrade automatically when task is executed from non-Japan ESMC, so I would recommend to upgrade it manually, i.e. using any installer type create in ESET PROTECT. In case there are many of such devices, we might think of some more automated workaround (for example using run command task...).

Also I will probably report this, as even if it won't be possible to upgrade such client, it might be nice to detect such state...

Link to post
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...