Jump to content

LegacyConnectorSupport

ESET Staff
  • Content count

    37
  • Joined

  • Last visited

Profile Information

  • Gender
    Female
  • Location
    Please select

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. HTTPS certificate isn't changed immediately. In settings where You change certificate is also timeout to apply this certificate. MDM does this delayed exchange because devices need to be applied new trust (essentially CA from the certificate is first distributed to devices then MDM switches to new certificate) We'll look into how to communicate this more clearly.
  2. LegacyConnectorSupport

    Cannot uninstall ESET Management Agent 7 deployed via GPO

    C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs (note they may contain sensitive information, so PM them to me) Thanks.
  3. LegacyConnectorSupport

    Cannot uninstall ESET Management Agent 7 deployed via GPO

    Not enough rights (access denied) is (usually) caused by Agent self-defense mechanism. I meant Agent trace logs if we can pair them with installation logs we should know more about the issue.
  4. LegacyConnectorSupport

    Cannot uninstall ESET Management Agent 7 deployed via GPO

    Can You also provide Agent logs from same time You tried uninstallation? I assume Agent restarted somehow and enabled self-defense.
  5. LegacyConnectorSupport

    ERA Agent V7 issues

    Hello. The logs sadly do not contain Agent logs (that is we can't determine why it failed to start). If this issue is reproducible please do following at the time You get this error (before You press cancel) please zip entire folder C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData and PM it to me. Thanks and sorry for the inconvenience.
  6. LegacyConnectorSupport

    ESET MDM and IOS 12

    Hello, We use iOS built-in MDM which is backward compatible. So it should. However, I don't recall we had tested this (as it was released recently), so to ensure please raise a support ticket, so our QA engineers can check. We'll be releasing configuration updates later if there are any notable changes, these will be delivered to existing installations via module updates.
  7. LegacyConnectorSupport

    ESET MDM hostname does not match HTTPS certificate

    This is "feature". You can change the timeout interval when new certificate is applied. Otherwise, MDM waits till all devices exchanged their current trust with new one. As You changed hostname the devices must be re-enrolled anyway (as by hostname change they lost connectivity). You can find this timeout in policy in https certificate. As a side note, You're getting the protection state because protection states are evaluated on a certificate which is currently in use. We will think how to make this clearer for a future version.
  8. LegacyConnectorSupport

    ESET MDM hostname does not match HTTPS certificate

    Hello, You can ensure certificate You created has valid (same) hostname via GetConfiguration task. (hostname is still visible in configuration) The reason for removal from policy was that changing this option is essentially equal to reinstallation. (all devices lose connectivity) If configured hostname matches the certificate, please PM me ESET log collector logs. Thanks and sorry for the inconvenience.
  9. LegacyConnectorSupport

    ESCM Installed Application problem

    No problem at all. We will be glad to have those anytime. If the issue does not just apper randomly but is repeatable it would be great to have process monitor logs from the time of upgrade as well as MSI logs are usually not verbose enough. I mistakenly understood You had the same problem as @Pinni3, however that does not seem to be the case (You had Agent reported as installed applications). @MichalJ solution should work for you.
  10. LegacyConnectorSupport

    ESCM Installed Application problem

    Can You please PM me installation/upgrade logs? If this was the component upgrade task ESET log collector logs from affected machine should contain the last upgrade logs. Otherwise, where logs are (or if they're available at all) depends on the method of deployment You used. Thanks in advance and sorry for the inconvenience.
  11. LegacyConnectorSupport

    Warning <resource-not-found> After Upgrade

    The protection state means "Windows updates available". The issue is not the same the other you mention and as Marcos noted this string should be in "Translation support module", not ESMC localization files. (and it's been in there a long time, version 1704 is definitely sufficient)
  12. LegacyConnectorSupport

    Policies - ERA6.5 to ESMC7

    Yes, policies are forward compatible.
  13. LegacyConnectorSupport

    Possible bug during the upgrade (Web Control)

    That seems to be unfortunate effect of application of v7 policy to product with not up-to-date configuration module. As products now have (or should have) up to date configuration module (1685.14 on EES v6.5) this issue should not happen again and in case it already happened and product has invalid configuration this should auto-correct with next policy application. (Agent restart or new policy) Your case with GetConfiguration was most likely caused this way (policy was applied incorrectly on product and You actually saw in requested configuration what product though was correct result of policy application) Sorry for issues caused.
  14. LegacyConnectorSupport

    Changing the MDM replication port on ERA server

    In that case, assign it to the computer where ERA server and MDC is. (sorry MDM is previous product name I'm used to)
  15. LegacyConnectorSupport

    Changing the MDM replication port on ERA server

    Almost there Yes create a policy for 'ESET Mobile Device Connector' however You'll have to assign it to the computer where MDM is installed (not where ERA server is)
×