Jump to content

Megachip

Members
  • Posts

    166
  • Joined

  • Last visited

Everything posted by Megachip

  1. Didn't know. How to determine? Regarding to ERAS all is fine. Seems not. Is this anywhere documented? Where ERAS get these informations? MDM isn't listened in repository. Website still pointed to 6.2.176. But still the yellow warning that this version is outdated...
  2. Didn't know. How to determine? Regarding to ERAS all is fine.
  3. Tried to upgrade eslc via Remote Install Task in ERAS (works fine for upgrading Rouge Detection) but getting the following error: SoftwareInstallation: Failed to install binary package '/tmp/cf44-5c97-1fd4-f297/eslc.x86_64.rpm.bin' with exit code: 1, stdout: This is ESET Shared Local Cache distribution script. Press Enter to show the Licence... (press q after you have read the Li... Will try skip license param ---> not working. Is there a way to do it via RA or must it done manually on console?
  4. Except the following information/warning/error: 2016-01-13 13:42:08 W [1] Cannot parse APNS cert, iOS enrollment and push notifications will not work 2016-01-13 13:42:08 I [1] Logging to directory /var/log/eset/RemoteAdministrator/MDMCore/Proxy/ 2016-01-13 13:42:09 E [18] Perform Update: Cannot parse the license file. What does this mean? And ERAS told me, 6.2.180 was the latest version, download provides me 6.2.176.
  5. So, short HowTo: putting mysql socket to /tmp (if it is not there) ... e.g. via symlink. (Changing param in my.cnf did not work for me in appliance) Running installer exact the same way as MDMCore was installed. (server assistant seems working) At least the log tell me, that it will be upgraded: ... 2016-01-13 14:42:05 Status of current installation is: UPGRADE ... 2016-01-13 14:42:06 Database status is 'DB_UPGRADEABLE'. Database exists and will be upgraded
  6. So it require at least the following params (even they are provided via configuration of the already installed version) - should be fixed: Must be provided: HTTPS CERTIFICATE: Provide '--https-cert-path' AND '--https-cert-password' PEER CERTIFICATE: for server-assisted installation provide at least '--webconsole-password' for offline installation provide '--cert-path' AND '--cert-auth-path' CONNECTION TO SERVER AT LEAST: Provide '--hostname' FOR MYSQL DATABASE AT LEAST: Provide '--db-type="MySQL Server"' AND '--db-driver' AND '--db-admin-username' AND '--db-admin-password' AND '--db-user-password' FOR MSSQL DATABASE AT LEAST: Provide '--db-type="MS SQL Server"' AND '--db-driver' AND '--db-admin-username' AND '--db-admin-password' AND '--db-user-password' even on ./MDMCore-Linux-x86_64.sh --hostname=rz-vm57.gfz-potsdam.de --cert-path=agent.pfx --db-admin-username=root --db-admin-password="$secret" --db-user-password="$secret2" --db-type="MySQL Server" --db-driver="MySQL ODBC 5.3 ANSI Driver" --cert-auth-path=agent.pfx it requires 2016-01-13 10:28:54 Error: option --https-cert-path was not specified. So i will try the full install command, cause I do not know where to get (export) the Root CA. Hmm, neither the installer nor the installed MDM can connect to the db anymore :/ Installer: 2016-01-13 11:02:15 Checking database connection and status... 2016-01-13 11:02:15 ./MDMCore-Linux-x86_64.sh: 1108: Connection to database failed with message: 65535 MDMCore: 2016-01-12 14:00:17 Warning: Could not connect to database. Retrying in 10 seconds. MySQL is running, connection works with the provided credentials (also to mdm db) --> hihi, known problem. How to tell MDM which socket to use?
  7. Tried the server assisted installation, but the install script still requested for the database connection If useful, this is how 6.1.414 was installed: ./MDMCore-Linux-x86_64.sh --webconsole-password="$secret" --db-type="MySQL Server" --db-driver="MySQL ODBC 5.3 ANSI Driver" --hostname=*** --https-cert-path=mycert.pfx --db-admin-username=root --db-admin-password="$secret" --db-user-password="$secret2" --db-hostname=localhost --db-port=3306 Would it work to re-run the new installer with the same params? On the other hand, all these params are stored in the config file...
  8. Yes, the simplest way how to upgrade to MDC 6.2 (from 6.0 or 6.1) is to manually run MSI installer in interactive mode. Reason that it is not possible upgrade using "Upgrade infrastructure" task is that MDC 6.2 introduced "breaking" changes in configuration and new parameters (new certificate type) are required and therefore silent installation is not possible. Future releases are expected to support silent upgrade (if nothing goes wrong, upgrade from 6.2 to 6.3 will be possible using mentioned task) Thx. But seems I missed a major thing. Using the ERAS Appliance, so OS is Cent OS. Afaik the linux installer has no interactive mode?
  9. It failed with the following message logged to web-gui: ReadUpgradeStatus: Upgrade infrastructure task failed: Assertion violation
  10. So should I create for every minor update a new upgrade package? The last 6 Years I've simply replaced the msi files and only created new packages on major version upgrades. But problem only occurs sporadic and not on every client/upgrade ... :/
  11. Sometimes, upgrades will not work and the ESET Remote Installer stops with this error message. What params will ERI check to determine if a package is already installed? Only the Packagename from Registry Key or some other params like version? If there is a minor version upgrade, I only replace the msi within the ERAS (not changing the package name). BTW, the safe mode uninstall tool seems not removing these entries :/ P.S. Topic allready exist, but search board search did not found it: https://forum.eset.com/topic/2161-a-package-with-the-same-name-has-already-been-installed-on-this-computer/ Could be merged, if possible.
  12. Strange, hxxp://help.eset.com/era_install/62/en-US/index.html?components_upgrade.htm tell me that Will try the component upgrade task again. On first try, it failed. Regarding to it should update these 3 components, right? P.S. Clicking on your link gets me a 404 (Safari, OS X 10.11.2), while citing the link seems work o.O -> there is an whitespace in your url But I've found hxxp://help.eset.com/era_admin/62/en-US/index.html?client_tasks_upgrade_components.htm, where these both components not listened as manually.
  13. Cause ERAS not supports upgrading MDC, it should be done manually. But is there any guide, manual or something, which describes how to upgrade manually? Simply run the binary without params? Thx a lot, best, meg
  14. Doing a mitm attack for security reason is never a good decision. Also most apps will not support certificate hijacking and with cert pinning it will also not work...
  15. Upgraded to Inside build 11082. EA was uninstalled without any mentions by upgrade. Interesting that 3rd party firewall (Glasswire) still up and running. (no uninstallation/removal cause of upgrade). Why M$ removes ESET on Upgrades?
  16. Have the same problem on a 5.0.2242 Client. Others working. Client is shown in RA, so if connection on port 2222 working, why client reports on 2221 "could not connect"?
  17. You've got an email. Back to local install, which seems really strange: Today I've started my test system, the EA gui was blanc (white) except the green checkmark on the upper right. After some time, it told me, that it could't communicate with the kernel and closed. So I take a look at the ESET services and none was installed/registered (I'm sure that it installed fine last week). After repairing the installation (it was listed within software) and starting the realtime protection (which disabled MS protection), EA seems working fine. --- After Restart, realtime protection is disabled again.
  18. Back on Rails. 1. Remoteinstall quit with the following message: [2015-12-08 16:37:00.193] Status 2401, ID 90: Failure during the package install - exit code: 1603, description: Fatal error during installation. 2. Local install - To be tested again...
  19. Will do, when I got my system recovered. After trying to enable device control (in the non working client) I've ended up in a BSOD boot loop (something about not finding the boot device). Repair not possible. But short form: Customer told me, that he has upgraded Win10 (with installed eset) to Version 1511. First thing was that EA was uninstalled by windows. Second that he can't install it again. On trying to reproduce the problem, I was able to install EA 5.0.2254, but almost no module works (even after restart).
  20. Feels like EA 5.0.2254.X isn't compatible with latest windows November build?
×
×
  • Create New...