Endpoint Security Complete

 View Only
  • 1.  Unable to enroll IOS devices

    Posted Jan 12, 2012 04:06 PM
    Hey Guys, I'm hoping someone can help with an issue we are having with our MMS setup. I have followed the proof of concept guide on this site twice now but when I get to the enrollment screen URL: http://<Site Server Name or Address>/MobileEnrollment/Symc-IOSEnroll.aspx I cannot access this page. The error displayed is that the page annot be found. On my MMS, within IIS, I cannot see this path. Has anyone had issues with this. We are running our MMS on Server 2008 R2SP1. We have also recently just upgraded to CMS 7.1 SP2. I can provide screenshots tomorrow if required as I'm out of the office currently. Thanks in advance.


  • 2.  RE: Unable to enroll IOS devices

    Posted Jan 13, 2012 03:47 PM

    First, you should be using the fully-qualified domain name, e.g. mmstest.be-intuitive.com (not mms.be-intuitive.local).

    Second, use telnet to confirm you can access the site on HTTP port 80 and HTTPS port 443:
    telnet yourserver.yourdomain.com 80
    telnet yourserver.yourdomain.com 443

    Both should connect and have a blinking _ at the command prompt, indicating that you can resolve yourserver.yourdomain.com and also reach it on the provided ports.

    Finally, when you access the URL, it should say <result>success</result>, the URL being http://yourserver.yourdomain.com/MobileEnrollment/Symc-iOSEnroll.aspx

    In all cases above, yourserver.yourdomain.com is not your NS but rather your MMS site server.  If you cannot reach the server on port 80 or 443, it could be a network, DNS, or firewall issue.  It could also be a failure for IIS to have a binding on the default site for the proper port.

    If the .aspx fails, it could be failure to install .NET.

    Does this help?  If you still have an issue, please do post screenshots.



  • 3.  RE: Unable to enroll IOS devices
    Best Answer

    Posted Jan 17, 2012 07:12 AM

    I had to reinstall the Mobile Service manually again as I noticed that I was missing many Virtual Folders in IIS.

    Thanks for you pointers.smiley