Please - Very Urgent... ERA push installs

Discussion in 'ESET Server & Remote Administrator' started by aluminex, Feb 18, 2011.

Thread Status:
Not open for further replies.
  1. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    This is extremely urgent!~

    I cannot push install via ERA the way it is intended

    I can push via IP by creating a custom list but the custom list looks like it is restricted to 10 names at a time...

    I can't push via era because it is saying network name is no longer available although I can ping the name and do an nslookup.


    Is there a way either to fix my issue or to input more that 10 clients in custom list at a time.
     
  2. ThomasC

    ThomasC Former ESET Support Rep

    Joined:
    Sep 8, 2008
    Posts:
    209
    Hello,

    I would suggest changing the way that the computers are discovered for the remote installs. There may be conflict between NetBIOS and the information in Active Directory. Open the ESET Remote Administrator Console and go to tools server options. Go to the advanced tab and select edit advanced. The ESET configuration window will open. Tool down to ESET Remote Administrator>>ERA Server>>Setup>>Remote Install>> Network scan methods, click edit and uncheck Active Directory scan. It will now populate only via NetBIOS and Custom search. You should see the same list of computers that are available via windows networking after the change without discrepencies.
     
    Last edited: Feb 18, 2011
  3. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    I tried your suggestion but unfortunately have the same results..
     
  4. aluminex

    aluminex Registered Member

    Joined:
    Oct 13, 2009
    Posts:
    143
    [2011-02-20 18:20:50.442] V1 [4d619ffc0001] [000012b4] <ERASCHEDULER_INFO> Event not executed because has EXLUSIVE flag and currently running: eType=1, id=16
    [2011-02-20 18:20:50.442] V1 [4d619ffc0002] [0000121c] <ERASCHEDULER_INFO> Next wake up: UTC 23:21 20-02-2011 (0 Minutes) (totalmilliseconds=9557)
    [2011-02-20 18:20:50.817] V1 [4d61a1bc0255] [00001730] <SESSION_INFO> KernelProcessRequestFull: 0x0042fcd0
    [2011-02-20 18:20:50.880] V1 [4d619ffa0000] [00000b54] <IPRANGE CONFIG XML_WARNING> [ CCompOrgIpRange::proceedOrgSearch ]: Failed, code: 00000052, description: Unable to resolve name


    I really don't understand how this is possible because in the ERA Console I can actually see the IP already resolved... and I can do nslookups all day long from the same server.
     
    Last edited: Feb 20, 2011
  5. ThomasC

    ThomasC Former ESET Support Rep

    Joined:
    Sep 8, 2008
    Posts:
    209
Thread Status:
Not open for further replies.