Mirek S.

Hello, This is not possible as Apple devices does not allow for such change when they are enrolled. You will have to reinstall MDM with external hostname and enroll devices again. HTH, M.

Hello, MDM certificate change is somewhat complicated process due to support for self-signed certificates. MDM first installs dual-trust profile (device will trust both old and new certificate), then replaces enrollment profile with trust to new certificate. At this moment both certificates are still trusted. When all devices arrive into previous state (or timeout happens) MDM exchanges it's outside HTTPS certificate with new one. Then process of uninstallation of dual-trust profile (installed as first step) is run. Until all this is complete there is some protection state on devices / MDM. As a sidenote for newer EESA versions EESA (as iOS) also trusts 3rd party root CAs preinstalled in device certificate store. Currently certificate change process isn't adapted to this, however even if some protection state persists entire process is safer with such certificates as devices which fail to exchange trust will still continue to connect. If some protection state persists after MDM certificate is exchanged please contact support as it (as always) could be issue on our side. HTH, M.

Hello, Currently only newly enrolled devices (or reenrolled ones) will have profile signed with new certificate. M

Hello, We do support iOS/iPadOS 15, however there were multiple changes in v15 which are not implemented in MDM. There is currently no roadmap to add support iOS v15 new features (except for policies which will be delivered by module update). If You're experiencing issues with iOS 15 please contact customer care. HTH, M.

Hello, Only TLS not aware (just port forwarding without traffic introspection) is supported on both ports. 9980 (by default enrollment port) allows for reverse/application proxy. 9981 (by default mdm port) requires client certificate authentication and thus supports only port forwarding. HTH, M.

Hello, MDC uses - so called - silent license. It should activate the same way as EP server, and does not eat any license from total (license is used just for telemetry and module updates) Devices use EESA license. You might use EP endpoint license but those are more expensive. Generally licensing for devices works the same way as for other producs. HTH, M.

Hello, Please contact local customer care, without actual logs we can't tell. One mistakes customers make relatively frequently is using new APNS certificate (which isn't prohibited by MDM) instead of renewed one which will break connectivity. Phones don't need renewed APNS certificate only MDM needs it (and with correct one connectivity is immediately restored). In case of a new APNS certificate iOS devices have to be reenrolled instead. HTH, M.

