Jump to content

anthonyh

Former ESET Employees
  • Posts

    34
  • Joined

  • Last visited

Posts posted by anthonyh

  1. I appreciate the patience on this issue, we have new steps for using the LDAP with simple authentication in order to get active directory to sync, which can be found here:

    hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3665

     

    This has been very successful in getting the active directory structure to sync within the Linux deployment of Remote Administrator, please let me know if you run into any issues.

  2. I didn't get that extra username/password on the initial install, nor on the upgrade. However when I had a few "quirks" I tried a repair, and then I got that extra prompt. Entering a username that does, or does not, exist in the database gave me the same error; choosing to create a new user caused the entire installation to fail and rollback.

     

    So some weirdness going on here I think.....

     

     

    Jim

     

    Did it not allow you to keep the current database user, or did it clear your database at all?

     

    all of my components on the RA server are not up to the new version.

     

    Can you list what did/did not upgrade, did you use the same upgrade path listed in the link provided by CB530?  If so, were there any issues during the process.

     

  3. hello,

    i totaly agree that eset doesn't provide any support on third party msi installation, but this feature is really important for me !

    i tryed using the hxxp:// link as if i installed an eset package.

    So we can figure out where it went wrong in the chain, there are a couple places we can look for the error.  On the server, there are two logs, C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\trace.log and C:\ProgramData\ESET\RemoteAdministrator\Server\EraApplicationData\Logs\trace.log 

     

    On the client, there is just the C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\trace.log.  If you can find the error that corresponds with the time stamp, we can go from there.

     

    Also, if you could try to download it locally and try to install it using the file:/// path and see if we get different results, that can help us determine if it is a transfer issue or an execution/install handling issue.

     

    this is a complete joke that this version doesn't have this. it's a step backwards.

     

    It's still there, just a bit different.  Now that you are able to install from hxxp:// there are a lot more variables.

  4. I'm just wondering how to get the Tasks to start faster.

     

    For example I sent a command to one client. shutdown -r, sent 11 minutes ago. Why is it taking so long? There's no other deployments happening as far as I can tell. It's kind of hard to tell really, maybe I just don't know where to look. Is there a place to see what the server is currently working on? And as I am typing this it finally completed, 12 minutes after it was sent. I tried a test message task as well and it took about as long. Triggers were both set for ASAP.

     

    Also, is there a way to get RA6 and the Agent to sync up on demand? I have a policy in place for it to check every 5 minutes, but I don't know how to get a client to update when I want it to.

     

    Probably the same question really, but specifically policies. I started by setting the group policy for my Windows clients to the 60 minute interval and then switched to the 5 minute interval, but will my clients not get the new policy until the 60 minute interval is up? How do I get them to refresh their policy on demand?

     

    I'm probably overloading a single topic here, but I also have one singular client that is reporting that Windows Security Center is reporting "the feature is not installed or working properly", but when I go to the client the security center doesn't have any warnings. Maybe it is already cleared, I don't know, I can't get it to update on demand, I guess I have to wait for the 60 minute policy to check?

     

    EDIT: yep, this client is cleared now, and the policy was updated. I'm sure there's probably a way to force the agents to sync with RA6, I just can't figure it out.

    The tasks start as soon as the agent checks into the ERA again.  You can force the client to check in by left clicking on the client and selecting "Send Wakeup call"

  5. I'm trying to configure a Domain security group. I'm the only IT person, but I've got a slow day so I figured I'd try and get this security group thing working, well it was just giving me a connection error, so I ran the diagnostic tool and I'm getting this:

    2015-02-12 13:54:38 Error: ConsoleApiModule [Thread 7fc9ea7d4700]: Untranslatable CInterModuleException: boost::process::find_executable_in_path: 
    file not found: No such file or directory: "wbinfo"
    

    I love how Ubuntu helps idiots like me. I typed in wbinfo and it told be to install "winbind"

    apt-get install winbind

    So I'm not getting an error any more. It doesn't find anything though, there is nowhere to specify a domain or authentication or anything. Do I need to track down the LDAP connection string and manually type it in there? What is the select button even for?

     

     

    Are you able to run authconfig.tui to join the machine to the domain?  After that, Remote Administrator should be able to read the AD structure.

  6. Hello Jim, I apologize for the delay on a response, but to answer your first question, removing the clients from the task does not trigger any action to be carried out on the client, it is simply modifying the clients that the task will target the next time the task is run.

     

    As for the other two, there is some limited capabilities in creating tasks with certain triggers.  If you were to create a dynamic group with a specific value, let's say the template  Installed software . Application name contains Endpoint, then all machines that do not have an Endpoint product currently installed would get filtered to that group.  From there, when you create a task, you can set the trigger to run the Endpoint install task on the group when a new machine is added to that group.

     

    The only way to see what tasks have been triggered/run is to go to Admin>Server/Client tasks then select the task through the tree, right click on it, then go to the details tab.  It will tell you when it has been triggered, when it started running the task, and the outcome of the task execution. 

     
  7. You are correct, there are a lot of moving parts to an install, which is typically all handled by our All-In-One installers.  We do offer the stand alone installers so that each program can be configured to work around the SBS features, but it can be time consuming when setting it up per each environment.

     

    If you have the option of hosting a HyperV instance to run the Remote Administrator sever, the only real drawback would be having to send the Agent live installers to the clients for manual installation.  However, after that is done, everything else will be controllable through the server.

  8. The best thing to do here, because the database password is not kept unencrypted anywhere, is to change the setting to Create new user, and change the username.  This username is only held by Remote Administrator, and the password is randomized on each install.  The old user can be deleted after the install by using the SQL Studio.

  9. You are correct in that the version 6 Remote Administrator no longer has the mirror built in.  With that said though, the clients still have the ability to create a mirror server and host the updates.  In most of the instances we are seeing, the techs are usually setting up the ESET File Security install on the Remote Administrator server machine as the mirror, which is found by entering the advanced settings menu, then Updates>Mirror.  It still needs port 2221 to be opened in the firewall, and the server connection address for the updates is still in the hxxp://%servername%:2221 format.

×
×
  • Create New...