Jump to content

Mirek S.

ESET Staff
  • Content Count

  • Joined

  • Last visited

  • Days Won


Mirek S. last won the day on January 17

Mirek S. had the most liked content!

Profile Information

  • Gender
  • Location
    Czech Rep.

Recent Profile Visitors

1,914 profile views
  1. Hello, This is due to changes in ESMC since version 6.5 which was last released version of VAH and can be safely ignored. HTH, M.
  2. Hello, We are aware of this issue, please contact support for HF. (SR had to be pushed out due to APNS deprecation in november 2020) Sorry for the inconvenience. M.
  3. Hello, AdminConnector: Connected: false MDM requires Agent is installed on same system HTH, M.
  4. Hello, It seems like You have changed server CA. (that is server certificate validation fails) In such case You must also reconfigure MDM like You did with Agents (via MDM policy). For such change to apply Agent next to MDM must be able to connect to ESMC server. You might need to manually restart MDM after changing CA. HTH, M.
  5. Connection parameters (and other configuration options) are set during installation, so these settings were not changed from initial setup. Once policy is applied it stays in configuration (some of our products have a feature that policy removal restores original settings, MDM does not have this feature). ERA/ESMC will not try to do something behind scenes without user approval, so no worries. Actually we will create improvement for newer versions so some connection settings are taken from Agent as it does not make sense/is misleading to configure this separately.
  6. Hello, First create MDM policy on device which has MDM installed And edit connection list same as You would with Agent HTH, M.
  7. Well, if you're changing subnet and Agents are deployed in a way they contact server via IP adress, You will need to reconfigure both Agents and MDM (as I previously pointed out MDM also has server connection settings in it's policy). If you're using IP address for MDM device endpoint You will loose connectivity from all enrolled devices and will need to re-enroll those. if You're using DNS names and DNS entires are correctly updated (or traffic is forwarded from some other endpoint) in both cases subnet change should work without issues. As for last connection time, I believe s
  8. Hello, I guess we would need logs (in this case those in proxy directory) in trace severity. However as far as I'm aware MDM should not care where server is - MDM only cares about device endpoint which must remain the same - so this is likely connectivity/firewall issue. Some data are sent/received over Agent installed next to MDM. Device data are sent over MDM proxy component (for which connection can be configured in MDM policy. HTH, M.
  • Create New...