Hello, As @MichalJ noted, this is "issue" on MSP provider side, where he installed certificate which is not by default trusted by Android devices. Situation can be remedied by using 3rd party certificate (not ESMC/not self-signed) trusted by Android certificate store by default. Note this issue is related only to enrollment, after enrollment is complete (I.e. You manually choose to trust MSP generated certificate) connection is secure. There does not seem to be official list of trusted root CAs preinstalled with Android, so I'll at least point out same list for Apple devices. https://support.apple.com/en-us/HT205205 For our cMDM solution I believe we are using digicert signed certificate which works across large range of devices and versions. Whether You require Your MSP to fix that certificate depends on Your flow. If Your users (or users across Your company) are skilled enough to ensure it's actually the MSP certificate and not a DNS spoof which could enroll You to different MDM or not. Another option would be manually adding root CA of MSP used certificate into Android trusted root CA store with some secure delivery path prior to enrollment. My opinion would be to require this as certificates can be for free (Let's encrypt was successfully used with our users) and extra load of verification of where You're enrolling should not be Your business in MSP managed environment. HTH, M.

Hello, Please contact customer care, this is nothing we can solve over forum and without logs. What comes to mind is that previous versions did not have MariaDB installation prevented and it caused issues "like" this. Thanks, M.

Hello, To my knowledge there is no restriction of VPN used with EESA as EESA does not care for internet/intranet connection (now) and it's main point of interception is filesystem. HTH, M.

Currently there is only anti-phishing protection it's settings are in EESA policy. Web control is in plan for future however is currently not available. You can post in EP feature requests if You have something specific in mind. HTH, M.

If You mean RAM - no, AFAIK only total RAM can be displayed. If You mean disk space (SSD/internal flash etc...) 8.0 added this for iOS devices. 8.1 will probably add it for Android. Cloud MDM already has this implemented for both OSes.

* Create static group named "MDM Device Enrollment Managers" * Move Agent installed next to MDM into this static group * Create permission set "MDM Device Enrollment Managers" ** In "Static Groups" add "MDM Enrollment Device Managers" Group You created in previous step. ** In functionality enable at least "Read" for "Groups & Computers" * Assign this permission set to user who You want to be able to see enrollment links. NOTE: This user will also require write rights to some other static group which can come from other permission set so he can actually create new devices via enrollment wizard. You want this static group different than "MDM Device Enrollment Managers" as user would have rights to reconfigure MDM and run stuff on server. Downside is users will be able to see configuration of server and MDM. I'm unsure there is any way around this. Possibly @MartinK would be able to think of a beter way around current limitations.

Hello, Your user must be able to see MDM server Agent in EP console to have access to that MDM enrollment links. AFAIK that is the only protection there currently is in place. HTH, M.

@ChrisC Hello, after testing addition to ABM via Apple Configurator 2 we found some quirks in process. * Device must have internet connectivity during erasure phase (You can't input it manually on device). For devices without data SIM this can be archieved by installation of WiFi profile (including valid authentication) via APC2. * Checkbox "Activate and complete enrollment" must be disabled in APC2. * Device must be assigned to MDM server on ABM side before any progress on device is made after reset. * MDM must synchronize with ABM before any progress on device after reset is made and after it's assigned to MDM on ABM server. This can be archieved by restarting MDM service and waiting 2 minutes. * URL configured in APC2 seems to be only used to preinstall certificates onto device. You may input any URL or empty field to skip this step and even though APC2 will output error in step directly following this one it's harmless. We will most likely document some parts or entire process and possibly look into improving ABM synchronization part where MDM restart is currently required to force sync. HTH, M.

The state could persist due to "currently used" certificate, essentially worst error is reported which might not be best idea for these cases. If You try to request configuration from MDM You should be able to see if there is issue with new certificate. New certificate should be applied on MDM HTTPS interface when all devices install new trust (newly applied certificate root CA). This process is required as we support self-signed certificates and process for using already trusted 3rd party certificates never got in (yet) as most customer use self signed certificates from console. Since newer versions of EESA (10.7+ IIRC) and for all iOS versions device certificate store should also be used for MDM HTTPS certificate validation, meaning using certificates signed by 3rd party certificate authorities and already trusted by devices (verisign, let's encrypt...) can be exchanged without default timeout of one month (as can be configured by policy). HTH, M.

As an explanation why this protection state happens. * Apple decided to follow CA/B rules for browsers (which is quite good for security reasons) * We (ESET) have existing userbase and as we honor our customers previous installations and configurations have to work for some time. * Prefered action for this protecion state is to actually create new certificate either via webconsole or via 3rd party CA and setting it to MDM. Disabling notification via policy is there just for extreme reasons, like our implementation issues etc... * Since EP 8.0 some parts of validation are enforced even for Android, so disabling this in policy might not work for You. Valid flow is using correct certificate/chain.

@Christian Stück Nothing is in stone yet, but it's the direction ESET is currently pushing forward. In any case if this happens there would be transitional period and a way to move devices from EP to EPC. @ChrisC I will update this thread once we are able to test and figure out how it should work. However it will likely require release. The ASM issue is different as device is already in Apple remote profile (ASM/ABM sync part is similar) - MDM knows it's serial number so it allows enrollment.

Thanks, We will definitely checks this. Seems like information on our side is outdated and Apple now supports adding devices not purchased via ABM/ASM into ABM/ASM. This actually helps us as well as we have multiple devices not purchased via ABM not usable for ABM testing...

Currently no, And as we now have cloud MDM, there is not much of chance this will ever happen with on premises version.

Hello, I believe this is different case, can You elaborate a bit why You need to run Apple Configurator 2 on devices (for supervised mode) ? Also as far as I know it's impossible to add devices not bough via ABM into ABM. M.

Hello, We currently do not support ASM, only ABM is supported. IIRC main reason was EP is device centric while ASM is user centric but I might be wrong on that one. M.

Hello and sorry for late response. You actually have two issues there, 1. License fails to activate. 2. APNS fails to verify peer (Apple Push Notification Server) certificate so it refuses connection. Please contact support we will need more logs to identify reasons for this behaviour. Sorry for inconvenience, M.

Hello, 1. ESET PROTECT 8 was tested with iPadOS Beta 14 without any issues. I will contact our documentation team about issue in docs. One issue with Apple devices we discovered they don't work well with IP based setups, so only DNS hostnames are officially supported. 2. 3rd party (implicitly trusted and preinstalled within device certificate store) certificate is always prefered for both Apple and Android. Self-signed certificates generated in EP are essentially a historical leftover as nowdays everyone can generate DNS certificate for free from Let's encrypt and possibly other providers. In explanation this is due to certificate exchange process where there is a risk of loosing device connectivity with self-signed certificates while there is lower risk with 3rd party (implicitly trusted) ones. Choose Your poison. 3. DDNS is really about endpoint devices and if they can cache DNS records correctly (in case of DDNS just for few minutes). In world of IPv6 I see little use for this technology, but You probably have Your reason. We never verified functionality wrt DDNS with Apple/Android devices as these could behave differently based on version (and it's a lot of versions to verify). So essentially it should work, but Your mileage might differ. HTH, M.

Hello, We do not officially support user profiles. As for MDM logs, I see only errors on enrollment port (9980) which can be caused by browser terminating traffic or other issues. Important is mdm communication after enrollment - port 9981 (enrollment is essentially just file download over https). If enrollment doesn't work there might be other issue. We might be able to help if we have all the logs required and You are ok with running production server in not officially supported scenario please contact our customer care (with MDM trace severity and EESA application logs) I'm unsure what You mean by EMII. IMEI is accessible only for Android devices enrolled in Device Owner mode (applications are restricted by google and can't access real device identifiers) HTH, M.