Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by adamp

  1. Issue Resolved. I missed the "Repository" setting under 'Server Settings'. Thanks for your help!
  2. I participated in the ESMC beta. In doing so, I changed the following settings on my server: In order to make sure upgrade will run smoothly, you have to copy following repository link hxxp://repository.eset.com/prerelease/beta into two locations: Server settings / repository Policy for ERA Agent / repository Once the policy is replicated and applied, you can start upgrading. Of course, other upgrade methods are as well supported (according to the documentation https://help.eset.com/esmc_install/70/en-US/upgrade_procedures.html ) Now I'm trying to upgrade to the latest ESMC release. I changed the agent and server repositories back to AUTOSELECT. But when I try and do a components upgrade, all I see is ESMC 7.0.451.0. It appears I'm still in the beta channel. I found this KB and followed all of the steps to no avail. https://support.eset.com/kb6749/?locale=en_US&viewlocale=en_US Any help would be appreciated. Thank you!
  3. I would be interested in testing the GA release, however, I'm afraid I don't meet the minimum requirements of having 5 ERA related posts. Bummer!
  4. You can disregard this post. I found a solution. It looks like the day after I downloaded the OVF template version was released. The new version fixed my issue. Thank you.
  5. I receive an error that "server configuration failed. See /root/appliance-configuration-log.txt." The log file tells me it failed to join the domain. "Invalid configuration ("workgroup" set to 'DOMAINNAME', should be 'NETBIOSNAME') and configuration modification was not requested 'net ads join -U username%password' command failed with 255 If I edit smb.conf and change 'WORKGROUP' from "domain.com" to "ABC" and run 'net ads join -U username%password' again, it works. I receive the following message: Using short domain name -- ABC. Joined 'ERA-SVR' to dns domain 'domain.com'. However, I'm not sure what I need to run now that I fixed the error, or what I need to change during template deployment. Any help would be greatly appreciated. Thank you.
  • Create New...