scott72 0 Posted August 17, 2015 Posted August 17, 2015 I am currently testing out deploying the MDC on our internal network, but will eventually want this accessible from the Internet in order to use the remote wipe capabilities. Are people installing the MDC separate from their ERA in a DMZ scenario? I would be surprised if everyone was opening up these ports to their internal network. I currently am getting the MDM is up and running, but when trying to enroll on an internal wireless network I am getting a Communication Failure. Anyone run into this issue? I can get to the webpage, but when you hit connect, this comes up.
LocknetSSmith 6 Posted August 24, 2015 Posted August 24, 2015 We installed the MDC on our ERAS, which is in the DMZ... our phones hit the ERAS from the Internet however (or mobile data), not from within the internal network. I should warn you that while we have been able to complete remote enrollments over the Internet/mobile data network, as far as getting ESET Mobile installed, and the mobile device indicating a successful connection to the ERAS/showing as "Connected to Remote Administrator" in local settings, we have not been able to get any of these devices to show as managed in our Web Console. I have an open ticket with support on this however. The one frustrating thing however is when enrolling devices, to make them "authorized," we have had to provide IMEI #'s, MEID's (dec value), and WiFi Mac's, depending on the device. It doesn't feel very standardized. But our phones are also checking in from a host of different providers (Verizon, AT&T, US Cellular).
scott72 0 Posted August 26, 2015 Author Posted August 26, 2015 Thanks for the response, this helps. Not sure exactly how people were deploying this. I think I am going to try and separate the MDC and put it on my DMZ, we'll see if this works.
Recommended Posts