Jump to content

Howto manually reset Agent after Cloning?


j.schulz
 Share

Recommended Posts

Hi,

 

i know about the SID problem and i know about the client reset task but how should that work if i only see one of the cloned machines with an old ip address in the administration webinterface?

Why don't you tell us howto reset the agent by commandline?

 

This Agent thing is really a pain, please let me know howto reset the agent by hand without uninstall and reinstall of it, what is the trick?

 

And why don't you offer the possibility to install the agent without building the sid before the next reboot so it could be imaged without any hassle.

 

 

Please tell me howto reset the agent by hand at the client (command line)?

 

 

Regards X23

Link to comment
Share on other sites

Hi,

 

i know about the SID problem and i know about the client reset task but how should that work if i only see one of the cloned machines with an old ip address in the administration webinterface?

Why don't you tell us howto reset the agent by commandline?

 

This Agent thing is really a pain, please let me know howto reset the agent by hand without uninstall and reinstall of it, what is the trick?

 

And why don't you offer the possibility to install the agent without building the sid before the next reboot so it could be imaged without any hassle.

 

 

Please tell me howto reset the agent by hand at the client (command line)?

 

 

Regards X23

Link to comment
Share on other sites

Hi,

 

i need to know howto do that by commandline? Don't tell me about that funny reset agent task, useless!

How is it possible to embedd the agent in an image and have it in a clean state before imaging or in the end howto reset it?

 

 

Regards X23

Link to comment
Share on other sites

  • ESET Staff

Hello, as of now, there is no option to manually reset Agent ID. The only way, is to use the "reset cloned agent task".

Concerning the options, how to embed the agent in a n image is, to follow these steps:

 

1) Create the template image and install the agent and Endpoint on it.

2) Let the agent connect to ERAS (at least once)

3) Create an image of the disk.

 

IMPORTANT: This computer (image) must not connect to ERAS again, otherwise this will execute the task and will prevent from executing it again.

 

4) For this computer entry in ERA, create a "Reset cloned agent" for the agent with trigger "ASAP" and no expiration so that anytime computer with the same Agent UUID connects, the task will be executed.

5) Image other computers using the prepared image.

 

The "Reset cloned agent" task will change the unique ID so that the server can distinguish between the clients.

 

We are currently working hard, to solve the issues with supporting pooled environments. We aim to have fix available in ESET Remote Administrator 6.5, which is planned for release in December 2016.

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...