anthonyh

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.

Did it not allow you to keep the current database user, or did it clear your database at all? 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.

Is your cert being used to access the site from an external fqdn?

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. It's still there, just a bit different. Now that you are able to install from hxxp:// there are a lot more variables.

We currently have an inquiry in with the development team asking where we can find further information on the sync task errors. With the static groups, do the computers show up when you go to the All group, then click on the Subgroups checkbox?

Technically we are not able to support the installation of 3rd party products through Remote Administrator, but with that being said, are you installing the package using an hxxp:// path or a file:/// path?

Thank you for your feedback, we have submitted it through the appropriate channels and will hopefully see it implemented soon!

That is an excellent suggestion, and I think that could tie in with having an easier way to re-run a task as a whole. The issue has been submitted to our development team. We appreciate your patience!

That makes total sense, and I will submit that request to our developers. To be honest, I think that the features are closed out for the release due out at the end of the month, but our developers do take the requests seriously, so keep an eye 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"

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.

Unfortunately the console itself is not able to export a PDF file directly, but since it is a browser based console, you are able to print directly from the browser and use any 3rd party print to PDF program to accomplish this.

Are you able to see if the EKRN service is still running?

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.

I will pass your suggestion to our development team. In the meantime, you can use the filters to narrow down the package that you want, then once you create that task, you can continue using the same task to deploy to other targets, which would eliminate having to go through the repository list over and over again.