ESET Staff MartinK 378 Posted July 21, 2016 ESET Staff Share Posted July 21, 2016 Unfortunatly, this is not always working like that, cf attachement : Are those computers reporting their FQDN correctly in client details view (Device identifiers subsection)? There is chance that FQDN/Hostname is not fetched by AGENT before first connection attempt is made (we did not want to postpone connection because of this) which may end up like in your case. Can you check how many computers were not named correctly in Lost&Found group (i.e. in %)? Link to comment Share on other sites More sharing options...
comunic 4 Posted July 21, 2016 Share Posted July 21, 2016 (edited) yep the computers reports their correct FQDN name in the details, allowing me to execute the server task for remaning the computers. About 10% of the computers are named with reverse DNS. I am also disappointed about that in case computer has multiple network card with virtual cards (ex virtualbox), the reported ip in ERA is the fake virtual ip... totally useless ! Edited July 21, 2016 by comunic Link to comment Share on other sites More sharing options...
macros 1 Posted July 22, 2016 Share Posted July 22, 2016 (edited) same case about computer name. Edited July 22, 2016 by macros Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted July 22, 2016 Author ESET Staff Share Posted July 22, 2016 In order to enable this functionality, you should also upgrade all of the agents to the latest version. Just upgrading the ERA server is not enough. In case of ERA 6.4, the "computer name" is reported by the agent. PS: you can apply the "rename computers task", even to specific sub-groups / individual computers, but you have to run this client manually. Link to comment Share on other sites More sharing options...
comunic 4 Posted July 22, 2016 Share Posted July 22, 2016 hi, this problem happened with both 6.3 agent/console and still happens now with 6.4 agent/console. applying rename computer task is a workarround, but not a solution ! Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted July 22, 2016 ESET Staff Share Posted July 22, 2016 In order to enable this functionality, you should also upgrade all of the agents to the latest version. Just upgrading the ERA server is not enough. In case of ERA 6.4, the "computer name" is reported by the agent. Actually upgrading AGENT's won't help as computer are already created on SERVER using previous version. This new functionality will work only for NEW installations of ERA 6.4. Computers that already existed on SERVER before AGENT was installed/upgraded to 6.4 won't be renamed. Link to comment Share on other sites More sharing options...
comunic 4 Posted July 24, 2016 Share Posted July 24, 2016 hi this bug-name happens with newly created computers with 6.4 agents and 6.4 ERA. Link to comment Share on other sites More sharing options...
bbahes 29 Posted July 26, 2016 Share Posted July 26, 2016 May I suggest option to have selection ERA IP or FQDN in all-in-one installer in initial wizard? Link to comment Share on other sites More sharing options...
Amel 0 Posted July 26, 2016 Share Posted July 26, 2016 Plzzz help for urgent installation ..... Is it possible to deploy agent 6.4 through ERA version 5 .. i already test successfully the deployment of agent 6.3 from era 5.. Link to comment Share on other sites More sharing options...
bbahes 29 Posted July 26, 2016 Share Posted July 26, 2016 (edited) May I suggest option to have selection ERA IP or FQDN in all-in-one installer in initial wizard? Even after entering IP address in HOSTNAME field at the start of wizard I get: 2016-07-26 10:03:07 Error: CReplicationModule [Thread 994]: CStepProcessor: Replication slave stopped replication during initialization with reason: UNKNOWN_ORIGIN 2016-07-26 10:03:07 Error: CReplicationModule [Thread 994]: CStepProcessor: Replication slave stopped replication during initialization with reason: UNKNOWN_ORIGIN 2016-07-26 10:03:07 Error: CReplicationModule [Thread 994]: CReplicationManager: Failure of scenario (type=Regular, task_id='00000000-0000-0000-7005-000000000001', link='Automatic replication (REGULAR)' (00000000-0000-0000-7007-000000000001), current_step= [], current_step_phase=, remote_peer=host: "192.168.125.239" port: 2222, remote_peer_type=3, remote_peer_id=c34c8386-80b3-4912-8f87-1e9badf167fe, remote_realm_id=) Creating bundle installer after initial wizard i have client connected to ERA. Edited July 26, 2016 by bbahes Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted July 26, 2016 ESET Staff Share Posted July 26, 2016 May I suggest option to have selection ERA IP or FQDN in all-in-one installer in initial wizard? Even after entering IP address in HOSTNAME field at the start of wizard I get: 2016-07-26 10:03:07 Error: CReplicationModule [Thread 994]: CStepProcessor: Replication slave stopped replication during initialization with reason: UNKNOWN_ORIGIN 2016-07-26 10:03:07 Error: CReplicationModule [Thread 994]: CStepProcessor: Replication slave stopped replication during initialization with reason: UNKNOWN_ORIGIN 2016-07-26 10:03:07 Error: CReplicationModule [Thread 994]: CReplicationManager: Failure of scenario (type=Regular, task_id='00000000-0000-0000-7005-000000000001', link='Automatic replication (REGULAR)' (00000000-0000-0000-7007-000000000001), current_step= [], current_step_phase=, remote_peer=host: "192.168.125.239" port: 2222, remote_peer_type=3, remote_peer_id=c34c8386-80b3-4912-8f87-1e9badf167fe, remote_realm_id=) Creating bundle installer after initial wizard i have client connected to ERA. This seems to be fine. Connection was closed because this computer was "unknown" for ERA Server. Once this is detected, computer entry should be created in Lost&Found group and further connection attempts should be successful. Link to comment Share on other sites More sharing options...
bbahes 29 Posted July 26, 2016 Share Posted July 26, 2016 May I suggest option to have selection ERA IP or FQDN in all-in-one installer in initial wizard? Even after entering IP address in HOSTNAME field at the start of wizard I get: 2016-07-26 10:03:07 Error: CReplicationModule [Thread 994]: CStepProcessor: Replication slave stopped replication during initialization with reason: UNKNOWN_ORIGIN 2016-07-26 10:03:07 Error: CReplicationModule [Thread 994]: CStepProcessor: Replication slave stopped replication during initialization with reason: UNKNOWN_ORIGIN 2016-07-26 10:03:07 Error: CReplicationModule [Thread 994]: CReplicationManager: Failure of scenario (type=Regular, task_id='00000000-0000-0000-7005-000000000001', link='Automatic replication (REGULAR)' (00000000-0000-0000-7007-000000000001), current_step= [], current_step_phase=, remote_peer=host: "192.168.125.239" port: 2222, remote_peer_type=3, remote_peer_id=c34c8386-80b3-4912-8f87-1e9badf167fe, remote_realm_id=) Creating bundle installer after initial wizard i have client connected to ERA. This seems to be fine. Connection was closed because this computer was "unknown" for ERA Server. Once this is detected, computer entry should be created in Lost&Found group and further connection attempts should be successful. It connected but was unable to get updates and activate. Link to comment Share on other sites More sharing options...
RyanTsai 3 Posted October 4, 2016 Share Posted October 4, 2016 I would also like to know if there is any command line options for installing the bundled installer silent? It should be parameter --silent and also --avr-disable may be interesting as it disables AVRemover. Just wondering if there's any other parameter for the bundled installer similar to msiexec /passive which shows a progress bar. Link to comment Share on other sites More sharing options...
Recommended Posts